| Summary: | KWin breaks when running pacman updates that require DKMS post-transaction hooks | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | David Conner <dconner.pro> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | phd |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.20.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David Conner
2020-11-22 10:41:52 UTC
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*) Seems like it needs to re-init automatically when the graphics drivers are updated. I'm not sure what makes KWin create another QtQuick GL context, there is nothing that says this in the backtrack. All other KDE apps that are already running do not crash even when the driver becomes unavailable. And I have never experienced running KWin crash in this situation either. If we could locate the place where GL context is being created in KWin, connecting to QQuickWindow::ContextNotAvailable signal should stop KWin from crashing [1], and maybe let us handle the problem from here (fallback to software and retry?). Or we could simply do this fallback check before even allowing QtQuick to create the new GL context. [1] https://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/scenegraph/qsgrenderloop.cpp?h=5.14.2#n331 Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! 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! |