Bug 477863

Summary: When opening Logout Screen while overview is on, Plasma freezes
Product: [Plasma] kwin Reporter: Akseli Lahtinen <akselmo>
Component: effects-overviewAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, nate
Priority: NOR    
Version First Reported In: git-stable-Plasma/5.27   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Akseli Lahtinen 2023-12-01 20:24:09 UTC
SUMMARY

Typing "Shut down" and selecting it in overview, when Logout Screen is enabled, will freeze Plasma session

STEPS TO REPRODUCE
1. Make sure Logout Screen is toggled on in Desktop Session settings
2. Open overview
3. Type Shut down/logout, anything that opens the Logout Screen

OBSERVED RESULT
Plasma freezes. It takes some time but usually starts working again after some waiting.

EXPECTED RESULT
Overview would close and Plasma would not freeze

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.6.2-201.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

ADDITIONAL INFORMATION

This also happens in Plasma 6. I think it's very likely due to Overview effect and Logout Screen effect colliding somehow. It feels like Overview effect is not closed properly when Logout Screen appears.
Comment 1 Nate Graham 2023-12-13 17:17:32 UTC
This is a dev session issue; the same one that causes the logout screen to appear blank when triggered with any of the UI elements that show it, rather than running `~/kde/usr/lib64/libexec/ksmserver-logout-greeter --windowed` manually to force it to launch the Plasma 6 version of the binary.

This was discovered by reproducing the bug as you described it, and then later entering `~/kde/usr/lib64/libexec/ksmserver-logout-greeter --windowed` in the Overview effect's search field; that works properly.

Thus it is a duplicate of Bug 462824.

*** This bug has been marked as a duplicate of bug 462824 ***