Bug 311505 - KWin crashed after moving a recently started application from one desktop to another
Summary: KWin crashed after moving a recently started application from one desktop to ...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: effects-desktop-grid (show other bugs)
Version: 4.10.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 319875 327568 359687 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-11 10:37 UTC by Martin
Modified: 2018-11-17 08:39 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.50 KB, text/plain)
2013-03-25 19:33 UTC, Martin
Details
KWin Support Information (6.10 KB, text/plain)
2013-03-28 08:19 UTC, Martin
Details
New crash information added by DrKonqi (4.66 KB, text/plain)
2013-03-29 07:39 UTC, Martin
Details
New crash information added by DrKonqi (4.11 KB, text/plain)
2013-07-24 20:05 UTC, yo
Details
New crash information added by DrKonqi (2.99 KB, text/plain)
2013-11-07 15:24 UTC, Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2012-12-11 10:37:52 UTC
Application: kwin (4.9.4)
KDE Platform Version: 4.9.4
Qt Version: 4.8.3
Operating System: Linux 3.5.0-20-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:

I started Kile and immediately activated the desktop grid effect via a screen edge. I moved the Kile window from my second to my first desktop. The program was not completely started; I could see the splash screen after the move. I was still in the grid view (I think) when KWin crashed.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6059806780 (LWP 2408))]

Thread 3 (Thread 0x7f6051b93700 (LWP 2413)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f606901dcd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f606901dd09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f606117ee9a in start_thread (arg=0x7f6051b93700) at pthread_create.c:308
#4  0x00007f606c0f4cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f604a8bf700 (LWP 2785)):
#0  0x00007f606c0ee023 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f6067df9023 in qt_safe_select (nfds=19, fdread=0x7f6040000ac8, fdwrite=0x7f6040000d60, fdexcept=0x7f6040000ff8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83
#2  0x00007f6067dfd9e4 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f6040000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223
#3  0x00007f6067dfe572 in QEventDispatcherUNIX::processEvents (this=0x7f60400008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:926
#4  0x00007f6067dcc2bf in QEventLoop::processEvents (this=this@entry=0x7f604a8bedd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f6067dcc548 in QEventLoop::exec (this=0x7f604a8bedd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f6067ccdb10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f6067dac9af in QInotifyFileSystemWatcherEngine::run (this=0x1cc2cd0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f6067cd0aec in QThreadPrivate::start (arg=0x1cc2cd0) at thread/qthread_unix.cpp:338
#9  0x00007f606117ee9a in start_thread (arg=0x7f604a8bf700) at pthread_create.c:308
#10 0x00007f606c0f4cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6059806780 (LWP 2408)):
[KCrash Handler]
#6  0x00007f606a8e0df4 in KWin::EffectWindow::geometry (this=<optimized out>) at ../../../kwin/libkwineffects/kwineffects.cpp:310
#7  0x00007f604b765e0e in setActive (active=<optimized out>, this=0x1d9e200) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1053
#8  KWin::DesktopGridEffect::setActive (this=0x1d9e200, active=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1036
#9  0x00007f604b766cba in KWin::DesktopGridEffect::windowInputMouseEvent (this=0x1d9e200, e=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:648
#10 0x00007f606c491401 in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=<optimized out>, e=0x7fff5c288f40) at ../../kwin/effects.cpp:1043
#11 0x00007f606c42e70d in KWin::Workspace::workspaceEvent (this=0x1a987d0, e=0x7fff5c288f40) at ../../kwin/events.cpp:249
#12 0x00007f606c420848 in KWin::Application::x11EventFilter (this=0x7fff5c2894a0, e=0x7fff5c288f40) at ../../kwin/main.cpp:362
#13 0x00007f60671e17bc in qt_x11EventFilter (ev=0x7fff5c288f40) at kernel/qapplication_x11.cpp:441
#14 qt_x11EventFilter (ev=0x7fff5c288f40) at kernel/qapplication_x11.cpp:429
#15 0x00007f60671f17f0 in QApplication::x11ProcessEvent (this=0x7fff5c2894a0, event=0x7fff5c288f40) at kernel/qapplication_x11.cpp:3449
#16 0x00007f606721a9d9 in QEventDispatcherX11::processEvents (this=0x1954ad0, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#17 0x00007f6067dcc2bf in QEventLoop::processEvents (this=this@entry=0x7fff5c2891b0, flags=...) at kernel/qeventloop.cpp:149
#18 0x00007f6067dcc548 in QEventLoop::exec (this=0x7fff5c2891b0, flags=...) at kernel/qeventloop.cpp:204
#19 0x00007f6067dd1708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#20 0x00007f606c422ed4 in kdemain (argc=3, argv=0x7fff5c2895e8) at ../../kwin/main.cpp:545
#21 0x00007f606c02276d in __libc_start_main (main=0x4006a0 <main(int, char**)>, argc=3, ubp_av=0x7fff5c2895e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff5c2895d8) at libc-start.c:226
#22 0x00000000004006d1 in _start ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-12-11 15:35:14 UTC
Looks like there's a dangeling pointer (likely the splash) in the motionmanager.
Either because it was added in the first place, or the effect did not receive slotWindowClosed for the window.

Random try would be to MM::unmanage() windows from the deleted slot.
Comment 2 Martin 2013-03-25 19:33:08 UTC
Created attachment 78379 [details]
New crash information added by DrKonqi

kwin (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

This is still valid in KDE 4.10.1 and can be reproduced like before.

-- Backtrace (Reduced):
#6  QObject::property (this=0x260100000de1, name=0x7f2820ed0821 "geometry") at kernel/qobject.cpp:3733
#7  0x00007f2820ec05bd in KWin::EffectWindow::geometry (this=<optimized out>) at ../../../kwin/libkwineffects/kwineffects.cpp:662
#8  0x00007f27f53a44ab in setActive (active=<optimized out>, this=0x1d0df50) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1051
#9  KWin::DesktopGridEffect::setActive (this=0x1d0df50, active=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1034
#10 0x00007f27f53a546a in KWin::DesktopGridEffect::windowInputMouseEvent (this=0x1d0df50, e=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:646
Comment 3 Thomas Lübking 2013-03-26 20:28:14 UTC
No crash here, please:

a) descripbe -what* you move - the splashscreen or the mainwindow?
b) note how many other windows are on the from/to desktops
c) provide the output of "qdbus org.kde.kwin /KWin supportInformation"
Comment 4 Martin 2013-03-28 08:19:56 UTC
Created attachment 78449 [details]
KWin Support Information

a) I move the main window. I did not know that I also can move the splashscreen until now.
b) During my first test I had three windows on desktop 1 and one window on desktop 2 (out of two desktops). I could reproduce the bug in 'both ways' (moving from 1 to 2 and vice versa). Then I closed all windows except the browser window and tried again. So far I got one crash in 15 tries. I also tried to reproduce the crash using krita but that did not work. Maybe it is related to the fact that the kile splash is visible for a short duration after the main window showed up (krita replaces the splash with the main window much faster).
c) attached
Comment 5 Thomas Lübking 2013-03-28 12:50:33 UTC
I, for one, can not move the kile mainwindow while the splash is still there (because it's ~100ms at best and the layout re-arranges with the appearance of the main window)

So here comes a wild guess: does it happen with "dim inactive" disabled?
Comment 6 Martin 2013-03-29 07:39:41 UTC
Created attachment 78469 [details]
New crash information added by DrKonqi

kwin (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

Yes, the crash also happens with 'dim inactive' disabled. Since I am not completely sure that this backtrace is not slightly different, I attached it, too.
I am using Kile from Git, maybe the splashscreen is longer active in that version. Maybe a test app with just a splashscreen and a main window can help to reproduce this bug.

-- Backtrace (Reduced):
#6  0x00007f37ca81e5b4 in KWin::EffectWindow::geometry (this=<optimized out>) at ../../../kwin/libkwineffects/kwineffects.cpp:662
#7  0x00007f379edc34ab in setActive (active=<optimized out>, this=0x3588c40) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1051
#8  KWin::DesktopGridEffect::setActive (this=0x3588c40, active=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:1034
#9  0x00007f379edc446a in KWin::DesktopGridEffect::windowInputMouseEvent (this=0x3588c40, e=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:646
#10 0x00007f37cc3ec191 in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=<optimized out>, e=0x7fffedc13030) at ../../kwin/effects.cpp:1069
Comment 7 Martin Flöser 2013-05-15 17:57:20 UTC
*** Bug 319875 has been marked as a duplicate of this bug. ***
Comment 8 yo 2013-07-24 20:05:54 UTC
Created attachment 81325 [details]
New crash information added by DrKonqi

kwin (4.10.95) on KDE Platform 4.10.95 using Qt 4.8.4

- What I was doing when the application crashed:

I entered Show All Desktops via a keybinding. From there, I dragged Chrome and KWin segfaulted.

-- Backtrace (Reduced):
#6  KWin::DesktopGridEffect::windowInputMouseEvent (this=0x8d8510, e=<optimized out>) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:568
#7  0x00007fcb007dffcb in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=<optimized out>, e=0x7fffa90565b0) at ../../kwin/effects.cpp:1237
#8  0x00007fcb00778405 in KWin::Workspace::workspaceEvent (this=0x9beb60, e=e@entry=0x7fffa90565b0) at ../../kwin/events.cpp:113
#9  0x00007fcb0076d3a0 in KWin::Application::x11EventFilter (this=0x7fffa90569a0, e=0x7fffa90565b0) at ../../kwin/main.cpp:414
#10 0x00007fcaf9bfa42c in qt_x11EventFilter (ev=0x7fffa90565b0) at kernel/qapplication_x11.cpp:441
Comment 9 Thomas Lübking 2013-07-24 20:19:09 UTC
May be a different issue.
How many monitors and virtual desktops do you use?
Comment 10 Martin 2013-11-07 15:24:49 UTC
Created attachment 83405 [details]
New crash information added by DrKonqi

kwin (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5

I think I ran into the same bug again. Kwin crashed right after moving a window to another desktop.

-- Backtrace (Reduced):
#6  0x00007fbb70875428 in QObject::property(char const*) const () from /usr/lib/libQtCore.so.4
#7  0x00007fbb757ab452 in KWin::EffectWindow::geometry (this=<optimized out>) at /chakra/desktop-unstable/kde-workspace/src/kde-workspace-4.11.2/kwin/libkwineffects/kwineffects.cpp:690
#8  0x00007fbb50bf5526 in KWin::DesktopGridEffect::setActive (this=0x2827db0, active=<optimized out>) at /chakra/desktop-unstable/kde-workspace/src/kde-workspace-4.11.2/kwin/effects/desktopgrid/desktopgrid.cpp:1046
#9  0x00007fbb50bf8b91 in KWin::DesktopGridEffect::windowInputMouseEvent (this=<optimized out>, e=<optimized out>) at /chakra/desktop-unstable/kde-workspace/src/kde-workspace-4.11.2/kwin/effects/desktopgrid/desktopgrid.cpp:643
#10 0x00007fbb7607d0bb in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=<optimized out>, e=0x7fff8aab0ab0) at /chakra/desktop-unstable/kde-workspace/src/kde-workspace-4.11.2/kwin/effects.cpp:1238
Comment 11 Thomas Lübking 2013-11-13 18:03:04 UTC
*** Bug 327568 has been marked as a duplicate of this bug. ***
Comment 12 Thomas Lübking 2016-02-22 23:42:55 UTC
*** Bug 359687 has been marked as a duplicate of this bug. ***
Comment 13 Andrew Crouthamel 2018-11-01 13:50:23 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2018-11-16 11:31:48 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
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!
Comment 15 Martin 2018-11-17 08:39:46 UTC
I could not reproduce the error anymore.