FS#34732 - [kdebase-workspace] Plasma Desktop shell crashes often

Attached to Project: Arch Linux
Opened by David Kowis (BeepDog) - Thursday, 11 April 2013, 14:48 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 15 April 2013, 02:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
My kde pops up with a crash report usually about a couple times a day. It usually recovers and I can keep working, but I'd like to find a way to get it fixed.

I'd report it upstream, but it says the generated crash report is not useful. Is there a a way to make it more useful? Or is this an arch bug? I never had any crashes on other distros, as recent as Fedora 18.

a backtrace is:
<backtrace>
Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f49067eb780 (LWP 1120))]

Thread 3 (Thread 0x7f48e532b700 (LWP 1126)):
#0 0x00007f49050b08b4 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007f48f77097a7 in ?? () from /usr/lib/libQtScript.so.4
#2 0x00007f48f77097d9 in ?? () from /usr/lib/libQtScript.so.4
#3 0x00007f48f3eb91b4 in ?? () from /usr/lib/libGL.so.1
#4 0x00007f49050acdd2 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007f4903e36ced in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f4857b99700 (LWP 1128)):
#0 0x00007f4903e2e09d in poll () from /usr/lib/libc.so.6
#1 0x00007f4900d80b14 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f4900d80c34 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3 0x00007f4905467b86 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4 0x00007f49054383ff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5 0x00007f4905438688 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6 0x00007f49053398a0 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7 0x00007f4905418bbf in ?? () from /usr/lib/libQtCore.so.4
#8 0x00007f490533c87c in ?? () from /usr/lib/libQtCore.so.4
#9 0x00007f48f3eb91b4 in ?? () from /usr/lib/libGL.so.1
#10 0x00007f49050acdd2 in start_thread () from /usr/lib/libpthread.so.0
#11 0x00007f4903e36ced in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f49067eb780 (LWP 1120)):
[KCrash Handler]
#5 0x00007f490544d86e in QMetaObject::addGuard(QObject**) () from /usr/lib/libQtCore.so.4
#6 0x00007f48f6f106de in ?? () from /usr/lib/libQtDeclarative.so.4
#7 0x00007f490544eb8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#8 0x00007f48f7055abf in ?? () from /usr/lib/libQtDeclarative.so.4
#9 0x00007f48f6f2760c in ?? () from /usr/lib/libQtDeclarative.so.4
#10 0x00007f48f70560f1 in ?? () from /usr/lib/libQtDeclarative.so.4
#11 0x00007f490544eb8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0x00007f48f704a54f in QListModelInterface::itemsRemoved(int, int) () from /usr/lib/libQtDeclarative.so.4
#13 0x00007f48f6e9305f in QDeclarativeListModel::remove(int) () from /usr/lib/libQtDeclarative.so.4
#14 0x00007f48f704911b in ?? () from /usr/lib/libQtDeclarative.so.4
#15 0x00007f48f704921f in QDeclarativeListModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDeclarative.so.4
#16 0x00007f48f6ff3d28 in ?? () from /usr/lib/libQtDeclarative.so.4
#17 0x00007f48f6ff5996 in ?? () from /usr/lib/libQtDeclarative.so.4
#18 0x00007f48f6ff62cb in ?? () from /usr/lib/libQtDeclarative.so.4
#19 0x00007f48f777fc63 in ?? () from /usr/lib/libQtScript.so.4
#20 0x00007f48f767be60 in ?? () from /usr/lib/libQtScript.so.4
#21 0x00007f48f765906a in ?? () from /usr/lib/libQtScript.so.4
#22 0x00007f48601c0480 in ?? ()
#23 0x0000000000000000 in ?? ()
</backtrace>

Additional info:
local/kdebase-plasma 4.10.2-1 (kde kdebase)


Steps to reproduce:
Just use the computer for a while.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 15 April 2013, 02:01 GMT
Reason for closing:  Upstream
Comment by Andrea Scarpino (BaSh) - Thursday, 11 April 2013, 16:00 GMT
Please try wiping /var/tmp/kde*. If the crash still persist, then try with a different user.
Comment by Ike Devolder (BlackEagle) - Thursday, 11 April 2013, 16:13 GMT
Just a small question, are you using choqok ?

The crash really went away after switching from choqok to hotot for twitter

it was already reduced alot after wiping /var/tmp/kde*
Comment by David Kowis (BeepDog) - Thursday, 11 April 2013, 16:43 GMT
Interesting. I am using choqok. I'll try first one then the other.

Right now, I'm stupid busy at work, and as this is my work box, it might have to wait a bit.

Thanks. :)
Comment by David Kowis (BeepDog) - Friday, 12 April 2013, 19:17 GMT
So clobbered /var/tmp/kde* and it crashed again. Interestingly enough, it did correspond with choqok telling me about a new item in my twitter feed :(

So I have turned off choqok, and shall see if that rectifies it as well.

Sadly, the current hotot in AUR has the KDE build disabled :(
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 15 April 2013, 02:01 GMT
This is most definitely an upstream bug judging by all that has been said. Please open this bug upstream against choqok. It obviously misbehaves. KDE devs will be much better suited for fixing this problem for you.

Loading...