Bug 425056 - KWin crashes/dies after resume from sleep
Summary: KWin crashes/dies after resume from sleep
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-05 23:36 UTC by Joe
Modified: 2022-11-03 02:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
curruption (1.29 MB, image/png)
2020-08-05 23:36 UTC, Joe
Details
journctl log (99.51 KB, text/plain)
2020-08-05 23:36 UTC, Joe
Details
Updated segfault on resume (16.27 KB, text/plain)
2020-08-16 03:29 UTC, Joe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe 2020-08-05 23:36:09 UTC
Created attachment 130673 [details]
curruption

SUMMARY

The compositor is now consistently dying for me on resume. I started getting a black screen and cursor on resume after updating (possibly the 450.57 nvidia driver upgrade). I had always had that issue on my laptops with nvidia cards, but never the desktop. To work around it, I disabled kscreenlocker. 

Now, with no screen locker, I get back to the desktop, but kwin/the compositor is dead and cannot be revived without a reboot (or dropping to a ttl and restarting sddm/x). Other issues include system settings having the left side blacked out, and other applications having similar corruption.I have attached screen shots and my journctl which includes the kwin seg fault. 

Should I also create a bug for the kscreenlocker issue? It seems pretty common on various forums searching around, but, I wasn't able to find an existing bug here for it.


STEPS TO REPRODUCE
1. Disable screen locker
2. Put system to sleep
2. Resume system

OBSERVED RESULT

Compositing is dead, black panels in various applications

EXPECTED RESULT

The system to resume fine.


SOFTWARE/OS VERSIONS

Arch Linux, Stable

Linux/KDE Plasma: 5.7.12-arch1-1 
(available in About System)
KDE Plasma Version:  5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

NVDIDA RTX 2080 Super/450.57, X11
Comment 1 Joe 2020-08-05 23:36:35 UTC
Created attachment 130674 [details]
journctl log
Comment 2 David Edmundson 2020-08-07 16:34:56 UTC
Can you confirm it still happens?

I had this when I first upgraded to 450.57 on my nvidia box, but after upgrading again today it seems to have sorted itself out.
Comment 3 Joe 2020-08-07 16:49:34 UTC
So funny enough, right after finally filling this, I have noticed all of my resume/suspends have been fine. However, I did just wake it up (after sleeping since yesterday), and while compositing/etc is working fine, SystemSettings still has the blacked out navigation panel. 

I can try updating everything again/restarting and continue to test and see if the SystemSettings issue still persists (I feel in the last major release SystemSettings in general has become rather flakey). 

David, do you think I should file a bug for the kscreenlocker issue? I haven't re-enabled it to test again, yet.
Comment 4 Joe 2020-08-16 03:29:38 UTC
Created attachment 130905 [details]
Updated segfault on resume
Comment 5 Joe 2020-08-16 03:31:02 UTC
OK, so, an update: The system settings issue never went away - it always has the black side bar after resume. The compositing being broken, however, did seem to fix itself - until I resumed today, at least, and now the compositor always breaks after resume again.

I have yet to try to ree-nable the screen locker, though, and see if the black screen w/ cursor persists.
Comment 6 Joe 2020-08-16 17:25:54 UTC
Played around a bit more - I can get to the compositing in system settings (even with the blackout, if you can guess the right place on the left nav it still works on click). Re-enabling the compositor doesn't work at all (it also has detection disabled). If I change to XRender and apply it does work again, but, either OpenGL 2 or 3.1 and it just crashes/breaks. Have to reboot to get it working again. I also noticed even after re-enabling auto detection, on reboot the compositor is still off, I have to manually go into system settings and reset everything to make it work again.
Comment 7 Joe 2022-11-03 02:29:39 UTC
So in general, I don't think this is happening anymore, and probably should be closed.