I can’t seem to find this problem on the web, so I’m posting here. I am running Fedora 42 on a Lenovo Thinkpad TP1G6. I upGRADED to Fedora 42 just fine. Then this past week, I applied an upDATE that included some kde stuff, kwin stuff, kf6 stuff, some plasma stuff and some qt6 stuff (among other things).
Rebooted and window system (KDE plasma) would not start. It hung on the FEDORA screen with the little cycler semicircle stuck in the left position (which is just where the window system usually launches). However, the system did boot and I was able to roll back.
I have since applied the nvidia updates. Plasma starts, though there’s a complaint about kwin crashing upon login (but otherwise ok). I updated the isolated packages that I could, one by one and all fine. So I’ve narrowed it down to the 100 packages associated with updating plasma (or any of the kde, qt6, etc. packages). Always hangs after reboot in the same way
So, here’s the request: I understand the info above is sorta nebulous and perhaps system-dependent. Thus, if someone could point me to the appropriate logs where I can see why plasma/kde doesn’t start that would be wonderful.
Alternatively, if you’ve had the same problem, pray do tell how you fixed it.
Try typeing ESC so that you can see the boot up messages.
Do you use an nvidia GPU?
If so the nvidia drivers maybe being built by akmods as you boot up.
This is a slow process and you should see the akmods service messages on the console.
Leave the system to complete the build, which can take a number of minutes.
Then the system should complete the boot up and allow you to login.
Thanks – I always let akmods fully complete the builds. Also, there’s (in recent releases) a failsafe that does not let you reboot until akmod has done its magic ). So that’s probably not the issue.
I’ll try the esc (where exactly – in the hung display, maybe?) and see what that yields.
Thanks, LordByte I’ll try and see – it downgraded 126 packages for me (obviously depends on what I have loaded already). We’ll see if it now boots (I suspect it will since the things it downgraded where qt6, kde and plasma -related.
I THINK we can close this out – the new update (4/29-30/2025) seems to have fixed the problem with qt6 and kde/plasma starts up after reboot.
I did have an odd gdb (gnudebug) instance (repeatedly) that ate up some resources. It was started using my UID (I didn’t invoke it directly) but other than that, all good!
