Summary: | Plasma crashed while playing with widgets (bubblemon and Yasp) | ||
---|---|---|---|
Product: | [Applications] ksysguard | Reporter: | Thomas Thym <ungethym> |
Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | lotusom-dev |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thomas Thym
2009-05-19 12:55:38 UTC
Still crashing with 4.2.95. This time locking the widgets. No idea if this is a dup of https://bugs.kde.org/show_bug.cgi?id=176014 Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb5e6d700 (LWP 5838))] Thread 3 (Thread 0xb1de6b90 (LWP 5841)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7cedc35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb7d4d582 in QWaitCondition::wait (this=0x8aebab0, mutex=0x8aebaac, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #3 0xb75c5ad2 in QHostInfoAgent::run (this=0x8aebaa0) at kernel/qhostinfo.cpp:260 #4 0xb7d4c572 in QThreadPrivate::start (arg=0x8aebaa0) at thread/qthread_unix.cpp:188 #5 0xb7cea1b5 in start_thread () from /lib/libpthread.so.0 #6 0xb65333be in clone () from /lib/libc.so.6 Thread 2 (Thread 0xa67f7b90 (LWP 7109)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7cedf62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb7d4bf69 in thread_sleep (ti=0xa67f72c0) at thread/qthread_unix.cpp:297 #3 0xb7d4c09b in QThread::msleep (msecs=<value optimized out>) at thread/qthread_unix.cpp:323 #4 0xb24acbd8 in ?? () from /usr/lib/kde4/plasma_applet_cwp.so #5 0xb7d4c572 in QThreadPrivate::start (arg=0xa758670) at thread/qthread_unix.cpp:188 #6 0xb7cea1b5 in start_thread () from /lib/libpthread.so.0 #7 0xb65333be in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5e6d700 (LWP 5838)): [KCrash Handler] #6 0xb23838d6 in KSGRD::SensorManager::sendRequest (this=0xa8e5710, hostName=@0xbfb815c4, req=@0xbfb815f8, client=0x8b2e154, id=386) at /usr/include/QtCore/qhash.h:589 #7 0xb23bbbd1 in SystemMonitorEngine::updateSourceEvent (this=0x8b2e148, sensorName=@0xbfb815f8) at /usr/src/debug/kdebase-workspace-4.2.95/plasma/dataengines/systemmonitor/systemmonitor.cpp:65 #8 0xb5be8905 in Plasma::DataEnginePrivate::internalUpdateSource (this=0x8b00210, source=0x9650178) at /usr/src/debug/kdelibs-4.2.95/plasma/dataengine.cpp:518 #9 0xb5beac3a in Plasma::DataEngine::qt_metacall (this=0x8b2e148, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb8174c) at /usr/src/debug/kdelibs-4.2.95/build/plasma/dataengine.moc:118 #10 0xb23bbb0a in SystemMonitorEngine::qt_metacall (this=0x8b2e148, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb8174c) at /usr/src/debug/kdebase-workspace-4.2.95/build/plasma/dataengines/systemmonitor/systemmonitor.moc:67 #11 0xb7e56788 in QMetaObject::activate (sender=0x9650178, from_signal_index=6, to_signal_index=6, argv=0xbfb8174c) at kernel/qobject.cpp:3113 #12 0xb7e57412 in QMetaObject::activate (sender=0x9650178, m=0xb5d3d124, local_signal_index=2, argv=0xbfb8174c) at kernel/qobject.cpp:3187 #13 0xb5be63f3 in Plasma::DataContainer::updateRequested (this=0x9650178, _t1=0x9650178) at /usr/src/debug/kdelibs-4.2.95/build/plasma/datacontainer.moc:107 #14 0xb5c149b0 in Plasma::SignalRelay::timerEvent (this=0x9c1f8b8, event=0xbfb81bd0) at /usr/src/debug/kdelibs-4.2.95/plasma/private/datacontainer_p.cpp:149 #15 0xb7e5172f in QObject::event (this=0x9c1f8b8, e=0xbfb81bd0) at kernel/qobject.cpp:1075 #16 0xb680a7fc in QApplicationPrivate::notify_helper (this=0x80a9518, receiver=0x9c1f8b8, e=0xbfb81bd0) at kernel/qapplication.cpp:4056 #17 0xb6812aee in QApplication::notify (this=0x80a3248, receiver=0x9c1f8b8, e=0xbfb81bd0) at kernel/qapplication.cpp:3603 #18 0xb72fe10d in KApplication::notify (this=0x80a3248, receiver=0x9c1f8b8, event=0xbfb81bd0) at /usr/src/debug/kdelibs-4.2.95/kdeui/kernel/kapplication.cpp:302 #19 0xb7e4116b in QCoreApplication::notifyInternal (this=0x80a3248, receiver=0x9c1f8b8, event=0xbfb81bd0) at kernel/qcoreapplication.cpp:610 #20 0xb7e705f6 in QTimerInfoList::activateTimers (this=0x80abea4) at kernel/qcoreapplication.h:213 #21 0xb7e6c980 in timerSourceDispatch (source=0x80abe70) at kernel/qeventdispatcher_glib.cpp:165 #22 0xb63b09c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb63b4083 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb63b4241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb7e6c8d8 in QEventDispatcherGlib::processEvents (this=0x80a6b88, flags={i = -1078452872}) at kernel/qeventdispatcher_glib.cpp:327 #26 0xb68aacc5 in QGuiEventDispatcherGlib::processEvents (this=0x80a6b88, flags={i = -1078452824}) at kernel/qguieventdispatcher_glib.cpp:202 #27 0xb7e3f78a in QEventLoop::processEvents (this=0xbfb81e20, flags={i = -1078452760}) at kernel/qeventloop.cpp:149 #28 0xb7e3fbd2 in QEventLoop::exec (this=0xbfb81e20, flags={i = -1078452696}) at kernel/qeventloop.cpp:201 #29 0xb7e42079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0xb680a677 in QApplication::exec () at kernel/qapplication.cpp:3525 #31 0xb48949f0 in kdemain (argc=1, argv=0x80785f0) at /usr/src/debug/kdebase-workspace-4.2.95/plasma/shells/desktop/main.cpp:50 #32 0x0804e2b0 in launch (argc=1, _name=0x808b29c "/usr/bin/plasma-desktop", args=0x808b2b4 "", cwd=0x0, envc=0, envs=0x808b2b8 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051389 "0") at /usr/src/debug/kdelibs-4.2.95/kinit/kinit.cpp:672 #33 0x0804ea8d in handle_launcher_request (sock=7, who=<value optimized out>) at /usr/src/debug/kdelibs-4.2.95/kinit/kinit.cpp:1164 #34 0x0804ef23 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.2.95/kinit/kinit.cpp:1357 #35 0x0804fbca in main (argc=2, argv=0xbfb82604, envp=0xbfb82610) at /usr/src/debug/kdelibs-4.2.95/kinit/kinit.cpp:1784 Just wanted to verify if this was a problem with the system monitoring applet or ksysguard since they are two different application, from reading your report it seems to be a problem with the plasma widget. Could you confirm? Seems to be fixed. No problems in 4.3.0 anymore. |