Bug 250201 - plasma crashes after closing the scripts window
Summary: plasma crashes after closing the scripts window
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-04 21:31 UTC by yerko
Modified: 2010-09-07 22:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.80 KB, text/plain)
2010-09-07 22:38 UTC, dramascus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description yerko 2010-09-04 21:31:11 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.32-25-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: I disabled a script from the sripts window and clicked on OK.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0xb6163940 (LWP 1645))]

Thread 3 (Thread 0xac8b2b70 (LWP 1647)):
#0  0x03ac6e16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x038cc48b in do_gettime () at tools/qelapsedtimer_unix.cpp:105
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:119
#3  0x039a2965 in QTimerInfoList::updateCurrentTime (this=0x9d38134) at kernel/qeventdispatcher_unix.cpp:339
#4  0x039a29aa in QTimerInfoList::timerWait (this=0x9d38134, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x039a0a38 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xac8b20ac) at kernel/qeventdispatcher_glib.cpp:136
#6  0x039a0ac5 in timerSourcePrepare (source=0x0, timeout=0x3acaff4) at kernel/qeventdispatcher_glib.cpp:169
#7  0x02861aca in g_main_context_prepare () from /lib/libglib-2.0.so.0
#8  0x02861ee9 in ?? () from /lib/libglib-2.0.so.0
#9  0x028624b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#10 0x039a082f in QEventDispatcherGlib::processEvents (this=0x9d25b20, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#11 0x03970a99 in QEventLoop::processEvents (this=0xac8b2280, flags=) at kernel/qeventloop.cpp:149
#12 0x03970f1a in QEventLoop::exec (this=0xac8b2280, flags=...) at kernel/qeventloop.cpp:201
#13 0x0386dc5e in QThread::exec (this=0x9d346c0) at thread/qthread.cpp:490
#14 0x0394f9ab in QInotifyFileSystemWatcherEngine::run (this=0x9d346c0) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x03870f39 in QThreadPrivate::start (arg=0x9d346c0) at thread/qthread_unix.cpp:266
#16 0x004fe96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#17 0x001dda4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xaadd3b70 (LWP 1760)):
#0  0x00574422 in __kernel_vsyscall ()
#1  0x00503015 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x001ea9dd in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x01e2851d in ?? () from /usr/lib/libQtWebKit.so.4
#4  0x01e28601 in ?? () from /usr/lib/libQtWebKit.so.4
#5  0x004fe96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#6  0x001dda4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb6163940 (LWP 1645)):
[KCrash Handler]
#7  0x02dea0fc in TaskManager::Task::icon(int, int, bool) () from /usr/lib/libtaskmanager.so.4
#8  0x02dab0ea in ?? () from /usr/lib/kde4/plasma_applet_daisy.so
#9  0x02db2763 in ?? () from /usr/lib/kde4/plasma_applet_daisy.so
#10 0x03977d4a in QMetaObject::metacall (object=0x95bb528, cl=QMetaObject::InvokeMetaMethod, idx=-1080102284, argv=0x20) at kernel/qmetaobject.cpp:237
#11 0x0398aab5 in QMetaObject::activate (sender=0x941ad78, m=0x1114fec, local_signal_index=9, argv=0xbf9ef3d4) at kernel/qobject.cpp:3280
#12 0x0109efa9 in KWindowSystem::windowChanged (this=0x941ad78, _t1=56624560, _t2=0xbf9ef434) at ./kwindowsystem.moc:178
#13 0x010a2556 in KWindowSystemPrivate::x11Event (this=0x93fff78, ev=0xbf9ef92c) at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:184
#14 0x00f3b51a in KAppX11HackWidget::publicx11Event (this=0x9299cb0, _event=0xbf9ef92c) at ../../kdeui/kernel/kapplication.cpp:915
#15 KApplication::x11EventFilter (this=0x9299cb0, _event=0xbf9ef92c) at ../../kdeui/kernel/kapplication.cpp:966
#16 0x002f9c3a in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#17 0x06d22440 in qt_x11EventFilter (ev=0xbf9ef92c) at kernel/qapplication_x11.cpp:408
#18 0x06d32e80 in QApplication::x11ProcessEvent (this=0x9299cb0, event=0xbf9ef92c) at kernel/qapplication_x11.cpp:3248
#19 0x06d6356a in x11EventSourceDispatch (s=0x92af0a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#20 0x0285e5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x028622d8 in ?? () from /lib/libglib-2.0.so.0
#22 0x028624b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#23 0x039a07f5 in QEventDispatcherGlib::processEvents (this=0x926a568, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#24 0x06d62de5 in QGuiEventDispatcherGlib::processEvents (this=0x926a568, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x03970a99 in QEventLoop::processEvents (this=0xbf9efc24, flags=) at kernel/qeventloop.cpp:149
#26 0x03970f1a in QEventLoop::exec (this=0xbf9efc24, flags=...) at kernel/qeventloop.cpp:201
#27 0x039754cf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#28 0x06ca05a7 in QApplication::exec () at kernel/qapplication.cpp:3672
#29 0x002e2b1e in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#30 0x0804860b in _start ()

Possible duplicates by query: bug 250063, bug 248454, bug 248328, bug 248309, bug 247673.

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2010-09-05 02:56:35 UTC
#8  0x02dab0ea in ?? () from /usr/lib/kde4/plasma_applet_daisy.so

3rd party addon. not plasma. remove daisy and your problems will go away.
Comment 2 yerko 2010-09-05 03:20:27 UTC
but for being 100% sure... I was using amarok and I closed the scripts window (after disabling a script) when plasma-desktop crashed. Does amarok anything to do with the bug?
Comment 3 Aaron J. Seigo 2010-09-05 03:55:50 UTC
"Does amarok anything to do with the bug?"

no.
Comment 4 dramascus 2010-09-07 22:38:49 UTC
Created attachment 51406 [details]
New crash information added by DrKonqi

Happens most of the time. 
I'm running five panels and the widgets; Daisy, fuzzyclock, systray, smooth tasks, kickstart, picture frame, notes. 
At the time of the crash I am usually running kopete, and often times firefox. Though the crash has happened without these programs running as well so it's probably not related.