| Summary: | Kwin crash frecuently | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Eduardo A. Cabanillas <ea.cabanillas> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Eduardo A. Cabanillas
2011-04-02 21:22:39 UTC
#6 KWin::Workspace::setCompositeTimer (this=0xb1a950) at ../../kwin/composite.cpp:499 #7 0x00007ff4c3f7620a in KWin::WobblyWindowsEffect::postPaintScreen (this=<value optimized out>) at ../../../kwin/effects/wobblywindows/wobblywindows.cpp:364 unless KUbuntu has patched the wobblywindow effect, this backtrace makes no sense, since the line is "if (!compositing())" and compositing() is a oneline inliner testing whether a global pointer is NULL. That's not quite crash prone at all... However, the wobblywindow effect as a wonky QHash implementation - probably because of the prop. "Pair" struct (effectively being QPointF) @Eduardo: Long story short - this backtrace makes no sense. Do all backtraces look like this (the same first lines in thread 1, in doubt attach some) when it crashes in this context? As a workaround you might disable the WobblyWindows effect which may be causing this - or update to a more recent KDE version. we need some feedback. Please also test wether the crash happens at all with newer versions of KDE - at least 4.5.4. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |