Riparare pacchetti danneggiati o riparare il sistema Zorin.

Questo tutorial vi spega come ad esempio, dopo un aggiornamento o un eventuale installazione di software non compatibile possa danneggiare o bloccare il sistema.
Se avessimo questo tipo di problema, apriamo il il terminale(se vi e' piu' semplice Ctrl+Alt+t) e digitamo i seguenti comandi (non insieme):

sudo su -c apt-get update

sudo su -c dpkg --configure -a

sudo su -c apt-get -f install

infine diamo:

sudo apt-get update

sudo apt-get upgrade

Alla fine dovremmo essere riusciti a sbloccare/riparare il nostro sistema.

questa guida è ancora valida?

il primo comando, dopo aver messo la mia pw, mi restituisce

Code:

No passwd entry for user 'update'


"sudo su" is a command used to change access as a user to running a command as Admin or User with Root.
If your installation has your user as the admin, you need only to use "sudo" to elevate to root since you are the only user.
The error you received is saying that there is no stored password for a user that does not exist.
To overcome that, remove the use of "su" from the command.

Aravisian wrote:"sudo su" is a command used to change access as a user to running a command as Admin or User with Root.
If your installation has your user as the admin, you need only to use "sudo" to elevate to root since you are the only user.
The error you received is saying that there is no stored password for a user that does not exist.
To overcome that, remove the use of "su" from the command.

thank you, I'll try again.

unfortunately there isn't a "like" button on this forum

now this:

Code:

:~$ sudo -c apt-get update
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
            [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] file ...


Doncic wrote:now this:

Code:

:~$ sudo -c apt-get update
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
            [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
            prompt] [-T timeout] [-u user] file ...


You can run all of the above commands without the "-c" in order to update, upgrade or dist upgrade

Code:

sudo apt-get update

Updates the sources.list

Code:

sudo apt-get upgrade

Upgrades any packages that have availabel upgrades from the Main Server / Ubuntu repository

Code:

sudo apt-get dist-upgrade

Upgrades your Distribution Packages.

I know, thank you, I was just tryng to follow @albano guide

albano wrote:Questo tutorial vi spega come ad esempio, dopo un aggiornamento o un eventuale installazione di software non compatibile possa danneggiare o bloccare il sistema.
Se avessimo questo tipo di problema, apriamo il il terminale(se vi e' piu' semplice Ctrl+Alt+t) e digitamo i seguenti comandi (non insieme):

sudo su -c apt-get update

sudo su -c dpkg --configure -a

sudo su -c apt-get -f install

infine diamo:

sudo apt-get update

sudo apt-get upgrade

Alla fine dovremmo essere riusciti a sbloccare/riparare il nostro sistema.

and what's "sudo su -c dpkg --configure -a" for?

Doncic wrote:
and what's "sudo su -c dpkg --configure -a" for?

A quick breakdown for all:
sudo = SuperUser DO command. Issues a command with administrative privileges.
su = switches to another user account without needing to log out and log in, allowing a command to be issued as another user
-c = This denotes the command for the other user. Use the -c, then type the command that is to follow.
dpkg = is an installation or removal utility
--configure = this command tells dpkg to run the configuration script that will set the parameters of installed software to the existing hardware and software being installed to. For example, installing software that must make use of Graphics Drivers must be configured to know which drivers it must communicate through to run on the graphics card.
-a = All. This command denotes to perform a command for All.

Below that you will also see ''-f' which is the command "Force install". The command to install by Force is used to Force the installation of a package that your computer initially refused to install if the --configure- found missing dependencies or incompatibility. Sometimes, configuration utility is over-protective and needs a human operator to 'force' through an installation Would Work, but the Utility's programming makes it think it would not work.

In this thread, "sudo su -c dpkg --configure -a" is used in regards to a system Upgrade. As this upgrade may consist of software that makes use of existing software and hardware on your machine, it will need to be configured.
So, SuperUser Privileges first to install with Root using 'sudo', 'su' to switch from the admin account to the user account to install the upgrade to the users account (Not applicable in your case), -c to show that the command for the other user follows; the following command is for the 'dpkg' utility to '--configure" and Install (when you invoke dpkg, the command to install is automatic) the upgrade to; '-a' all user accounts.

I hope this breakdown and explanation helps. Perhaps Albano could have explained it more neatly or better than I. I have not seen Albano actively post on this forum in the entire time I have been on it.

I do not believe that the listed commands above are applicable on Ubuntu 18.04. The terminal commands given above say to run the apt updater, which updates the sources list, then gives an installation command without specifying what is to be installed until after. It tells to switch user account from Admin to User without ensuring that it is necessary to do so as many of todays users are also the Admin as they installed Zorin on their personal Home Machine.
I am not certain as I moved from Windows to Linux after all that and started out on Zorin 12, just before Zorin 15 was introduced. I have only been using Zorin and Linux for a short time and lack experience with anything at all pre-Zorin12.

Thank you very much