Kubuntu (13.04) “Plasma Desktop” keeps crashing.

[Robtygart]

I am not sure why but, “Plasma Desktop” keeps crashing, It happens during updates, using update manager or when updating in terminal, the screen will go black for a few seconds then it comes back up again with a crash report.

Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1ee2d527c0 (LWP 1777))]

Thread 4 (Thread 0x7f1ec3346700 (LWP 1778)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:168
#1 0x00007f1edc318cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2 0x00007f1edc318d09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3 0x00007f1ed3bf6734 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#4 0x00007f1ed69bef9f in start_thread (arg=0x7f1ec3346700) at pthread_create.c:311
#5 0x00007f1ee262b0cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 3 (Thread 0x7f1ebc1ab700 (LWP 1779)):
#0 0x00007f1ed69c1075 in __GI___pthread_mutex_lock (mutex=0x7f1eb4000a90) at pthread_mutex_lock.c:95
#1 0x00007f1ed62fce11 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f1ed62bf603 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f1ed62bfc8b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f1ed62bfe84 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f1edf2c1c16 in QEventDispatcherGlib::processEvents (this=0x7f1eb40008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f1edf2922bf in QEventLoop::processEvents (this=this@entry=0x7f1ebc1aacd0, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f1edf292548 in QEventLoop::exec (this=0x7f1ebc1aacd0, flags=...) at kernel/qeventloop.cpp:204
#8 0x00007f1edf193b10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9 0x00007f1edf2729af in QInotifyFileSystemWatcherEngine::run (this=0x1eea660) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f1edf196aec in QThreadPrivate::start (arg=0x1eea660) at thread/qthread_unix.cpp:338
#11 0x00007f1ed3bf6734 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#12 0x00007f1ed69bef9f in start_thread (arg=0x7f1ebc1ab700) at pthread_create.c:311
#13 0x00007f1ee262b0cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 2 (Thread 0x7f1eb3fff700 (LWP 1782)):
#0 0x00007fff07dff847 in clock_gettime ()
#1 0x00007f1ed81ad32d in __GI_clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:115
#2 0x00007f1edf1ec9c4 in do_gettime (frac=0x7f1eb3ffea28, sec=0x7f1eb3ffea20) at tools/qelapsedtimer_unix.cpp:123
#3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4 0x00007f1edf2c241d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f1ea8002860) at kernel/qeventdispatcher_unix.cpp:343
#5 0x00007f1edf2c2763 in QTimerInfoList::timerWait (this=0x7f1ea8002860, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#6 0x00007f1edf2c12cc in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f1eb3ffeb14) at kernel/qeventdispatcher_glib.cpp:136
#7 0x00007f1edf2c1375 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#8 0x00007f1ed62bf5f8 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007f1ed62bfc8b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f1ed62bfe84 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f1edf2c1c16 in QEventDispatcherGlib::processEvents (this=0x7f1ea80008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x00007f1edf2922bf in QEventLoop::processEvents (this=this@entry=0x7f1eb3ffecd0, flags=...) at kernel/qeventloop.cpp:149
#13 0x00007f1edf292548 in QEventLoop::exec (this=0x7f1eb3ffecd0, flags=...) at kernel/qeventloop.cpp:204
#14 0x00007f1edf193b10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#15 0x00007f1edf2729af in QInotifyFileSystemWatcherEngine::run (this=0x259eee0) at io/qfilesystemwatcher_inotify.cpp:248
#16 0x00007f1edf196aec in QThreadPrivate::start (arg=0x259eee0) at thread/qthread_unix.cpp:338
#17 0x00007f1ed3bf6734 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#18 0x00007f1ed69bef9f in start_thread (arg=0x7f1eb3fff700) at pthread_create.c:311
#19 0x00007f1ee262b0cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7f1ee2d527c0 (LWP 1777)):
[KCrash Handler]
#6 QDeclarativeObjectScriptClass::newQObject (this=0x1bbb090, object=0x254ff30, type=136) at qml/qdeclarativeobjectscriptclass.cpp:118
#7 0x00007f1ee0ee77de in QDeclarativeEnginePrivate::scriptValueFromVariant (this=0x1bb7ab0, val=...) at qml/qdeclarativeengine.cpp:2131
#8 0x00007f1ee0f832aa in QDeclarativeObjectScriptClass::property (this=<optimized out>, obj=<optimized out>, name=<optimized out>) at qml/qdeclarativeobjectscriptclass.cpp:320
#9 0x00007f1ee0f88af5 in QDeclarativeContextScriptClass::property (this=0x1bba7b0, object=<optimized out>, name=<optimized out>) at qml/qdeclarativecontextscriptclass.cpp:289
#10 0x00007f1edc38f280 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#11 0x00007f1edc269822 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#12 0x00007f1eb0b7f6aa in ?? ()
#13 0x0000000000000000 in ?? ()

Is there anyway for me to track this down so I can file a worth wile bug report?

[Robtygart]

Also I installed Debuging Symbols. From the crash reporting assistant, it asks to install the "Debuging Symbols" But it never installs them, so I did so using the package manager.

[james147]

You should install the debug symbols if you want a useful backtrace.

Ubuntu splits the debug symbols out of the packages and put them in a separate package with -dbg appended to the name ie: kde-workspace-dbg

Then wait for the crash to happen again.

[Robtygart]

Edit: Just looked at the time stamp. Both at 10:01 lol, you must not have seen my post.

You should install the debug symbols if you want a useful backtrace.

Ubuntu splits the debug symbols out of the packages and put them in a separate package with -dbg appended to the name ie: kde-workspace-dbg

Then wait for the crash to happen again.

Thank you James
But as I said in my second post, installing debug information did not help. I am sure this problem will be fixed (in the next few updates) but since I am having the problem I would like to post a bug report, but I don't know how I should respond to this.

[starbetrayer]

Robtygart,

I migrated to 13.04 last night and I did not this issue.

[sithlord48]

I upgraded to 13.04 alpha1 two days ago on my netbook. i have a crash when i first login of plasma-desktop then it after some time will "just work" if i re-run plasma-desktop.
i wonder if you have any of the following in your machine i386 (32-bit) install , encrypted home folder, intel I915 video card. as for creating a useful bug report you should have the debug (-dbg) package installed, then next crash you should have a more useful dump.

[Guest]

kde mint 64 bit similar bug--noone assigned yet

I upgraded to 13.04 alpha1 two days ago on my netbook. i have a crash when i first login of plasma-desktop then it after some time will "just work" if i re-run plasma-desktop.
i wonder if you have any of the following in your machine i386 (32-bit) install , encrypted home folder, intel I915 video card. as for creating a useful bug report you should have the debug (-dbg) package installed, then next crash you should have a more useful dump.

FYI I had a similar problem using the 64 bit version of KDE linux mint 13, fully updated and with the kde-workspace-dbg package installed, since I saw a post that might've added plasma desktop debug reports as of Dec 18. I reported bug 1089556 on Dec. 12 and no one's been assigned yet. FYI, the boot crash involving some kind of segmentation problem occurs on a laptop, with intel i3 processor but no separate video card (LOL!). Yup, I tried reinstalling the backtrace symbols again today, but still no usable backtrace and I can't find the plasma desktop dbg package to install.

How I hate adding frowning faces during the holidays! But maybe it'll get attention....

[Robtygart]

I haven't been on 13.04 in two days, after the last upgrade that I did nothing would load, I am going to log into the terminal tonight and update && upgrade again. If that does not work I am going to use the latest daily build and reformat.

[blackpaw]

Do you have the veromix widget enabled? it crashes my plasma desktop. I had to edit plasma-desktoprc & plasma-desktop-appletsrc in ~/.kde/share/config to remove it.

There seems to be a problem with python based widgets in general.