Bug 320792

Summary: KDE plasma-desktop crashed during renaming and switching activities using Winkey+tab
Product: [Unmaintained] plasma4 Reporter: adam <wanakutia>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.10.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description adam 2013-06-06 02:17:05 UTC
Application: plasma-desktop (4.10.3)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.9.0-030900rc8-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:
using activity manager I was changing a names of may activities - 4 in total, and I was switching between them too using Winkey+tab. 
- Unusual behaviour I noticed:
before I start managing my activities I was changing settings and short cuts for window switcher: to alt+tab=swith windows, winkey+tab=swith activities (hell lots of problems with this one). to the point: alt+tab always switching between activities, windows and desktops with no particular pattern...

I using:
toschiba sattelite p300-20h with 2nd HDD
porcessor: intel pentium dualcore t3400 2.16 Mhz
RAM: 2 Gb

OS:
around week old Ubuntu 13.04 with additional desktop environments installed (Unix, gnome, cinnamon, Lxde, xfce and KDE - couldn't resist to compare the all). kernel upgraded to 3.9  (around hour before crash). Regards, hope it'll help

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcf7e0827c0 (LWP 4648))]

Thread 4 (Thread 0x7fcf5f143700 (LWP 4649)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fcf76dafe77 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007fcf76dafea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007fcf714aaf8e in start_thread (arg=0x7fcf5f143700) at pthread_create.c:311
#4  0x00007fcf7d96ce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fcf577cf700 (LWP 4650)):
#0  0x00007fcf7d97b090 in pthread_mutex_lock (mutex=0x7fcf50000a60) at forward.c:192
#1  0x00007fcf70de75c1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcf70da7493 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcf70da8188 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fcf70da8304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fcf7a54c036 in QEventDispatcherGlib::processEvents (this=0x7fcf500008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007fcf7a51c38f in QEventLoop::processEvents (this=this@entry=0x7fcf577ced90, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fcf7a51c618 in QEventLoop::exec (this=this@entry=0x7fcf577ced90, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fcf7a41e410 in QThread::exec (this=this@entry=0x1bf5020) at thread/qthread.cpp:542
#9  0x00007fcf7a4fdedf in QInotifyFileSystemWatcherEngine::run (this=0x1bf5020) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007fcf7a420bec in QThreadPrivate::start (arg=0x1bf5020) at thread/qthread_unix.cpp:338
#11 0x00007fcf714aaf8e in start_thread (arg=0x7fcf577cf700) at pthread_create.c:311
#12 0x00007fcf7d96ce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fcf46050700 (LWP 4662)):
#0  0x00007fcf7d9603cd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fcf70da81dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcf70da8304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcf7a54c036 in QEventDispatcherGlib::processEvents (this=0x7fcf380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fcf7a51c38f in QEventLoop::processEvents (this=this@entry=0x7fcf4604fd90, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fcf7a51c618 in QEventLoop::exec (this=this@entry=0x7fcf4604fd90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fcf7a41e410 in QThread::exec (this=this@entry=0x1a49540) at thread/qthread.cpp:542
#7  0x00007fcf7a4fdedf in QInotifyFileSystemWatcherEngine::run (this=0x1a49540) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007fcf7a420bec in QThreadPrivate::start (arg=0x1a49540) at thread/qthread_unix.cpp:338
#9  0x00007fcf714aaf8e in start_thread (arg=0x7fcf46050700) at pthread_create.c:311
#10 0x00007fcf7d96ce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7fcf7e0827c0 (LWP 4648)):
[KCrash Handler]
#6  0x00007fcf7c118944 in QDeclarativeItem::~QDeclarativeItem (this=0x5942d90, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#7  0x00007fcf5dd0cb11 in ~QDeclarativeElement (this=0x5942d90, __in_chrg=<optimized out>) at /usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:87
#8  QDeclarativePrivate::QDeclarativeElement<Plasma::FrameSvgItem>::~QDeclarativeElement (this=0x5942d90, __in_chrg=<optimized out>) at /usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:87
#9  0x00007fcf7a5375e8 in QObject::event (this=0x5942d90, e=<optimized out>) at kernel/qobject.cpp:1175
#10 0x00007fcf798c38ec in QApplicationPrivate::notify_helper (this=this@entry=0x1086d50, receiver=receiver@entry=0x5942d90, e=e@entry=0x4fbc990) at kernel/qapplication.cpp:4567
#11 0x00007fcf798c625b in QApplication::notify (this=this@entry=0x1031c30, receiver=receiver@entry=0x5942d90, e=e@entry=0x4fbc990) at kernel/qapplication.cpp:4428
#12 0x00007fcf7b1e1af6 in KApplication::notify (this=0x1031c30, receiver=0x5942d90, event=0x4fbc990) at ../../kdeui/kernel/kapplication.cpp:311
#13 0x00007fcf7a51d63e in QCoreApplication::notifyInternal (this=0x1031c30, receiver=receiver@entry=0x5942d90, event=event@entry=0x4fbc990) at kernel/qcoreapplication.cpp:946
#14 0x00007fcf7a521171 in sendEvent (event=0x4fbc990, receiver=0x5942d90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xfe91f0) at kernel/qcoreapplication.cpp:1570
#16 0x00007fcf7a5214a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#17 0x00007fcf7a54be83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#18 postEventSourceDispatch (s=0x1077d60) at kernel/qeventdispatcher_glib.cpp:279
#19 0x00007fcf70da7f05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fcf70da8248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fcf70da8304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fcf7a54c016 in QEventDispatcherGlib::processEvents (this=0xfeaad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x00007fcf799691ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007fcf7a51c38f in QEventLoop::processEvents (this=this@entry=0x7fff96a99eb0, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007fcf7a51c618 in QEventLoop::exec (this=this@entry=0x7fff96a99eb0, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007fcf7a521cf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#27 0x00007fcf798c1ffc in QApplication::exec () at kernel/qapplication.cpp:3828
#28 0x00007fcf7dc7846b in kdemain (argc=1, argv=0x7fff96a9a1a8) at ../../../../plasma/desktop/shell/main.cpp:126
#29 0x00007fcf7d894ea5 in __libc_start_main (main=0x4006e0 <main(int, char**)>, argc=1, ubp_av=0x7fff96a9a1a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff96a9a198) at libc-start.c:260
#30 0x0000000000400711 in _start ()

This bug may be a duplicate of or related to bug 302931.

Possible duplicates by query: bug 320031, bug 319793, bug 319760, bug 319682, bug 319653.

Reported using DrKonqi
Comment 1 Martin Flöser 2013-06-06 09:54:04 UTC

*** This bug has been marked as a duplicate of bug 302931 ***