Bug 225021 - Plasma crashes going in energy saving mode
Summary: Plasma crashes going in energy saving mode
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: 2010-01-31 17:28 UTC by Louis Boulais
Modified: 2010-01-31 18:21 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 Louis Boulais 2010-01-31 17:28:29 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-18-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
System was going in energy saving mode when this happened. Screen saver (empty screen) had been manually put on. when I came back to computer morning after, crash report warning was on screen.

 -- Backtrace:
Application: Espace de travail Plasma (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7862700 (LWP 1686))]

Thread 2 (Thread 0x60bfb70 (LWP 1708)):
#0  0x007ed422 in __kernel_vsyscall ()
#1  0x004dfe15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x0778087d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x0015fe67 in QWaitConditionPrivate::wait (this=0x8daef10, mutex=0x8daef0c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x8daef10, mutex=0x8daef0c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x02ddd922 in QHostInfoAgent::run (this=0x8daef00) at kernel/qhostinfo.cpp:260
#6  0x0015ee32 in QThreadPrivate::start (arg=0x8daef00) at thread/qthread_unix.cpp:188
#7  0x004db80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x077738de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7862700 (LWP 1686)):
[KCrash Handler]
#6  0x003a6d57 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0x0119e70e in qt_x11_getX11InfoForWindow (xinfo=0xa155f1c, a=...) at kernel/qwidget_x11.cpp:400
#8  0x011a5b4e in QWidgetPrivate::create_sys (this=0xa155e28, window=29539943, initializeWindow=true, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545
#9  0x01166b1c in QWidget::create (this=0xa184790, window=29539943, initializeWindow=true, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1253
#10 0x06757c5e in SystemTray::X11EmbedContainer::embedSystemTrayClient (this=0xa184790, clientId=62914620) at ../../../../plasma/applets/systemtray/protocols/fdo/x11embedcontainer.cpp:110
#11 0x06753440 in SystemTray::FdoGraphicsWidget::setupXEmbedDelegate (this=0xa168760) at ../../../../plasma/applets/systemtray/protocols/fdo/fdographicswidget.cpp:159
#12 0x0675351b in SystemTray::FdoGraphicsWidget::qt_metacall (this=0xa168760, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd9408c) at ./fdographicswidget.moc:78
#13 0x00265263 in QMetaObject::activate (sender=0xa1077c0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#14 0x00265ec2 in QMetaObject::activate (sender=0xa1077c0, m=0x33f908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#15 0x0026a387 in QSingleShotTimer::timeout (this=0xa1077c0) at .moc/release-shared/qtimer.moc:76
#16 0x0026a49c in QSingleShotTimer::timerEvent (this=0xa1077c0) at kernel/qtimer.cpp:298
#17 0x0025f3bf in QObject::event (this=0xa1077c0, e=0xbfd94520) at kernel/qobject.cpp:1075
#18 0x0110ff54 in QApplicationPrivate::notify_helper (this=0x8a64858, receiver=0xa1077c0, e=0xbfd94520) at kernel/qapplication.cpp:4056
#19 0x0111767c in QApplication::notify (this=0x8a5ea48, receiver=0xa1077c0, e=0xbfd94520) at kernel/qapplication.cpp:3603
#20 0x00c4625a in KApplication::notify (this=0x8a5ea48, receiver=0xa1077c0, event=0xbfd94520) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x0024f6cb in QCoreApplication::notifyInternal (this=0x8a5ea48, receiver=0xa1077c0, event=0xbfd94520) at kernel/qcoreapplication.cpp:610
#22 0x0027c7ce in QCoreApplication::sendEvent (this=0x8a66934) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 QTimerInfoList::activateTimers (this=0x8a66934) at kernel/qeventdispatcher_unix.cpp:572
#24 0x0027a0e0 in timerSourceDispatch (source=0x8a66900) at kernel/qeventdispatcher_glib.cpp:165
#25 0x00f30e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00f34730 in ?? () from /lib/libglib-2.0.so.0
#27 0x00f34863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x0027a02c in QEventDispatcherGlib::processEvents (this=0x8a64648, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0x011b0be5 in QGuiEventDispatcherGlib::processEvents (this=0x8a64648, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x0024dc79 in QEventLoop::processEvents (this=0xbfd947e4, flags=) at kernel/qeventloop.cpp:149
#31 0x0024e0ca in QEventLoop::exec (this=0xbfd947e4, flags=...) at kernel/qeventloop.cpp:201
#32 0x0025053f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x0110fdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x01c108ad in kdemain (argc=1, argv=0x8a24de0) 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=0x8a064f8 "", 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=0xbfd95044, envp=0xbfd95050) at ../../kinit/kinit.cpp:1793

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-31 18:21:48 UTC
This is fixed in KDE SC 4.4 Regards

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