Bug 227343 - kwin crashes after resuming from suspend and using grid-plugin
Summary: kwin crashes after resuming from suspend and using grid-plugin
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-02-17 12:02 UTC by Mat Lechner
Modified: 2018-10-21 04:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.35 KB, text/plain)
2010-04-29 15:17 UTC, Mat Lechner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mat Lechner 2010-02-17 12:02:10 UTC
Application: kwin (4.4.00 (KDE 4.4.0))
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
kwin crashed after I resumed from suspend and changed desktop using the grid-plugin. I cannot reproduce this crash.

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#6  0x01abb2de in KWin::DesktopGridEffect::windowInputMouseEvent (this=0x864fa18, e=0xbf89e828) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:472
#7  0x00960490 in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=0x8621c68, e=0xbf89ed8c) at ../../kwin/effects.cpp:817
#8  0x008fd038 in KWin::Workspace::workspaceEvent (this=0x85bddb0, e=0xbf89ed8c) at ../../kwin/events.cpp:260
#9  0x008d6c82 in KWin::Application::x11EventFilter (this=0xbf89f138, e=0xbf89ed8c) at ../../kwin/main.cpp:361
#10 0x0643fbd0 in qt_x11EventFilter (ev=0xbf89ed8c) at kernel/qapplication_x11.cpp:399
#11 0x0644f3e0 in QApplication::x11ProcessEvent (this=0xbf89f138, event=0xbf89ed8c) at kernel/qapplication_x11.cpp:3231
#12 0x0647f95a in x11EventSourceDispatch (s=0x84d8040, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#13 0x016e0e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#14 0x016e4730 in ?? () from /lib/libglib-2.0.so.0
#15 0x016e4863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#16 0x012678e5 in QEventDispatcherGlib::processEvents (this=0x84bf7d0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#17 0x0647f485 in QGuiEventDispatcherGlib::processEvents (this=0x84bf7d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#18 0x0123a319 in QEventLoop::processEvents (this=0xbf89f084, flags=) at kernel/qeventloop.cpp:149
#19 0x0123a76a in QEventLoop::exec (this=0xbf89f084, flags=...) at kernel/qeventloop.cpp:201
#20 0x0123e95f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#21 0x063c0317 in QApplication::exec () at kernel/qapplication.cpp:3577
#22 0x008d8850 in kdemain (argc=3, argv=0xbf89f344) at ../../kwin/main.cpp:526
#23 0x080485cb in main (argc=3, argv=0xbf89f344) at kwin_dummy.cpp:3

Possible duplicates by query: bug 220582, bug 219721, bug 217786.

Reported using DrKonqi
Comment 1 Martin Flöser 2010-03-31 12:35:13 UTC
without a way to reproduce I can't see a chance to fix it :-( Looking at the code the crash does not make any sense. If it happens again please try to see what triggered the crash exactly.
Comment 2 Mat Lechner 2010-04-02 16:05:36 UTC
So far it did not happen again. But I'll report if it does.
Comment 3 Mat Lechner 2010-04-29 15:17:06 UTC
Created attachment 43100 [details]
New crash information added by DrKonqi

It happened again, but not immediately after resume (though I resumed an hour or so before). It again occured when usig the grid-effect normally, this time on a two-monitor-setup realized with xrandr (I don't know if this is important)
Comment 4 Andrew Crouthamel 2018-09-20 22:00:36 UTC
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!
Comment 5 Andrew Crouthamel 2018-10-21 04:44:30 UTC
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!