Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: As title. Only other thing to note is that I have two panels on my desktop rather than one. The stack trace looks similar to the other bug, but since the line numbers are different I figure better to be safe than sorry. -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [Current thread is 0 (LWP 4181)] Thread 2 (Thread 0x7f661bce6950 (LWP 4187)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 #1 0x00007f663b953939 in QWaitCondition::wait (this=0x26a6080, mutex=0x26a6078, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87 #2 0x00007f663a7cf4cc in QHostInfoAgent::run (this=0x26a6060) at kernel/qhostinfo.cpp:260 #3 0x00007f663b952952 in QThreadPrivate::start (arg=0x26a6060) at thread/qthread_unix.cpp:189 #4 0x00007f66377d33ba in start_thread (arg=<value optimized out>) at pthread_create.c:297 #5 0x00007f66383b7fcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f663bf0f750 (LWP 4181)): [KCrash Handler] #4 QMutex::lock (this=0x91) at thread/qmutex.cpp:152 #5 0x00007f663ba3b45e in QCoreApplication::postEvent (receiver=0x3c01e00, event=0x2b467d0, priority=0) at kernel/qcoreapplication.cpp:1012 #6 0x00007f66390476f3 in QX11Data::xdndHandleFinished (this=<value optimized out>, xe=0x7fff43f52720, passive=false) at kernel/qdnd_x11.cpp:1234 #7 0x00007f66390215c6 in QApplication::x11ClientMessage (this=<value optimized out>, w=0x3b730e0, event=0x7fff43f52720, passive_only=false) at kernel/qapplication_x11.cpp:3122 #8 0x00007f6639034b66 in QApplication::x11ProcessEvent (this=0x2023c10, event=0x7fff43f52720) at kernel/qapplication_x11.cpp:3675 #9 0x00007f663905d464 in x11EventSourceDispatch (s=0x2066000, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #10 0x00007f6637a2220a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #11 0x00007f6637a258e0 in ?? () from /usr/lib/libglib-2.0.so.0 #12 0x00007f6637a25a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #13 0x00007f663ba64e6f in QEventDispatcherGlib::processEvents (this=0x20625b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #14 0x00007f663905cbef in QGuiEventDispatcherGlib::processEvents (this=0x91, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #15 0x00007f663ba3a002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1140140560}) at kernel/qeventloop.cpp:149 #16 0x00007f663ba3a3cd in QEventLoop::exec (this=0x7fff43f52a50, flags={i = 1140140640}) at kernel/qeventloop.cpp:200 #17 0x00007f663ba3c694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #18 0x00007f662f90e6bb in kdemain (argc=1, argv=0x2007900) at /build/buildd/kdebase-workspace-4.2.96/plasma/shells/desktop/main.cpp:50 #19 0x0000000000407215 in launch (argc=1, _name=0x2014108 "/usr/bin/plasma-desktop", args=<value optimized out>, cwd=0x0, envc=0, envs=0x2014128 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a3c9 "0") at /build/buildd/kde4libs-4.2.96/kinit/kinit.cpp:676 #20 0x0000000000407a38 in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.2.96/kinit/kinit.cpp:1168 #21 0x0000000000407fe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.96/kinit/kinit.cpp:1361 #22 0x0000000000408b26 in main (argc=2, argv=0x7fff43f538f8, envp=0x7fff43f53910) at /build/buildd/kde4libs-4.2.96/kinit/kinit.cpp:1788 This bug may be a duplicate of or related to bug 182511 Reported using DrKonqi
This could be related to bug 192000. - Can you reproduce the crash at will again ? I wonder if this could be fixed when using Qt4.5.2+ Thanks
Unfortunately not. I just tried adding it again and it worked this time (though the widget certainly doesn't seem to be designed for the panel!)
*** This bug has been marked as a duplicate of bug 192000 ***