Bug 219616 - kde applet crash done nothing for hours
Summary: kde applet crash done nothing for hours
Status: RESOLVED DUPLICATE of bug 198294
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-22 01:02 UTC by nospam
Modified: 2009-12-22 01:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nospam 2009-12-22 01:02:20 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Done nothing for hours, the last thing I did was pulling out an usb pendrive, and let a screensaver turn off the display... when coming back the crash reporter screen was waiting

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

Thread 2 (Thread 0xabfb6b70 (LWP 2469)):
#0  0x005b5422 in __kernel_vsyscall ()
#1  0x001d9e15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122
#2  0x00e8a78d in __pthread_cond_wait (cond=0x91d7dd8, mutex=0x91d7dc0) at forward.c:139
#3  0x009b2e67 in QWaitConditionPrivate::wait (this=0x90d1840, mutex=0x90d183c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x90d1840, mutex=0x90d183c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x01c8b922 in QHostInfoAgent::run (this=0x90d1830) at kernel/qhostinfo.cpp:260
#6  0x009b1e32 in QThreadPrivate::start (arg=0x90d1830) at thread/qthread_unix.cpp:188
#7  0x001d580e in start_thread (arg=0xabfb6b70) at pthread_create.c:300
#8  0x00e7d7ee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb76e3700 (LWP 2468)):
[KCrash Handler]
#6  0x0049fd57 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0x04ed170e in qt_x11_getX11InfoForWindow (xinfo=0xaaf4e8c, a=...) at kernel/qwidget_x11.cpp:400
#8  0x04ed8b4e in QWidgetPrivate::create_sys (this=0xaaf4d98, window=27411149, initializeWindow=true, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545
#9  0x04e99b1c in QWidget::create (this=0xab06c88, window=27411149, initializeWindow=true, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1253
#10 0x079f1c1e in SystemTray::X11EmbedContainer::embedSystemTrayClient (this=0xab06c88, clientId=50331768) at ../../../../plasma/applets/systemtray/protocols/fdo/x11embedcontainer.cpp:110
#11 0x079ed3f0 in SystemTray::FdoGraphicsWidget::setupXEmbedDelegate (this=0xad131f8) at ../../../../plasma/applets/systemtray/protocols/fdo/fdographicswidget.cpp:159
#12 0x079ed4cb in SystemTray::FdoGraphicsWidget::qt_metacall (this=0xad131f8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf9a897c) at ./fdographicswidget.moc:78
#13 0x00ab8263 in QMetaObject::activate (sender=0xad27610, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#14 0x00ab8ec2 in QMetaObject::activate (sender=0xad27610, m=0xb92908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#15 0x00abd387 in QSingleShotTimer::timeout (this=0xad27610) at .moc/release-shared/qtimer.moc:76
#16 0x00abd49c in QSingleShotTimer::timerEvent (this=0xad27610) at kernel/qtimer.cpp:298
#17 0x00ab23bf in QObject::event (this=0xad27610, e=0xbf9a8e10) at kernel/qobject.cpp:1075
#18 0x04e42f54 in QApplicationPrivate::notify_helper (this=0x8681770, receiver=0xad27610, e=0xbf9a8e10) at kernel/qapplication.cpp:4056
#19 0x04e4a67c in QApplication::notify (this=0x865a930, receiver=0xad27610, e=0xbf9a8e10) at kernel/qapplication.cpp:3603
#20 0x011a1bfa in KApplication::notify (this=0x865a930, receiver=0xad27610, event=0xbf9a8e10) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x00aa26cb in QCoreApplication::notifyInternal (this=0x865a930, receiver=0xad27610, event=0xbf9a8e10) at kernel/qcoreapplication.cpp:610
#22 0x00acf7ce in QCoreApplication::sendEvent (this=0x8684334) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 QTimerInfoList::activateTimers (this=0x8684334) at kernel/qeventdispatcher_unix.cpp:572
#24 0x00acd0e0 in timerSourceDispatch (source=0x8684300) at kernel/qeventdispatcher_glib.cpp:165
#25 0x00151e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00155730 in ?? () from /lib/libglib-2.0.so.0
#27 0x00155863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x00acd02c in QEventDispatcherGlib::processEvents (this=0x8681560, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0x04ee3be5 in QGuiEventDispatcherGlib::processEvents (this=0x8681560, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x00aa0c79 in QEventLoop::processEvents (this=0xbf9a90d4, flags=) at kernel/qeventloop.cpp:149
#31 0x00aa10ca in QEventLoop::exec (this=0xbf9a90d4, flags=...) at kernel/qeventloop.cpp:201
#32 0x00aa353f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x04e42dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0163180d in kdemain (argc=1, argv=0x86462a0) at ../../../../plasma/shells/desktop/main.cpp:50
#35 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x8614d30 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x80511a5 "0") at ../../kinit/kinit.cpp:677
#36 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#37 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#38 0x0804fbaf in main (argc=2, argv=0xbf9a9934, envp=0xbf9a9940) at ../../kinit/kinit.cpp:1793

This bug may be a duplicate of or related to bug 218341

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-22 01:26:25 UTC
This is fixed in KDE SC 4.4 Thanks

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