| Summary: | kwin_x11 crash when suspending compositing | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Anssi Hannula <anssi.hannula> |
| Component: | general | Assignee: | Vlad Zahorodnii <vlad.zahorodnii> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andre.vmatos, andreas_nordal_4, dan93bars, diehard67, henk717, jumpyfattoad, letzdropthebas, mahen, megatoaster94, nate, null, philipp.knaak, taocrismon, tockar |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.14.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kwin/9ac2e5d5bb44934b6d30bda9315210d544f33958 | Version Fixed In: | 5.15.0 |
| Sentry Crash Report: | |||
|
Description
Anssi Hannula
2018-07-24 22:04:52 UTC
I am experiencing the same issue on Kubuntu 18.04 , KDE Plasma 5.12.6. When starting a game trough steam that disables compositing there is a chance that kwin_x11 stops working. I am unable to locate a crash dump or log entry of this event. When using Alt + F2 to manually start kwin_x11 the system resumes functioning normally and then i am unable to reproduce the bug. I have not been able to find out why the crash only occurs some of the times a game is ran but rarely happens after a reboot or restart of kwin_x11. Kwin support information: https://paste.kde.org/pxajs4zhr Hi ! I regularly (maybe once every 1-2 days ?) encounter a kwin crash (decorations disappear, I have to restart kwin manually) when starting a game that disables compositing (or switching mpv to fullscreen). I yet have to figure out a way to reproduce it... But it's been happening for at least 6 months - 1 year and is still the case when using the whole up to date KDE stack and Neon 18.04. (whether I use a PPA or not) It occurs with both Intel HD Graphics and AMD Radeon RX550/560 (but not with Nvidia, but those are not that pleasant to use under KDE :). It happens in both Neon 16.04 and 18.04. And also with a recent kernel in Manjaro. It occurs on several different PCs. How can I help pinpoint this ? Are there other related bug reports ? Cheers :-) *** Bug 400358 has been marked as a duplicate of this bug. *** I can always reproduce it by doing the following: * Run kwin from terminal, e.g. kwin_x11 --replace * Activate the Present Windows effect, hover some window * Activate the Desktop Grid effect * Replace kwin by running kwin_x11 --replace from krunner *** Bug 398018 has been marked as a duplicate of this bug. *** Hi ! I have a problem getting a proper debug trace... I frequently get the crash when gdb is not attached to kwin (I usually kill & start kwin from gdb). However when I try to attach gdb from the pre-existing kwin process, the system hangs. Any idea ? Also, for some reason, I never get DrKonqi when my decorations disappear. As a dirty and not that satisfying workaround, could kwin auto-restart when it crashes ? (In reply to Mahendra Tallur from comment #6) > However when I try to attach gdb from the pre-existing kwin process, the > system hangs. Any idea ? Did you resume kwin? e.g. (gdb) continue Also, I think this bug report already has good backtrace. (In reply to Vlad Zagorodniy from comment #7) > (In reply to Mahendra Tallur from comment #6) > > However when I try to attach gdb from the pre-existing kwin process, the > > system hangs. Any idea ? > Did you resume kwin? e.g. > (gdb) continue > > Also, I think this bug report already has good backtrace. Nope, I cannot resume, I cannot activate the terminal. OK, I have to do it from the full screen console, gonna check the right syntax... I think the problem is that kwin devs are not gamers and thus cannot experience it themselves ;) -- it's true it's difficult to be productive & gamer :) *** Bug 400881 has been marked as a duplicate of this bug. *** *** Bug 400886 has been marked as a duplicate of this bug. *** *** Bug 400954 has been marked as a duplicate of this bug. *** *** Bug 401491 has been marked as a duplicate of this bug. *** *** Bug 401559 has been marked as a duplicate of this bug. *** *** Bug 401770 has been marked as a duplicate of this bug. *** (In reply to Vlad Zagorodniy from comment #4) > I can always reproduce it by doing the following: > * Run kwin from terminal, e.g. kwin_x11 --replace > * Activate the Present Windows effect, hover some window > * Activate the Desktop Grid effect > * Replace kwin by running kwin_x11 --replace from krunner Weird, I'm not able anymore to reproduce the crash by following these steps. If you're able to reproduce this crash, could you please provide the following details: * version of libepoxy; * version of KWin; * what GPU and driver you use; * what were you doing to reproduce the crash; * is the crash reproducible in the following scenarios: - Background Contrast effect disabled / Blur effect disabled; - Background Contrast effect disabled / Blur effect enabled; - Background Contrast effect enabled / Blur effect disabled; - Background Contrast effect enabled / Blur effect enabled. Thanks. *** Bug 402317 has been marked as a duplicate of this bug. *** I added some debug outputs(https://phabricator.kde.org/P282) to see what the current OpenGL context is when the blur effect is about to be destroyed, and results are somewhat odd: About to unload all effects Current context: 0x55940fcbdbe0 Current context: 0x55940fcbdbe0 About to destroy the blur effect Current context: 0x0 Current context: 0x55940fcbdbe0 It looks like the context somehow got released. It looks like QQuickView messes with the current context. Current workaround: Disable close buttons in the Present Windows effect. Git commit 9ac2e5d5bb44934b6d30bda9315210d544f33958 by Vlad Zagorodniy. Committed on 21/12/2018 at 00:22. Pushed by vladz into branch 'master'. [effects] Make current OpenGL context per each unloaded effect Summary: Some effects may release the current context when they tear down, so we have to make the current context per each unloaded effect. FIXED-IN: 5.15.0 Test Plan: No longer able to reproduce bug 396830. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17716 M +36 -32 effects.cpp M +2 -0 effects.h https://commits.kde.org/kwin/9ac2e5d5bb44934b6d30bda9315210d544f33958 @Vlad : thank you so much for this important fix ! As a Neon user edition... user, is the provided workaround a proper way of confirming the fix works ? I'll try hard to reproduce it ! Can anyone confirm this bug also affect the LTS version of Plasma ? Thanks again, cheers, Mahen Replying to myself : yes, this bug affects the LTS too (several reporters) -- I'll think twice before posting. Would it be possible to backport the fix to 5.12 and possibly the current 5.14 too ? Cheers & thanks again for figuring it out, it's been turning me crazy ! *** Bug 423964 has been marked as a duplicate of this bug. *** |