Random Lockups

Wondering if anyone else is seeing random lockups with F38 both before GDM—e.g., at the splash screen—and, occasionally, just after login/before GNOME Shell loads?

My logs have some items that seem weird to me, like “Connector ‘dbus’ not found,” “usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1,” and “ucsi_acpi USBC000:00: PPM init failed (-110).” I can provide a full output if that helps. I also noticed this one with dmesg:

dconf worker[4145]: segfault at 7f7044001038 ip 00007f70628bf35b sp 00007f70527fc3e0 error 6 likely on CPU 4 (core 4, socket 0)

That was seems a bit worrying, just at first glance and without me knowing very much about, well, anything.

If someone could aim me to some ways to investigate further and/or which logs would be most helpful, I’d gladly post them.

Thanks, in advance!


This is a Fedora 38 install, running GNOME Shell and Wayland, with the 6.3.12-200.fc38.x86_64 kernel; however, it was occurring on prior kernels as well. The system just locked up during routine use and nothing could make the system respond, including the “magic” SysRq “raising elephants is so utterly boring” sequence.

Random crashes can be caused by vendor firmware, overheating, evil cables and connectors, and memory failures. Routine cleaning of heatsinks and fans helps prevent overheating. Inspecting and reseating cables and connectors may help. You can get “contact enhancer” at auto parts stores (I used to get it from Radio Shack – now that cars run on CPU’s it is essential for auto repair shops).

Some models have design problems with cooling or connectors that may be discussed in vendor forums.

See memtest86+.

I’ve previously opened the case on this particular device—an Asus Zenbook 14, the UX425IA variety—and already cleaned a bit; to be honest, there was a lot less dust than I expected. I don’t think that’s the particular issue.

Having completely forgotten memtest86+ exists, I appreciate that reminder. What would make you think this could be a memory issue?


Memtest86+ test passed with flying colors, so it’s nothing there…

Sometime it takes several passes with a memory test to reveal a problem. I’d want to run the test for a period 2x longer than a typical time between the crashes.

When you have multiple crashes involving different processes you need to look at lower level code and devices shared by many applications.

The next step should be a hard look at device firmware Fedora doesn’t provide, in particular SSD’s, docking stations, and “BIOS”.

One troubleshooitng technique is to try running with alternative devices (wired network instead of wifi, integrated graphics instead of GPU, wired keyboard and mouse instead of bluetooth, etc.).

So, after running a few more memory tests with a variety of variables, all passed without error.

I don’t use a docking station and I haven’t made any changes to the BIOS to cause a new issue. I’ve also played around on both wired and wireless connections and see lockups on both.

BIOS may need updating for new linux kernels/drivers, so it is not changes to BIOS that cause problems, but rather lack of the changes needed to continue working with current kernels and drivers.

Sorry, I should have mentioned checking for BIOS updates was something I already did…

This should be resolved by Commit - rpms/flatpak - 2e0f03b2a71f8dfc4ac5942ee4a1e0f6f7cb2212 - src.fedoraproject.org and should be an issue for anyone who has flatpak installed on a non-ostree variant of Fedora.

Is there anything useful injournalctl -b -1 -p "err" after a reboot to recover from the issue?

Did you try using a USB keyboard vice the laptop keyboard?

Interesting about the flatpak piece…

I just experienced another lockup, immediately after trying to login at GDM; the resulting journalctl command provided this, which I’m not sure provides any useful information…

Jul 22 11:49:57 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\SMIB], AE_ALREADY_EXISTS (20221020/dsfield-637)
Jul 22 11:49:57 asus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.WLAN], AE_NOT_FOUND (20221020/dswload2-162)
Jul 22 11:49:57 asus kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
Jul 22 11:50:02 asus kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
Jul 22 11:50:02 asus kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 22 11:50:03 asus kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jul 22 11:50:04 asus (sd-execu[582]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.
Jul 22 11:50:06 asus abrtd[950]: '/var/spool/abrt/oops-2022-03-29-13:31:59-911-0' is not a problem directory
Jul 22 11:50:06 asus kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 22 11:50:11 asus kernel: iwlwifi 0000:01:00.0: Not associated and the session protection is over already...
Jul 22 11:50:13 asus gdm-password][1857]: gkr-pam: unable to locate daemon control file
Jul 22 11:50:14 asus dbus-broker-launch[1983]: Ignoring duplicate name 'org.gnome.Shell.Extensions.GSConnect' in service file '/usr/share//dbus-1/services/org.gnome.Shell.Extensions.GSConnect.service'
Jul 22 11:50:14 asus systemd[1923]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2117.scope - Application launched by gnome-session-binary.
Jul 22 11:50:16 asus dbus-broker-launch[1983]: Ignoring duplicate name 'org.gnome.Shell.Extensions.GSConnect' in service file '/usr/share//dbus-1/services/org.gnome.Shell.Extensions.GSConnect.service'
Jul 22 11:50:22 asus bluetoothd[891]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

I have tried both a USB keyboard and mouse…