| Summary: | Compositing gets disabled by crashes and never re-enables itself absent manual intervention | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | nonouser |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kde.org, nate, plasma-bugs |
| Priority: | HI | Keywords: | regression, usability |
| Version: | 5.20.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Compositor - System Settings OpenGL warning.
kwin --replace output after crash Kwin kcrash file of 2021-01-30 |
||
|
Description
nonouser
2021-01-24 14:24:43 UTC
Seems like the compositor got turned off. If you hit Alt+Shift+F12, do these things start working again? (In reply to Nate Graham from comment #1) > Seems like the compositor got turned off. If you hit Alt+Shift+F12, do these > things start working again? Alt+Shift+F12 seems to do nothing on my machine. By compositor you mean kwin right? I tried restarting it with "kwin --replace" but no luck. The problem persists. On X11, KWin can either do compositing, or not. When compositing is turned off, the system exhibits the symptoms that you're reporting. Can you go to System Settings > Display and Monitor > Compositor and see if "Enable compositor on startup" is checked? Created attachment 135239 [details]
Compositor - System Settings OpenGL warning.
It was turned off along side a message about OpenGL compositing crashing kWin in the past.
I re-enable OpenGL detection and enable compositor on startup and everything is up and running.
I hadn't touch any of this setting though, it seems a crash has disabled them. I joined an image to the bug report as an attachment so you can see the warning.
It says it might be a driver bug, I have the Latest Legacy GPU version (390.xx series) cause I have an old GPU (GTX 560) in the legacy list.
Do you think it's ok to update to one of the latest driver versions 455 or 460?
No comment about driver versions as I don't use Nvidia hardware and am wildly ignorant about anything Nvidia-related. :) Since re-enabling compositing works, it seems like there's a KWin bug here in that compositing should not get totally disabled in the first place. That's pretty intrusive, and demands manual intervention from the user to re-enable compositing that they likely will not know how to perform (hence this bug report). Moving to KWin. Thanks for your help and advice. I see you moved it to kwin, but since I don't have any logs or crash information, is it useful to leave this open or should I close it? Let's leave it open. Created attachment 135274 [details] kwin --replace output after crash After using kwin for awhile it crashed again. I got the same massage in "System Settings > Display and Monitor > Compositor" I re-enable OpenGL detection and relaunched kwin. That promptly crashed again, I saved the output and added as an attachment. (see attachment) Because a crash happened the crash handler opened but I was unable to get any info. In the crash handler the "Developer Information" tab says "The debugger has quit unexpectedly. The crash information could not be generated." Clicking reload gives the following output. > Freeze in OpenGL initialization detected > Unable to start Dr. Konqi > ptrace: No such process. > /tmp/drkonqi.XsYgub:2: Error in sourced command file: > No symbol table is loaded. Use the "file" command. > /tmp/drkonqi.YcJicb:1: Error in sourced command file: > No thread selected Created attachment 135316 [details]
Kwin kcrash file of 2021-01-30
kwin crashed again this time the crash handler was able to create a kcrash log.
(see attachment)
Can you try to reproduce the issue with 5.25? If so, can you provide a new crash dump with debug information? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: 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 marked as a duplicate of bug 452344 *** |