Summary: | KDE gfx subsystem failure(s) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | magnus <magnus.neumann> |
Component: | aurorae | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ken20001 |
Priority: | NOR | ||
Version: | 4.9.2 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
magnus
2012-11-06 05:15:08 UTC
You got a "crash on exit" because kwin needs to restart to alter the graphicssystem. The crash was caused by the window decoration (aurorae, the things you can get from GHNS) and is actually a SIGABRT caused by an xcb assertion. FTR: the deco does not like the native graphicssystem too much anyway (inferior qml performance), so unless using the Xrender compositor, you're better off not using it. @Martin smells like calling QWidget::setParent(0) in the deconstructor is not reliable, at least not on exit and for the raster graphicssystem. -> hook onto qApp->aboutToQuit() and introduce a flag to omit special deconstruction in that case? forgot component update... but there is probably a good reason why the setParent(NULL) call is there. I just don't remember why and I would like to be able to reproduce the issue. Looks to me like a side issue. Given that there is an assertion I would expect that something is build in debug mode which shouldn't be? commit c3361a7cfb47feaf93fa4d0768272a0cba847328 Author: Martin Gräßlin <kde@martin-graesslin.com> Date: Sat Jun 19 15:23:48 2010 +0000 Defer deletion of the AuroraeScene and View to the next event loop. It is possible that the scene get's deleted before processing mouse events BUG: 242165 FIXED-IN: 4.5.0 CCBUG: 241876 CCBUG: 242116 --- There's not next event loop in this (after aboutToQuit) case anyway and the deconstruction will not be caused by an event. Also this may meanwhile be covered by the discussed general QueuedConnection (i'd have to check whether that was actually done) for useractions. I'd say it's as long a corner case as it does not get you a crash on exit for every logout. @magnus: is this a reproducible problem? > Also this may meanwhile be covered by the discussed general QueuedConnection
> (i'd have to check whether that was actually done) for useractions.
yeah, quite likely that it is no longer needed
assuming fixed |