24.04 beta: Subiquity fails with "Something went wrong"

Bug #2061180 reported by Hadmut Danisch

This bug report will be marked for expiration in 10 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
Incomplete
Undecided
Unassigned

Bug Description

Hi,

I was trying to freshly install today's Ubuntu 24.04 beta Desktop on a Fujitsu U727 Notebook with Core i5-6200U and 8GB RAM. (.iso on USB pen drive)

Live-Desktop comes up.

When starting the Installer, no matter whether the link on the desktop or the one in the left quickstart panel, I immediately get a window with an error message "Something went wrong".

and

"We're sorry, but we're not sure what the error is."

Unfortunately, I am not sure either.

Revision history for this message
Dan Bungert (dbungert) wrote :

Hi Hadmut Danisch, thanks for the report.

There isn't much to go on here, or even that the failure was related to the Installer itself. At that crash dialog should be an option to collect data and report, or if that isn't happening, a tarball of the contents of /var/log/installer would be good. With that information we can start to debug.

Changed in subiquity (Ubuntu):
status: New → Incomplete
affects: subiquity (Ubuntu) → subiquity
Revision history for this message
Hadmut Danisch (hadmut) wrote :

That hint was good. The machine is not running anymore, I've installed Kubuntu 24.04 beta meanwhile, but fortunately used another USB pendrive.

On the pendrive I used for the installation with the crash I found a log directory, which I'll attach.

Revision history for this message
Hadmut Danisch (hadmut) wrote :
Dan Bungert (dbungert)
Changed in subiquity:
status: Incomplete → New
Revision history for this message
Hadmut Danisch (hadmut) wrote :

The kernel log mentions lines like

python3.10[11739]: segfault at 1 ip 00007ea0a0d55720 sp 00007ffdb18770f0 error 4 in _nl80211.cpython-310-x86_64-linux-gnu.so[7ea0a0d55000+2000] likely on CPU 1 (core 1, socket 0)

Revision history for this message
Dan Bungert (dbungert) wrote :

Hi Hadmut,

Thanks for the logs.

I can see that the installer process is crashing multiple times a second. That's definitely not normal!
 I'm considering the possibility that you have a bad ISO download or a bad USB drive.

From your updates it sounds like you handled that already and used a different usb drive.
I think we can call this resolved and close this bug. If you were to try to plug your original key into a device and boot it I wager you'd see the same result, but don't feel obligated. I'm going to mark the bug incomplete for now, which will let the bug close in 60 days, and if we get more info we can reverse that.

Changed in subiquity:
status: New → Incomplete
Revision history for this message
Hadmut Danisch (hadmut) wrote :

I've verified the download against SHA256SUMS before writing to the USB drive.

The drive is quite new, I bought 20 of them, and never had any problem with any of them. I used a different one, because I have pendrives labeled with "Ubuntu Desktop", "Server", "Lubuntu", "Kubuntu". That's why I used a different one for installation of Kubuntu.

Maybe just wait a while whether there's more reports or not. If it's a real bug, there should be more reports coming in or people hitting "bug affects me".

Today it's late, and tomorrow I'm busy. Maybe on sunday or monday.

Revision history for this message
Dan Bungert (dbungert) wrote :

> I've verified the download against SHA256SUMS before writing to the USB drive.

OK good, we can rule out that part.

> The drive is quite new, I bought 20 of them

It might be worth trying writing that same ISO then to a different drive, and leaving the one that I suspect to the side.

> Maybe just wait a while whether there's more reports or not. If it's a real bug, there should be more reports coming in or people hitting "bug affects me".

I strongly agree. I chose to mark it "incomplete" here so that it would timeout if this appears to be a one-off glitch, or it should be easy to find again if we have reports that look similar.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.