Ubuntu
ubiquity package

Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to connect

Bug #2060920 reported by Daniel van Vugt

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

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Noble installer (20240410) crashes on Raspberry Pi 400. No slideshow commenced, no user account created. Can't log in.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060920

tags: added: iso-testing
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you have any log from the installation / crash?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No I couldn't open a terminal or log into a VT. Now trying to reimage...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Crashed on the second attempt too. Seems the issue that led up to both crashes was that WPA3 isn't supported and it will either hang forever, crash, or crash after you give up on the hang and try to abort wifi connecting.

I've now got past the crashes by just booting with ethernet connected instead.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
summary: - Noble installer crashes on Raspberry Pi 400
+ Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to
+ connect
Changed in ubiquity (Ubuntu):
importance: Critical → Medium
Revision history for this message
Prof. Schniepp (schniepp) wrote :

Same (or similar) happened to me on a Pi 5. Tried daily images from 4/17 and 4/14.

On the 4/17 image I was asked for keyboard, type, time zone, WiFi connection, username and password during GUI installation. However, the installer then crashes with a GUI error message. It then goes to a GUI login screen, but the username/password combination created earlier don't work for login. (Probably the account is never created.) I could not find a default username/password combination that I could use to log in.

Revision history for this message
Dave Jones (waveform) wrote :

I *think* you may have run into the issue with the installer crashing on the timezone selection screen (which is directly after network selection and which had a fatal issue with an out of date library; LP: #1987454). That issue is now corrected on the current daily (from 4/22 which I'm ISO testing as a release candidate), and I'm unable to replicate a full crash when attempting to connect to a WPA3 AP. Rather, it just sits there and fails to connect to the AP.

Incidentally, we do now have the firmware blobs that *allegedly* support WPA3 on the BCM43455 (used on the 3A+, 3B+, 4B, and 5) but apparently they only work with WPA3 under iwd (not wpa_supplicant) currently.

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

Other bug subscribers

Remote bug watches

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