Created attachment 181996 [details] Panel responsive then unresponsive when changing window mode SUMMARY When i was playing doom eternal if i changed to a different window mode like fullscreen, borderless etc my panel on my second 60hz 1080p hdmi monitor would go unresponsive until i closed the game STEPS TO REPRODUCE 1. Play Doom Eternal 2. Change to fullscreen or borderless 3. Keep changing until the panel becomes unresponsive on a second or third monitor OBSERVED RESULT Panel becomes unresponsive until game is closed EXPECTED RESULT Panel to not be unresponsive SOFTWARE/OS VERSIONS Linux/KDE Plasma: Cachyos KDE Plasma Version: 6.3.91 KDE Frameworks Version: 6.9.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION
Just the panel on the external screen? Or does it also affect all of Plasma (i.e. also the panel on the main screen and also the desktop)?
(In reply to Nate Graham from comment #1) > Just the panel on the external screen? Or does it also affect all of Plasma > (i.e. also the panel on the main screen and also the desktop)? sorry yes the main screen and desktop on that monitor stop working until i close the game aswell, this happens on my rtx 2060 also not just my amd card if thats worth anything
Please attach kwin's and plasmashell's logs. Run the following commands in terminal journalctl --boot --user-unit plasma-kwin_wayland > kwin_wayland.log 2>&1 journalctl --boot --user-unit plasma-plasmashell > plasmashell.log 2>&1 and then attach kwin_wayland.log and plasmashell.log to this bug report. What GPU do you have? If you disable VRR in system settings, does it make any difference?
Created attachment 182139 [details] kwin log
Created attachment 182140 [details] plasmshell log
(In reply to Vlad Zahorodnii from comment #3) > Please attach kwin's and plasmashell's logs. Run the following commands in > terminal > > journalctl --boot --user-unit plasma-kwin_wayland > kwin_wayland.log 2>&1 > journalctl --boot --user-unit plasma-plasmashell > plasmashell.log 2>&1 > > and then attach kwin_wayland.log and plasmashell.log to this bug report. > What GPU do you have? If you disable VRR in system settings, does it make > any difference? I have a RX 6700 10GB and disabling vrr doesn't solve the problem
This is reported against 6.3.91. Is it a regression or pre-existing issue in 6.3?
(In reply to Vlad Zahorodnii from comment #7) > This is reported against 6.3.91. Is it a regression or pre-existing issue in > 6.3? sorry this is a per-existing issue after testing 6.3.5 on a different distro
Update on this issue, when forcing wine wayland on the game instead of it running under xwayland this issue doesn't occur anymore(but there is a wine wayland bug with this game also which is heavy flickering) so either when wine wayland gets enabled as default this will be closed or this issue gets fixed with xwayland at some point.
Please get a backtrace of plasmashell while it's unresponsive > sudo gdb -p $(pidof plasmashell) > bt
This is what i was able to get, the application launcher also was able to freeze on me and wouldn't launch either if i did it enough times with changing borderless and fullscreen back and fourth. [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x00007fbdb64b2e42 in ?? () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007fbdb64b2e42 in ??? () at /usr/lib/libc.so.6 #1 0x00007fbdb64a64df in ??? () at /usr/lib/libc.so.6 #2 0x00007fbdb6533c43 in ppoll () at /usr/lib/libc.so.6 #3 0x00007fbdb55aae50 in ??? () at /usr/lib/libglib-2.0.so.0 #4 0x00007fbdb55aaf32 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x00007fbdb70a4a1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #6 0x00007fbdb6d8dc46 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #7 0x00007fbdb6d83fa9 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #8 0x000055693ba560ce in ??? () #9 0x00007fbdb6427b0b in ??? () at /usr/lib/libc.so.6 #10 0x00007fbdb6427bbb in __libc_start_main () at /usr/lib/libc.so.6 #11 0x000055693ba565f5 in ??? () (gdb) bt #0 0x00007fbdb64b2e42 in ??? () at /usr/lib/libc.so.6 #1 0x00007fbdb64a64df in ??? () at /usr/lib/libc.so.6 #2 0x00007fbdb6533c43 in ppoll () at /usr/lib/libc.so.6 #3 0x00007fbdb55aae50 in ??? () at /usr/lib/libglib-2.0.so.0 #4 0x00007fbdb55aaf32 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x00007fbdb70a4a1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #6 0x00007fbdb6d8dc46 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #7 0x00007fbdb6d83fa9 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #8 0x000055693ba560ce in ??? () #9 0x00007fbdb6427b0b in ??? () at /usr/lib/libc.so.6 #10 0x00007fbdb6427bbb in __libc_start_main () at /usr/lib/libc.so.6 #11 0x000055693ba565f5 in ??? () (gdb)
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.