#190 Fedora Kinoite 36 Beta - Crashes shortly after logging in
Closed: Fixed 2 years ago by siosm. Opened 2 years ago by jwillikers.

Fresh install of the Fedora Kinoite 36 Beta on an Intel NUC system, Intel Iris Xe graphics.
When I log in to the system, everything works for about 30-60 seconds before it freezes and the entire system is unresponsive.
I didn't have a chance to install / update anything.
Switching to a console log in before logging in to the graphical environment allows me to log in without the system crashing.


Metadata Update from @ngompa:
- Issue tagged with: kinoite

2 years ago

Can you get some logs or try other editions of Fedora to see if this is specific to Kinoite or KDE?

Can you get some logs or try other editions of Fedora to see if this is specific to Kinoite or KDE?

It runs GNOME on Silverblue just fine.
I can try running KDE on there when I get time.
As for the logs, I haven't been able to find anything of particular note in the system journal or the user journal.
I'm not sure if there's a particular KDE systemd unit or units I should be checking?

@siosm The Fedora 36 Beta KDE spin crashes in the exact same way. Everything seems to freeze a minute or so after logging in to a desktop session. Opening Konsole and following the user journal shows no errors.

QSocketNotifier: can only be used with threads started with QThread
Started plasma-baloorunner.service , KRunner provider for baloo file indexer.

The only other hint I notice is that the computer will spin up the fan pretty heavily right before it freezes, as if it is checking for updates in the background. The update icon in the bottom right-hand corner shows up before it freezes.

I can also replicate this on Fedora 36/35. While the OS completely invariably and completely freezes (no tty, does not respond to pings) a few minutes after booting, it strangely does not crash if there are any usb devices plugged in. Also, journald logs abruptly end when the system crashes - there is no hint as to the cause of the crash.

This issue no longer occurs after updating system firmware

This is going to be difficult to diagnose without more info. Closing but feel free to re-open if you have more.

Metadata Update from @siosm:
- Issue close_status updated to: Can't fix
- Issue status updated to: Closed (was: Open)

2 years ago

Issue status updated to: Open (was: Closed)

2 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Kinoite Status: Done