Summary: | kwindecoration crash after upgrade 4.8 to 4.9 | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Daniel Keenaghan <dkeenaghan> |
Component: | decorations | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | cfeck, dopiront, gasinvein, gorfou |
Priority: | NOR | ||
Version: | 4.9.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Daniel Keenaghan
2012-08-01 23:15:28 UTC
Thomas, looks like the regression is still there ... Actually, I did not see an API break in the commits, so it is a different bug, maybe we need valgrind logs to find out why the decoration isn't initialized correctly, and causes crashes whenever information is queried (font, etc., see other backtraces). *** Bug 304434 has been marked as a duplicate of this bug. *** I "accidentally" removed exported functions and classes (from the original tabbin implementation) - that is not ABI stable. I however re-added them (as stubs, but not NULL) For everything < 4.9.0 and in the kcm /only/ there's a chance for a dangeling factory pointer in the preview ( https://git.reviewboard.kde.org/r/105721/ ) but that should randomly affect *all* decos while atm. it only seems to hit 3rd party ones (including oc. those which are binary incompatible for sure (using instable API)) Also i've skulpture installed and just installed dekorator - w/o any issues. Still smells like ABI to me... What's interesting though, is that Mirza (bug #301646) has a bunch of old decos like redmond etc. installed which are no longer shipped with kwin since i think 4.8 and that do NOT seem to raise this issue. Created attachment 72910 [details]
New crash information added by DrKonqi
systemsettings (1.0) on KDE Platform 4.9.00 using Qt 4.8.1
- What I was doing when the application crashed:
Application crashes when opened
- Custom settings of the application:
QTCurve window decoration was installed and active before upgrading from 4.8 to 4.9
The crash can be reproduced every time.
-- Backtrace (Reduced):
#6 0x00007fde6776e300 in KDecorationOptions::showTooltips() const () from /usr/lib/libkdecorations.so.4
#7 0x00007fde6776e3a7 in KDecoration::createMainWidget(QFlags<Qt::WindowType>) () from /usr/lib/libkdecorations.so.4
[...]
#9 0x00007fde74f55232 in KDecorationPreview::recreateDecoration (this=0x1d25710, plugins=0x1d25670) at ../../../../kwin/kcmkwin/kwindecoration/preview.cpp:77
#10 0x00007fde74f5743d in KWin::DecorationModel::regeneratePreview (this=0x1d25540, index=..., size=...) at ../../../../kwin/kcmkwin/kwindecoration/decorationmodel.cpp:332
#11 0x00007fde74f57835 in KWin::DecorationModel::regenerateNextPreview (this=0x1d25540) at ../../../../kwin/kcmkwin/kwindecoration/decorationmodel.cpp:279
> that do NOT seem to raise this issue
Those other decorations don't try to use the options.
of course they did: https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/v4.5.0/entry/kwin/clients/redmond/redmond.cpp more important is that this option call is via KDecoration::createMainWidget() which about every decoration should call at a time. I had rather guessed that they'd be guarded through KCommonDecoration, but Skulpture uses it as well ... Created attachment 72942 [details]
New crash information added by DrKonqi
systemsettings (1.0) on KDE Platform 4.9.00 using Qt 4.8.1
- What I was doing when the application crashed:
In system settings, crah when clicking on workspace appearance.
-- Backtrace (Reduced):
#6 0x00007f327efad300 in KDecorationOptions::showTooltips() const () from /usr/lib/libkdecorations.so.4
#7 0x00007f327efad3a7 in KDecoration::createMainWidget(QFlags<Qt::WindowType>) () from /usr/lib/libkdecorations.so.4
[...]
#9 0x00007f32845e2232 in KDecorationPreview::recreateDecoration (this=0x13f6520, plugins=0x13f6480) at ../../../../kwin/kcmkwin/kwindecoration/preview.cpp:77
#10 0x00007f32845e443d in KWin::DecorationModel::regeneratePreview (this=0x13f6350, index=..., size=...) at ../../../../kwin/kcmkwin/kwindecoration/decorationmodel.cpp:332
#11 0x00007f32845e4835 in KWin::DecorationModel::regenerateNextPreview (this=0x13f6350) at ../../../../kwin/kcmkwin/kwindecoration/decorationmodel.cpp:279
*** This bug has been marked as a duplicate of bug 301646 *** The problem was in my case the following file: /usr/lib/kde4/kwin3deKorator.so after deleting the file everything worked again. This was the case on two different computers. 2012/8/4 Thomas Lübking <thomas.luebking@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=304407 > > Thomas Lübking <thomas.luebking@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DUPLICATE > > --- Comment #8 from Thomas Lübking <thomas.luebking@gmail.com> --- > > > *** This bug has been marked as a duplicate of bug 301646 *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. Yes, we know that it's ABI compatibility with 3rd party decorations (just recompiling the decoration or having your distro do so would do as well) The remaining issue is "what actually breaks the ABI" - see bug #301646 |