I upgraded to Ubuntu 20.04 today, choosing LightDM over gdm3 during the upgrade. During the upgrade I was asked if I wanted to keep or replace /etc/sane.d/dll.conf
file. I decided for keeping it.
Now, without actively rebooting, the "Oh no! Something went wrong" screen appeared.
As I am still inexperienced with this kind of troubleshooting, I feel it wouldn't be safe to just try out answers from other threads that don't have exactly the same 'history'.
Solutions I read included Ctrl+Alt+F4 and trying to login and get more information from the command line (Oh no! Something has gone wrong on restart).
Is that safe to do? Ideally, I'd like to save my data that is stored on an encrypted harddrive before trying to fix errors. I'd like to avoid reinstalling the OS.
From reading other threads, I know this post may be criticised as not being precise enough or haven't tried enough, but really I cannot get more information from that white screen myself and don't want to risk ruining everything just to provide more information...
Thank you for your help!! :)
Edit: I have no idea if the problem is related to lvm2-activation-generator, as in Ubuntu 19.10 “Something has gone wrong” after update from 19.04 This and other solutions include booting from a live usb. Can I do this 'safely' by simply switching the laptop off at this stage? Do I have to do sth before?
This will go a long way toward making that "Oh no something went wrong!" sign go away. First, press Ctrl+Alt+F3 to trigger the CLI, and login. Execute the command:
to continue upgrading. Your machine will install the missing resources, and finish upgrading, and then you just have to clean up and reboot:
Best of luck!
I had the same issue while upgrading my Ubuntu 18.04 to Ubuntu 20.04. some of the packages got crashed up. Mainly it is showing due to interruption of dpkg operations while booting the system.
Here's what I did to resolve this problem.
Firstly, press Ctrl+Alt+F3 together in order to open the terminal, then enter your login credentials and execute these following commands given below:-
This will resolve the problem of dpkg having been interrupted.
My question has been answered with the help of Ollie:
sudo apt-get update
returnedI tried to identify the process with
ps aux | grep -i apt
andps -aux | grep -iE "apt-get"
which didn't work, but I could identify it withpgrep focal
which gave me its process ID. I killed it withsudo kill <process_id>
.do-release-upgrade
worked for me only without the-y
option. It returnedThen I ran
sudo apt-get upgrade -y
and got the message0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded
. The 1 not upgraded was an expired libc++1 package.Rebooting the computer, Ubuntu 20.04 worked well.
I then installed the current version of this libc++1 package via Synaptic.
To solve this problem in my case, I used the recovery mode option in the GRUB menu and then selected the option to start a root shell. Then I ran these commands
I had wrongly installed this nvidia package that was causing my issues.
I had the same issue on ubuntu 20, I've tried many things but what worked for me was removing the gnome and gnome-shell and reinstalling:
similar to was described here. (but my problem wasn't my user)
First try to see if you can successfully login with another user account. If everything works, try deleting/moving the
.config
directory in your home folder.This will probably delete a bunch of settings which will go back to their default values; but it solved the issue for me.
I faced this problem and solved it by
First, go to tty:
Ctrl + Alt + F3
, and login.Then, as dpkg was locking things, I deleted all lock log files
as described here.
Finally, I resumed the release upgrade by following the steps given in this answer.
This worked for me.
Lets say you always login using: USER1
First check: If we can login to other user. Lets say other user: USER2
(Note: If you don't have another user, create a new user)
If you are successful in login using user USER2
Probably, this is issue of config file of the user.
Rename
~/.config
to~/.config.bak
.Then, try to login to that user
You can always get shell using CTRL+ALT+F2 and login with user.
Encountered the same problem updating from 21.10 to 22.04 had an unstable internet connection and encountered the oh no screen. I resolved my internet first, then what worked for me was
The enter login credentials after that run
sudo apt --fix-broken install
when I upgrade Ubuntu 20.04 to Ubuntu 22.04 this same error occurred on my laptop.
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover Please contact a system administrator
Atteched Screenshot
So I can forcibly reboot my laptop and then
Firstly, press Ctrl+Alt+F3 together in order to open the terminal, then enter my login credentials username first and then password and execute these following commands given below:-
apt --fix-broken install