Question

7

After Upgrade to Ubuntu 20.04: "Oh no! Something went wrong"

rated 0 times [ 7] [ 0] / answers: 1 / hits: 72079 / 3 Years ago, mon, september 27, 2021, 7:21:02

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?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

measord

Add To Favorites

Follow

Total Points: 259

Total Questions: 131

Total Answers: 106

Location: Venezuela

Member since Sun, Oct 2, 2022

2 Years ago

answered 3 Years ago uxuriousrnal · Accepted Answer

My question has been answered with the help of Ollie:

sudo apt-get update returned

Could not get lock /var/lib/apt/lists/lock. It is held by process 22027 (focal)

I tried to identify the process with ps aux | grep -i apt and ps -aux | grep -iE "apt-get" which didn't work, but I could identify it with pgrep focal which gave me its process ID. I killed it with sudo kill <process_id>.

do-release-upgrade worked for me only without the -y option. It returned

There is no development version of an LTS available.

To upgrade to the latest non-LTS development release

set Prompt=normal in /etc/update-manager/release-upgrades

Then I ran sudo apt-get upgrade -y and got the message 0 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.