This morning’s TW update prevented me from getting to my login screen. Anyone else encounter this problem?
I fixed it on my system with a snapshot rollback.
Solution was a rollback.
It actually seems that using lightdm instead of sddm also is a solution, if you don’t want to rollback.
At least on my system it worked.
I’m a tech noob. I don’t know what lightdm or sddm is. I hired an online Linux expert to help me fix it.
Don’t worry. We’ve all learned along the way.
Both sddm and lightdm are display managers. Basically they are what you see when you get to the graphical login prompt.
After powering on my monitor and a login attempt the login screen just sits there.
dmesg -wH shows:
[Oct19 23:18] [ T44403] kscreenlocker_g[44403]: segfault at 105 ip 00007f379c69df50 sp 00007ffe89dd8970 error 4 in libQt6Qml.so.6.8.0[29df50,7f379c4f1000+3d5000] likely on CPU 3 (core 3, socket 0)
[ +0.000011] [ T44403] Code: ff ff 48 8b 44 24 08 64 48 2b 04 25 28 00 00 00 0f 85 b1 00 00 00 48 83 c4 18 48 89 d8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 90 <4d> 8b 2c 24 4d 8b 75 10 41 80 7e 0d 00 74 11 4c 89 e6 e8 69 d6 ef
[Oct20 08:46] [ T46501] traps: kscreenlocker_g[46501] general protection fault ip:7f6ec5007768 sp:7ffe496a7ec0 error:0 in libQt6Qml.so.6.8.0[207768,7f6ec4ef1000+3d5000]
Switching TTY, pressing ESC or switching user seems to speed things up.
Additionally, my screen brightness went way way up, had to half it in monitor settings, not sure if related.
Do you find information according to a topic like “Change display manager” helpful for your use case? 
I’m a noob so I don’t really know what a display manager is and I don’t want to mess mess with it unless an expert is helping me and prevents big mistakes.
Do you find any further information interesting from existing bug reports?
Would you like to become more familiar with the system configuration for such a software component?
The experiences will evolve accordingly, won’t they?
Can you offer any more background information for this error situation?
Various experience reports were published also according to such an issue.
It seems to be “nice” that you can use such a system configuration option for a while.
Will any other solution approaches become more interesting?
Update: The remote Linux expert was unable to fix the issue. He thinks it’s something to do with the GPU graphics drivers. He said I’ll need to find a local expert. I’m now trying to find one.
- Would you like to share any more technical details from the affected system?
- Do you need further guidance according to better error reporting?
Your problem appears to be quite different from that in the OP here. You should open a new thread. Posting in a thread supposedly solved via rollback will cause fewer people to see yours, reducing potential for the help you seek.
You could if you really wanted to.
https://en.wikipedia.org/wiki/X_display_manager
A rollback, without more, is a workaround, not a solution.
Problem fixed. I hired a remote Linux expert and he found that, for some unknown reason, one of my USB drives was specified as auto-mount in the FSTAB file. We have no idea how this happened. He removed it from fstab and then I installed the big TW update (4GB!) and my system rebooted fine (took about 15 minutes to reboot as TW digested 4GB of updates). Now I’m back to normal.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.