Hi, after a reboot I'm now greeted by a white screen saying Oh no! Something has gone wrong A problem has occurred and the system can't recover. Please contact a system administrator.
I can still switch to a different tty, but I can't really tell what the issue is. The output of journalctl -b --priority 3 is: kernel: cros_ec_lpcs cros_ec_lpcs.0: EC ID not detected bluetoothd[894]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. bluetoothd[894]: sap-server: Operation not permitted (1) bluetoothd[894]: Failed to load LTKs for hci0: Invalid Parameters (0x0d) systemd[1]: Failed to start firewalld.service - firewalld - dynamic firewall daemon. csc_vpnagent[961]: Function: startParser File: ../../vpn/Common/Xml/CVCSaxParser.cpp Line: 171 Invoked Function: xmlCreateFileParserCtxt Return Code: -33554427 (0xFE000005) Description: GLOBAL_ERROR_NULL_POINTER csc_vpnagent[961]: Function: LoadSettingsFromXmlFile File: ../../vpn/PhoneHome/PhoneHomeAgent.cpp Line: 626 Invoked Function: XmlParser::parseFile Return Code: -33554423 (0xFE000009) Description: GLOBAL_ERROR_UNEXPECTED gnome-session-binary[1447]: Unrecoverable failure in required component org.gnome.Shell.desktop kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5) gnome-session-binary[1618]: Unrecoverable failure in required component org.gnome.Shell.desktop gnome-session-binary[1618]: Unrecoverable failure in required component org.gnome.SettingsDaemon.UsbProtection.desktop kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110) login[2018]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory PAM adding faulty module: pam_lastlog.so Now, the first line can just be ignored, that's typical. The things that concern me the most are the last two lines. It already has been reported as a bug and seems to be in the works, but I haven't seen any inidcation that this should cause a complete failure. The other reasons I've found for the Gnome related error message was either trouble with Nvidia - but I don't have any installed - or outdated firmware. So I've just made double shure to really have the latest firmware by copying over the 04/2024 archive from kernel.org with rsync -rc, yet no change (I'm running on a Ryzen 7040, so the AMD firmware available in the Debian repos is way too old, no matter which branch). So what's going on? Best Richard
