| Summary: | kWin crash after apply no border in any window | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Oscar Campos <oscar.campos> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 4.9.3 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Oscar Campos
2012-12-03 18:53:01 UTC
Through the rmb context menu i assume and it's not a problem when not using the Aurorae decorations (the ones you get via GHNS)? *** This bug has been marked as a duplicate of bug 310658 *** It only crash when Desktop effects are active No it just happens with whatever window decoration I use. I was using default KDE Oxygen decoration already. The crash happens from within the decoration. Whether the compositing state causes delays on the popup is interesting, but not relevant. Bind a shortcut to hiding the decoration, hide it using that shortcut. If it still crashes this way, please attach the new backtrace. Try another decoration (oxygen, not some "oxygen-air" clone from GHNS) If it still crashes on hidint the decoration, please attach that backtrace as well. Otherwise this is a dupe. *** This bug has been marked as a duplicate of bug 310658 *** #6 0x00007f216aaa9cfe in QScriptValue::toVariant() const () from /usr/lib64/qt4/libQtScript.so.4 #7 0x00007f216cb2f41e in QDeclarativeEnginePrivate::scriptValueToVariant(QScriptValue const&, int) () from /usr/lib64/qt4/libQtDeclarative.so.4 #8 0x00007f216cb35faf in QDeclarativeExpressionPrivate::value(QObject*, bool*) () from /usr/lib64/qt4/libQtDeclarative.so.4 #9 0x00007f216cb6dea9 in QDeclarativeBoundSignal::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt4/libQtDeclarative.so.4 #10 0x00007f216971a12b in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #11 0x00007f216cc25f72 in QDeclarativeMouseArea::pressed(QDeclarativeMouseEvent*) () from /usr/lib64/qt4/libQtDeclarative.so.4 #12 0x00007f216cad3d6f in QDeclarativeMouseArea::setPressed(bool) () from /usr/lib64/qt4/libQtDeclarative.so.4 There's a pending mousepress on some graphicsscene when the crash occured. Oxygen does not use a graphicsscene. => what did you click on when the crash occured and how is that related to hiding the titlebar? Just the context menu entry for "no border", now is not crashing anymore I didn't did anything, no recompile, no reboot, no anything. This kind of crash is unfortunately anything but deterministic. Since it happens on destruction, the memory will, though invalid, still contain the correct data. The core problem is however that it's not possible to stop eventprocessing inside the graphicsscene, which will continue after the nested eventloop of the popup exited (but then the GraphicsScene is gone) I'm willing to bet your right arm that this does not happen with the actual stock oxygen decoration, nor using a shortcut. In this case - and with a little luck ;-) the patch that closed the dupe will resolve this (it moves the destruction of the decoration to the next event cycle, when the events that caused it have been fully processed) I understand you, I'm developer too so I know how important are accurate reports. I was using the decorator that is Blue at borders and silver on center. I think this is regular Oxygen decorator theme. Anyway seems to be working nice now, I was doing a lot of changes to my KDE look & feel I think you shouldn't be worried about this bug report anymore. Regards and thanks for a fast reply. |