Bug 488603 - Screen freezes with compositor enabled - Nvidia Optimus
Summary: Screen freezes with compositor enabled - Nvidia Optimus
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 6.0.5
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-16 22:12 UTC by Oleksii Zolotarevskyi
Modified: 2025-03-25 20:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleksii Zolotarevskyi 2024-06-16 22:12:16 UTC
SUMMARY
After updating to Plasma 6 the screen sometimes freezes for ~10 seconds when trying to interact with the Desktop.
After disabling the compositor the issue doesn't happen.

STEPS TO REPRODUCE
1. Interact with Plasma Desktop, e.g. click on the item in the system tray.

OBSERVED RESULT
The whole desktop becomes unresponsive, only the mouse pointer is functional. The reaction to the mouse clicks and the keyboard presses during the freeze only happens after the feeze is over (seems like all inputs are registered). 

EXPECTED RESULT
Desktop doesn't freeze.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Graphics Platform: X11
Graphics Driver Version: Nvidia 550.78

ADDITIONAL INFORMATION
Optimus laptop with Nvidia set as primary GPU.
Somehow it happens when I switch from the external screen to a laptop screen. Almost doesn't happen with the external screen.

Messages in the system log:
Jun 13 23:04:09 user-tuxedo kwin_x11[13295]: kwin_core: XCB error: 152 (BadDamage), sequence: 31955, resource id: 21020632, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Jun 13 23:04:09 user-tuxedo kwin_x11[13295]: kwin_core: XCB error: 3 (BadWindow), sequence: 31956, resource id: 67109049, major code: 129 (SHAPE), minor code: 6 (Input)

The messages from plasmashell (restarted from Konsole):
QRhiGles2: Context is lost.
Graphics device lost, cleaning up scenegraph and releasing RHI
Comment 1 TraceyC 2025-03-25 20:01:25 UTC
Can you get a backtrace of what plasmashell is doing when it's hung? You'll need to run this either from TTY or ssh'd into the system, since the desktop freezes.

Run gdb attach -p $(pidof plasmashell) in a terminal while it's hung
If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
When you see a prompt that says "(gdb)", type "bt" and press the enter key.
If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
Copy-and-paste the contents of the terminal window into a comment here.

Thanks!