[plasma-login-manager] [Bug 524347] New: Resuming an already-active session via user switch freezes the screen (Wayland, NVIDIA)

https://bugs.kde.org/show_bug.cgi?id=524347

            Bug ID: 524347
           Summary: Resuming an already-active session via user switch
                    freezes the screen (Wayland, NVIDIA)
    Classification: Plasma
           Product: plasma-login-manager
      Version First 6.7.3
       Reported In:
          Platform: CachyOS
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
  Target Milestone: ---

Created attachment 195204
  --> https://bugs.kde.org/attachment.cgi?id=195204&action=edit
loginctl, coredumpctl, journalctl over a few boots, tracking the issue

DESCRIPTION

Switching between multiple users works - the first time (when logging in).
Switching *back to an active session* reliably causes issues.
Most notably, my display freezes and I can no longer interact with anything. I
end up having to power cycle/REISUB to restart.


STEPS TO REPRODUCE

1. Boot up
2. Log in to user#1
    - Note: here I have a few apps running: Firefox, Steam, Zed, Discord
3. Switch User
4. Log in to user#2
5. Switch User
6. Select user#1 and put in password to resume session

OBSERVED RESULT

Screen Freezes

EXPECTED RESULT

I resume the user #1's session with all visual configuration working as per the
first login/session

SOFTWARE/OS VERSIONS

Operating System: CachyOS Linux
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.5-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 64 GiB of RAM (61.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2080 SUPER

ADDITIONAL INFORMATION

Possibly related to Bug 522655
Note: I previously had autologin turned on, and have since turned it off.
`grep`ing for it showed no traces, but the symptoms are otherwise similar.

Note: user#1 = vikram, user#2 = work

When I was trying to figure out what was going on, I managed to get the screen
to resume once.
I did this by closing almost every GUI app before step 3 of the repro (first
Switch User from #1 to #2).
I was then able to log back in, but HDR didn't resume properly (screen faded
out). After turning off HDR, things looked right.
I could then use Ctrl+Alt+Fn to switch between users. It worked for a while
(~30 minutes), and at some point, I pressed Ctrl+C (possibly unrelated?) and
*it booted me from User#2 back to User#1*, and Ctrl+Alt+Fn didn't work to
switch me back. I had to switch user, log in as User#2, and _then_ it froze -
once again resuming an active log in. Weirdly, I was able to resume my discord
_audio_ call I was in, but then I had to power cycle to continue using my PC.

I had a clanker help me mine my journal for some info, I've attached it as
diag.txt
I am able to reproduce this, so if you need anything else, let me know.
For now, I have to fully log out to switch users. Or reboot...

After reviewing the above for completeness, the clanker wanted to add this to
the above report:
No backtrace available: coredumpctl shows no core dumps for kwin_wayland or
plasma components; the second session's end was a clean exit (helper code 2),
not a crash.
While a second session exists, the inactive session's kwin_wayland continuously
logs "atomic commit failed: Permission denied" and "drmModeListLessees()
failed: Permission denied" (see diag.txt); after the session death, the next
login was assigned VT 4 rather than reusing VT 3.

-- 
You are receiving this mail because:
You are watching all bug changes.