Arch Linux

potzi

Member

Registered: 2009-01-05

Posts: 12

[SOLVED] Plasma workspace crash (SIGSEGV) at login after update

Hi all,

after I updated via pacman -Syu last weekend and rebooted my system I got a plasma workspace crash at the login which happens ever since.

I get:

The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

and the following bug report:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb496f720 (LWP 3637)]
[New Thread 0xa928bb70 (LWP 3638)]
0xb8054424 in __kernel_vsyscall ()
[Current thread is 0 (LWP 3637)]

Thread 2 (Thread 0xa928bb70 (LWP 3638)):
#0  0xb8054424 in __kernel_vsyscall ()
#1  0xb635ac55 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb63d83e7 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xa95709f2 in RenderThread::run () from /usr/lib/kde4/plasma_wallpaper_image.so
#4  0xb63d73be in ?? () from /usr/lib/libQtCore.so.4
#5  0xb63566bc in start_thread () from /lib/libpthread.so.0
#6  0xb61a2ffe in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb496f720 (LWP 3637)):
#0  0xb8054424 in __kernel_vsyscall ()
#1  0xb616cb26 in nanosleep () from /lib/libc.so.6
#2  0xb616c911 in sleep () from /lib/libc.so.6
#3  0xb76cce12 in KCrash::startDrKonqi () from /usr/lib/libkdeui.so.5
#4  0xb76cda84 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb645fb57 in QIODevice::isOpen () from /usr/lib/libQtCore.so.4
#7  0xb6809ee7 in QImageReader::supportedImageFormats () from /usr/lib/libQtGui.so.4
#8  0xb6762e06 in ?? () from /usr/lib/libQtGui.so.4
#9  0xb6763fbc in ?? () from /usr/lib/libQtGui.so.4
#10 0xb7b5940f in KIO::pasteActionText () from /usr/lib/libkio.so.5
#11 0xa9525406 in FolderView::createActions () from /usr/lib/kde4/plasma_applet_folderview.so
#12 0xa952adda in FolderView::init () from /usr/lib/kde4/plasma_applet_folderview.so
#13 0xb7ffd6d7 in DesktopCorona::saveDefaultSetup () from /usr/lib/libkdeinit4_plasma.so
#14 0xb7ffdf18 in DesktopCorona::qt_metacall () from /usr/lib/libkdeinit4_plasma.so
#15 0xb64de831 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb64df4a2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb64e3967 in ?? () from /usr/lib/libQtCore.so.4
#18 0xb64e3a7c in ?? () from /usr/lib/libQtCore.so.4
#19 0xb64d879f in QObject::event () from /usr/lib/libQtCore.so.4
#20 0xb674d6ac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#21 0xb6754e44 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb7656bfa in KApplication::notify () from /usr/lib/libkdeui.so.5
#23 0xb64c874b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#24 0xb64f6a26 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb64f3ad0 in ?? () from /usr/lib/libQtCore.so.4
#26 0xb4db0288 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb4db3878 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#28 0xb4db39ea in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb64f3a1c in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb67ec5c5 in ?? () from /usr/lib/libQtGui.so.4
#31 0xb64c6cd9 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb64c7122 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#33 0xb64c949f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#34 0xb674d527 in QApplication::exec () from /usr/lib/libQtGui.so.4
#35 0xb8003e16 in kdemain () from /usr/lib/libkdeinit4_plasma.so
#36 0x0804876b in _start ()
#0  0xb8054424 in __kernel_vsyscall ()

The packages I've updated befor this bug appeared are:

[2009-05-24 09:55] upgraded dbus-core (1.2.4.6permissive-1 -> 1.2.14-1)
[2009-05-24 09:55] upgraded dbus (1.2.4.6permissive-1 -> 1.2.14-1)
[2009-05-24 09:55] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-05-24 09:55]  
[2009-05-24 09:55]  > Qt 4.5.1
[2009-05-24 09:55]  
[2009-05-24 09:55]    Prefix: /usr
[2009-05-24 09:55]  
[2009-05-24 09:55]  > ATTENTION 
[2009-05-24 09:55]    Some components are split into separate packages:
[2009-05-24 09:55]  
[2009-05-24 09:55]    qtmod       : Base libraries and tools
[2009-05-24 09:55]    qtmod-doc   : Documentation
[2009-05-24 09:55]    qtmod-demos : Demos & Examples
[2009-05-24 09:55]    qtmod-tools : Development Tools (Assistant, Designer, Linguist)
[2009-05-24 09:55]  
[2009-05-24 09:55] upgraded qtmod (4.5.1-2 -> 4.5.1-3)

However I've downgraded all of them back but the crash remains. I also removed qtmod and installed qt from the arch repositories but still no effect on the bug. Also tried to rename the .kde4/ folder to make KDE generating a new plain folder but doesn't help with the problem. Even complete removal of KDEmod and new installation didn't make a change.

I hope someone can help cause I'm runnig out of ideas what to try next.

thanks, potzi

Last edited by potzi (2009-06-03 22:43:52)

tim

Member

From: Sweden

Registered: 2006-10-29

Posts: 98

Re: [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

Have you tried adding a new user and loging in as the new user?

This same thing happens to me when running 32bit opensuse with the all latest KDE packages from their testing repo. sometimes I can fix it by deleting the plasma-desktoprc file and sometimes the only way I can ever fix it is to create a new user and start again.

Perhaps it's qt. Have you tried downgrading it to something before 4.5.x?

Good luck.

Last edited by tim (2009-05-26 13:42:12)

djgera

Developer

From: Buenos Aires - Argentina

Registered: 2008-12-24

Posts: 723

Website

Re: [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

Try to delete all plasma/kde cache related files, these are on:

/tmp/ksocket-yourusername
/tmp/kde-yourusername
/var/tmp/kdecache-yourusername

potzi

Member

Registered: 2009-01-05

Posts: 12

Re: [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

Hi,

tanks for the suggestions!

@ djgera: I tried deleting those files but unfortunately no change to the crash.

@ tim: the new user account did the trick. the only probelm is now how to get all my settings from my old user account to the new one. would be awsome if you have some tips there since you had to deal with this issue as well. Another thing ... where can you get qt versions older than 4.5.x ?

thanks

tim

Member

From: Sweden

Registered: 2006-10-29

Posts: 98

Re: [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

You can find old packages here:

http://arm.kh.nu/

That repo has saved my life a number of times. Especially with BLUETOOTH GRRRR.

As for getting all your old settings back, I didn't investigate this enough because i only have opensuse for curiosity as I think they do some really great stuff.
Basically I hadn't yet isolated what was causing the problems before I gave up because every time I tried to merge my old settings in to the new user account, I recreated the problem. No logical (subjective term obviously) separation of what to merge and what not to merge worked. So I gave up and just did everything manually. Sorry that I couldn't be more helpful.

Last edited by tim (2009-05-27 23:59:53)

potzi

Member

Registered: 2009-01-05

Posts: 12

Re: [SOLVED] Plasma workspace crash (SIGSEGV) at login after update

The bug didn't come up again after I installed the new KDEmod 4.2.4 packages. THANK GOD. Everything fine again

Thank for the help and suggestions anyway.