| Summary: | Desktopgrid cannot handle adding (crash) or removing screens | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | hynek |
| Component: | effects-desktop-grid | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | justin.zobel |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 4.11.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
hynek
2014-01-10 10:07:50 UTC
from the crash report it looks like you were using Desktop Grid while pluging in the screen. Can you confirm that? I have Desktop Grid enabled in KDE but don't think it has been displayed while plugging the display in. Happens. Removing a screen with DG active doesn't work properly either (but got no crash) Slightly different trace: Thread 1 (Thread 0xaee66740 (LWP 3604)): [KCrash Handler] #6 0xa723bd44 in QHash<KWin::EffectWindow*, KWin::WindowMotionManager::WindowMotion>::findNode (this=this@entry=0xa5d4a9c, akey=<optimized out>, ahp=0x0) at /usr/include/qt4/QtCore/qhash.h:884 #7 0xa7243215 in contains (akey=<synthetic pointer>, this=0xa5d4a9c) at /usr/include/qt4/QtCore/qhash.h:874 #8 isManaging (w=0xa46cf70, this=0xa5d4a98) at /home/src/KDE4/kde-workspace/kwin/libkwineffects/kwineffects.h:2514 #9 KWin::DesktopGridEffect::paintWindow (this=this@entry=0xa2bb800, w=w@entry=0xa46cf70, mask=<optimized out>, mask@entry=85, region=..., data=...) at /home/src/KDE4/kde-workspace/kwin/effects/desktopgrid/desktopgrid.cpp:305 #10 0xb76701b2 in KWin::EffectsHandlerImpl::paintWindow (this=0xa46e068, w=0xa46cf70, mask=mask@entry=85, region=..., data=...) at /home/src/KDE4/kde-workspace/kwin/effects.cpp:415 #11 0xb764d256 in KWin::Scene::paintWindow (this=0xa23c630, w=0xa480830, mask=85, region=..., quads=...) at /home/src/KDE4/kde-workspace/kwin/scene.cpp:412 #12 0xb764bfcf in KWin::Scene::paintGenericScreen (this=this@entry=0xa23c630, orig_mask=orig_mask@entry=80) at /home/src/KDE4/kde-workspace/kwin/scene.cpp:240 #13 0xb7659ad8 in KWin::SceneOpenGL2::paintGenericScreen (this=this@entry=0xa23c630, mask=mask@entry=80, data=...) at /home/src/KDE4/kde-workspace/kwin/scene_opengl.cpp:754 #14 0xb7648ed0 in KWin::Scene::finalPaintScreen (this=0xa23c630, mask=mask@entry=80, region=..., data=...) at /home/src/KDE4/kde-workspace/kwin/scene.cpp:196 #15 0xb7670123 in KWin::EffectsHandlerImpl::paintScreen (this=0xa46e068, mask=mask@entry=80, region=..., data=...) at /home/src/KDE4/kde-workspace/kwin/effects.cpp:375 #16 0xb69a768e in KWin::Effect::paintScreen (this=this@entry=0xa324000, mask=mask@entry=80, region=..., data=...) at /home/src/KDE4/kde-workspace/kwin/libkwineffects/kwineffects.cpp:522 Likely "accidentally" activated by active screen edge/corner. Backtrace sugests this and I can confirm that there's a bug (while i change the screen layout n times a day w/o any problem otherwise) That might be the case - I have an active corner which could have been activated via a random mouse movement. Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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 mark the bug 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! 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! |