Summary: | Kwin crashes on maximising konsole | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Karan Pratap Singh <wizard.karan> |
Component: | aurorae | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | adaptee |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.9.0 |
Description
Karan Pratap Singh
2011-04-21 17:14:33 UTC
*** This bug has been marked as a duplicate of bug 242165 *** I don't think it is the same crash as the duplicate is an assert while the original crash was a crash. are you able to reproduce the crash with a more recent version of qt? errr... just for the records: Both traces land in Aurorae::AuroraeMaximizeButton::mouseReleaseEvent() which pot. trigger(s/ed) a self-deletion. There's called QGraphicsItem::update() and the assumed dupe calls QGraphicsItemPrivate::invalidateParentGraphicsEffectsRecursively(this = 0x0) while this one ends up in an assert in qscopedpointer.h (which means "attempted access to the managed pointer being NULL") On a string based comparism they're certainly not equal but my Jedi senses tell me - it's the same solution, if not even bug =) > On a string based comparism they're certainly not equal but my Jedi senses tell
> me - it's the same solution, if not even bug =)
Yes they look very similar, nevertheless I assume that I did a proper fix for the crash ;-) and that
something else is hitting the assert (and the assert is probably compiled-out on most systems,
but we still don't get crash reports).
btw I cannot reproduce I can't reproduce this using KDE SC 4.8 beta1 and Qt 4.8 rc1 . (In reply to comment #7) > I can't reproduce this using KDE SC 4.8 beta1 and Qt 4.8 rc1 . Has it happened to you before? So far no developer could reproduce this - ever. (I actually feel tempted to blame downstream...) So unless it happened to you before, that's nice to know - but unfortunately meaningless :-( at latest fixed with Aurorae 3 in 4.9 |