| Summary: | Switching to an already logged-in user causes Plasma to display a black screen with no cursor | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | zupnikszydlik |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | kdedev, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
journalctl log 1
journalctl log 2 gdb log |
||
|
Description
zupnikszydlik
2025-11-10 15:29:32 UTC
Thanks for the bug report. When this happens, are you able to get to a TTY with Ctrl+Alt+F3? If so, can you check kwin's logs: journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt Also, could you retrieve kwin's backtrace while the bug is happening? You might need to ssh from another computer and attach a debugger to kwin process if it's hung, e.g. sudo gdb -p $(pidof kwin_wayland) then type bt then press 'c' if it asks you if you want to continue paging Then copy-and-paste the output here. Thanks! Created attachment 186782 [details]
journalctl log 1
Created attachment 186783 [details]
journalctl log 2
Created attachment 186784 [details]
gdb log
trying to get information using gdb
I created the logs you asked about: first with my daily account, and second with the breeze-only theme. Regarding gdb: I tried, but I’m not very familiar with debugging, sorry. I used a second computer with SSH. Every time I tried to debug, nothing really happened. I logged into the account, ran gdb, and always got the same output (which I don’t think is very useful). In the gdb session I used "bt", then repeated "bt" after 30 seconds. Afterwards I used "c" (as I read in the manual it continues the program), but mostly nothing happened. In the attached log I got information about 4 threads, but most of the time after entering "c" there was no reaction. After about one minute without any response I quit gdb. What is interesting is that I was able to return to the login screen by switching between ttys (e.g. tty3, tty2, and tty1 — the one with the login screen). Through SSH I checked what happens after clicking the "Switch user" option and logging into the same account: the screen stayed black, but I could see two login processes. After entering the password there were two ""/usr/bin/startplasma-wayland processes"", one on tty1 and another on tty4. Logging in → Select "Switch user" → Go back to login screen [radek@radek-komp ~]$ w 14:42:16 up 27 min, 5 users, load average: 0,16, 0,14, 0,13 UŻYTK. TTY ZAL.OD BEZCZ. JCPU PCPU CO radek tty1 14:15 27:21 0.03s 0.03s /usr/bin/startplasma-wayland radek pts/2 14:19 0.00s 0.01s 0.01s w Selecting to log into the same account: [radek@radek-komp ~]$ w 14:42:27 up 27 min, 6 users, load average: 0,12, 0,14, 0,13 UŻYTK. TTY ZAL.OD BEZCZ. JCPU PCPU CO radek tty4 14:42 27:32 0.04s 0.04s /usr/bin/startplasma-wayland radek tty1 14:15 27:32 0.03s 0.03s /usr/bin/startplasma-wayland radek pts/2 14:19 0.00s 0.01s 0.01s w It stayed like this (black screen, no login option): [radek@radek-komp ~]$ w 14:42:44 up 27 min, 6 users, load average: 0,10, 0,13, 0,13 UŻYTK. TTY ZAL.OD BEZCZ. JCPU PCPU CO radek tty4 14:42 27:49 0.04s 0.04s /usr/bin/startplasma-wayland radek tty1 14:15 27:49 0.03s 0.03s /usr/bin/startplasma-wayland radek pts/2 14:19 0.00s 0.01s 0.01s w After switching between ttys and returning, USER's login screen showed up and I had to enter my password again (that one that shows up after Meta+L): [radek@radek-komp ~]$ w 14:42:56 up 28 min, 6 users, load average: 0,08, 0,12, 0,12 UŻYTK. TTY ZAL.OD BEZCZ. JCPU PCPU CO radek tty1 14:15 28:01 0.03s 0.03s /usr/bin/startplasma-wayland radek pts/2 14:19 0.00s 0.01s 0.01s w Thanks for the additional details, that's really helpful. I'll let those more knowledgeable about this code look further. Can you paste the output of `cat /etc/sddm.conf`? |