Bug 205663

Summary: Clicked on Lancelot with clock calendar open, Plasma crashed
Product: [Unmaintained] plasma4 Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, finex, ivan.cukic
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dotan Cohen 2009-08-30 10:09:03 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I clicked on the analogue clock plasmoid, and the calendar widget opened. With this widget open I clicked on the Lancelot icon and Plasma crashed.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 0 (LWP 11978)]

Thread 2 (Thread 0xa87ffb90 (LWP 11989)):
#0  0xb7ff5430 in __kernel_vsyscall ()
#1  0xb650c0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb66ec2ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7dee172 in QWaitCondition::wait (this=0x9ea7fb8, mutex=0x9ea7fb4, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb772eac2 in QHostInfoAgent::run (this=0x9ea7fa8) at kernel/qhostinfo.cpp:260
#5  0xb7ded132 in QThreadPrivate::start (arg=0x9ea7fa8) at thread/qthread_unix.cpp:188
#6  0xb65084ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb66dd49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb6016a10 (LWP 11978)):
[KCrash Handler]
#6  0xb6fa98fa in QGraphicsItem::isWidget (this=0x9d3fe38) at graphicsview/qgraphicsitem.cpp:1142
#7  0xb6fe3667 in QGraphicsScene::event (this=0x9b1a0c0, event=0xbf90ec30) at graphicsview/qgraphicsscene.cpp:3850
#8  0xb69a2d3c in QApplicationPrivate::notify_helper (this=0x9a7a1e8, receiver=0x9b1a0c0, e=0xbf90ec30) at kernel/qapplication.cpp:4056
#9  0xb69ab03e in QApplication::notify (this=0x9a3c2c8, receiver=0x9b1a0c0, e=0xbf90ec30) at kernel/qapplication.cpp:3603
#10 0xb74b35cd in KApplication::notify (this=0x9a3c2c8, receiver=0x9b1a0c0, event=0xbf90ec30) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#11 0xb7ee1bcb in QCoreApplication::notifyInternal (this=0x9a3c2c8, receiver=0x9b1a0c0, event=0xbf90ec30) at kernel/qcoreapplication.cpp:610
#12 0xb6ff5a75 in QGraphicsView::viewportEvent (this=0x9c90bb8, event=0xbf90ec30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#13 0xb6e4d235 in QAbstractScrollAreaFilter::eventFilter (this=0xa0ccd18, o=0x9ab64d8, e=0xbf90ec30) at widgets/qabstractscrollarea_p.h:100
#14 0xb7ee0dea in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9a7a1e8, receiver=0x9ab64d8, event=0xbf90ec30) at kernel/qcoreapplication.cpp:726
#15 0xb69a2d1a in QApplicationPrivate::notify_helper (this=0x9a7a1e8, receiver=0x9ab64d8, e=0xbf90ec30) at kernel/qapplication.cpp:4052
#16 0xb69ab122 in QApplication::notify (this=0x9a3c2c8, receiver=0x9ab64d8, e=0xbf90ec30) at kernel/qapplication.cpp:4021
#17 0xb74b35cd in KApplication::notify (this=0x9a3c2c8, receiver=0x9ab64d8, event=0xbf90ec30) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#18 0xb7ee1bcb in QCoreApplication::notifyInternal (this=0x9a3c2c8, receiver=0x9ab64d8, event=0xbf90ec30) at kernel/qcoreapplication.cpp:610
#19 0xb69f944d in QWidget::event (this=0x9c90bb8, event=0xbf90ec30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 0xb6daaa53 in QFrame::event (this=0x9c90bb8, e=0xbf90ec30) at widgets/qframe.cpp:559
#21 0xb6e4b72d in QAbstractScrollArea::event (this=0x9c90bb8, e=0xbf90ec30) at widgets/qabstractscrollarea.cpp:918
#22 0xb6ff26a6 in QGraphicsView::event (this=0x9c90bb8, event=0xbf90ec30) at graphicsview/qgraphicsview.cpp:2840
#23 0xb69a2d3c in QApplicationPrivate::notify_helper (this=0x9a7a1e8, receiver=0x9c90bb8, e=0xbf90ec30) at kernel/qapplication.cpp:4056
#24 0xb69ab122 in QApplication::notify (this=0x9a3c2c8, receiver=0x9c90bb8, e=0xbf90ec30) at kernel/qapplication.cpp:4021
#25 0xb74b35cd in KApplication::notify (this=0x9a3c2c8, receiver=0x9c90bb8, event=0xbf90ec30) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#26 0xb7ee1bcb in QCoreApplication::notifyInternal (this=0x9a3c2c8, receiver=0x9c90bb8, event=0xbf90ec30) at kernel/qcoreapplication.cpp:610
#27 0xb69a9c6b in QApplication::setActiveWindow (act=0x9c90bb8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#28 0xb6a197b5 in QApplication::x11ProcessEvent (this=0x9a3c2c8, event=0xbf91017c) at kernel/qapplication_x11.cpp:3469
#29 0xb6a4537a in x11EventSourceDispatch (s=0x9a7cf00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0xb6555b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb65590eb in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb6559268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb7f0d2f8 in QEventDispatcherGlib::processEvents (this=0x9a79e48, flags={i = -1081015496}) at kernel/qeventdispatcher_glib.cpp:327
#34 0xb6a44a75 in QGuiEventDispatcherGlib::processEvents (this=0x9a79e48, flags={i = -1081015448}) at kernel/qguieventdispatcher_glib.cpp:202
#35 0xb7ee01fa in QEventLoop::processEvents (this=0xbf9103e0, flags={i = -1081015384}) at kernel/qeventloop.cpp:149
#36 0xb7ee0642 in QEventLoop::exec (this=0xbf9103e0, flags={i = -1081015320}) at kernel/qeventloop.cpp:201
#37 0xb7ee2ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#38 0xb69a2bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#39 0xb4b69120 in kdemain (argc=1, argv=0x9a54e18) at /build/buildd/kdebase-workspace-4.3.0/plasma/shells/desktop/main.cpp:50
#40 0x0804e27d in launch (argc=1, _name=0x9a03324 "/usr/bin/plasma-desktop", args=0x9a0333c "", cwd=0x0, envc=0, envs=0x9a03340 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x805136d "0") at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:676
#41 0x0804ea5d in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1168
#42 0x0804efe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1361
#43 0x0804fbca in main (argc=2, argv=0xbf910bd4, envp=0xbf910be0) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1788

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-01 23:14:34 UTC
There are some crashes with the same backtrace:
- can you reproduce the crash ?
Thanks
Comment 2 Ivan Čukić 2009-09-02 09:34:16 UTC
Lancelot can not crash the plasma-desktop since it runs in a separate process. Resetting assignee to default.

The backtrace looks like the crash is in Qt since no relevant KDE classes are touched (we've seen some similar crashes here at tokamak)
Comment 3 Dotan Cohen 2009-09-02 09:46:43 UTC
> There are some crashes with the same backtrace:
> can you reproduce the crash ?

Not consistently, and the last one did not have any "stars" in the bug reporting window, so I did not file it. I did not know which -dbg packages to add to make a good report.


> Lancelot can not crash the plasma-desktop since it runs in a
> separate process. Resetting assignee to default

I was not certain that this was a Lancelot crash, I only know that Lancelot was the last application that I interacted with before the crash.
Comment 4 Ivan Čukić 2009-09-02 12:44:17 UTC
Not your fault, just changed it so that it receives the needed attention of others aswell.
Comment 5 Ivan Čukić 2009-09-02 12:47:24 UTC
p.s. when replying, make sure that you reload the page so that you don't cancel the changes i've made to asignee and component again. cheerio
Comment 6 Dotan Cohen 2009-09-02 16:11:11 UTC
> p.s. when replying, make sure that you reload the page so that you don't
> cancel the changes i've made to asignee and component again. cheerio

I will try to remember that, Ivan. It sounds like a bug in bugzilla to me that this could even happen. Usually I see "mid air collision" when I respond to a thread that had a previous response between the time I opened the page until the time that I answer.
Comment 7 Dario Andres 2009-09-04 22:14:11 UTC

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