[KDE4 on i686] Unable to start KDE4 ( plasma error )

Potomac · 2013-08-20 01:31:20

I did a "pacman -Syu",

KDE was upgraded to KDE 4.11 and glibc to the last version ( 2.18-2 )

but when I did a reboot KDE4.11 can't start, plasma fails to start ( segfault ), it's a critical bug because I can not use KDE4.11, here is the backtrace :

Application: Outil de gestion de fenêtres Plasma (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb549c740 (LWP 464))]

Thread 3 (Thread 0xae29bb40 (LWP 476)):
#0  0xb777b424 in __kernel_vsyscall ()
#1  0xb6c3ac5b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#2  0xb0df0ed2 in ?? () from /usr/lib/libQtScript.so.4
#3  0xb0df0f1f in ?? () from /usr/lib/libQtScript.so.4
#4  0xb6c36ee0 in start_thread () from /usr/lib/libpthread.so.0
#5  0xb5fd801e in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0xa6141b40 (LWP 505)):
#0  0xb599be14 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#1  0xb599c39a in ?? () from /usr/lib/libglib-2.0.so.0
#2  0xb599c548 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0xb6df19af in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4  0xb6dc0ec3 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5  0xb6dc11e9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0xb6cafb1d in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0xb6da1354 in ?? () from /usr/lib/libQtCore.so.4
#8  0xb6cb240f in ?? () from /usr/lib/libQtCore.so.4
#9  0xb6c36ee0 in start_thread () from /usr/lib/libpthread.so.0
#10 0xb5fd801e in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0xb549c740 (LWP 464)):
[KCrash Handler]
#6  0xb6cfcfc6 in QString::fromLatin1_helper(char const*, int) () from /usr/lib/libQtCore.so.4
#7  0xa6f3c395 in Akonadi::ServerManager::instanceIdentifier() () from /usr/lib/libakonadi-kde.so.4
#8  0xa6f3c3f6 in ?? () from /usr/lib/libakonadi-kde.so.4
#9  0xa6f3c6aa in Akonadi::ServerManager::serviceName(Akonadi::ServerManager::ServiceType) () from /usr/lib/libakonadi-kde.so.4
#10 0xa6f3d102 in Akonadi::ServerManager::state() () from /usr/lib/libakonadi-kde.so.4
#11 0xa6f3dc5f in ?? () from /usr/lib/libakonadi-kde.so.4
#12 0xb6dd386a in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#13 0xb6ddb6bb in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb62bd9a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb62c43b3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb75076a4 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb6dc245a in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb6dc579d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#19 0xb6dc5cac in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#20 0xb6df219e in ?? () from /usr/lib/libQtCore.so.4
#21 0xb599c0de in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb599c488 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb599c548 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6df198f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb636d41e in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6dc0ec3 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb6dc11e9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb6dc698e in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#29 0xb62bbe44 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#30 0xaf999937 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#31 0x0804f3ab in _start ()

I have the same problem with a PC and a laptop, so it's probably a problem between kde4.11 and glibc, I don't understand why this bug was not detected during the testing period

my system is a i686 CPU

Last edited by Potomac (2013-08-20 14:46:10)

Potomac · 2013-08-20 01:41:36

I create a bug report :

https://bugs.archlinux.org/index.php?do … k_id=36604

cfr · 2013-08-20 02:19:06

It might help to clarify here and in the bug report if the segmentation fault problem is specific to i686 systems. I'm using 64 bit and it works fine here even though I didn't remove ~/.kde4. If KDE or QT were not built against updated libraries, I'd not expect that, so I'm thinking it might be architecture or system specific.

You should also clarify that your system is up-to-date (except for any downgrades to work around this specific problem) i.e. fully up-to-date when the crashes occur.

Last edited by cfr (2013-08-20 02:19:46)

Potomac · 2013-08-20 02:26:12

like I said in the bug report I did a "pacman -Syu", that means my system is up to date,

and I said also that my system is i686 archlinux version,

I tried also to delete ~/kde4 and ~/kde but it doesn't work, the problem is still here, plasma-desktop still crashes with a segfault

Last edited by Potomac (2013-08-20 02:27:33)

cfr · 2013-08-20 02:29:17

I wasn't directing that at you but more at other people reporting the same issue. (Or people with the same hardware but not seeing it.)

Potomac · 2013-08-20 03:09:11

I found a workaround :

edit the file /usr/share/autostart/plasma-desktop.desktop

and replace the line:

Exec=plasma-desktop

by this :

Exec=sleep 10 && plasma-desktop

the segfault is gone and KDE 4.11 now can start without problem,

this workaround was found in a gentoo forum :

http://forums.gentoo.org/viewtopic-t-967222.html

tonix · 2013-08-21 11:07:28

On the Gentoo forum (same post) a bit further down you also can use the following workaround in the same file:

Exec=LANG=C plasma-desktop

This works for me and saves a 10 seconds sleep during startup.

Cheers,

Ton

Potomac · 2013-08-21 12:46:27

tonix wrote:

On the Gentoo forum (same post) a bit further down you also can use the following workaround in the same file:
Exec=LANG=C plasma-desktop
This works for me and saves a 10 seconds sleep during startup.
Cheers,
Ton

it's not a good workaround because the language of KDE will be "english" instead of "french" in my case if I use your workaround ( I'm French )

a generic workaround like the "sleep 10" trick is more likeable for users who are not using an english installation of KDE

Last edited by Potomac (2013-08-21 12:48:00)

nilesh · 2013-08-21 15:33:05

What's the issue, actually? And why it doesn't cause problems on 64 bit?

david_goliath · 2013-08-21 15:37:02

Hi Potomac,
your workaround doesn't entirely work for me after upgrade to kdebase-workspace 4.11.0-2. kde starts but I get several kde components that crash.
I can post more details later if that helps.
cheers I'm half french :-)

LinuxChick · 2013-08-21 16:43:42

this workaround seems to have worked for me, nothing else kde related has crashed

Potomac · 2013-08-21 17:43:15

david_goliath wrote:

Hi Potomac,
your workaround doesn't entirely work for me after upgrade to kdebase-workspace 4.11.0-2. kde starts but I get several kde components that crash.
I can post more details later if that helps.
cheers I'm half french :-)

check if your /usr/share/autostart/plasma-desktop.desktop still have the line "Exec=sleep 10 && plasma-desktop"

because after the update of the kdebase-workspace package you will have to redo the workaround

you can also set this line in this file :

X-DBUS-StartupType=unique

instead of

X-DBUS-StartupType=multiple

david_goliath · 2013-08-22 10:45:25

weird, after reboot the crashes don't occur any more. As if my computer had sorted out some bucks over night. muha. *g*.
My configuration in

/usr/share/autostart/plasma-desktop.desktop

now even looks as follows

[Desktop Entry]
Exec=sleep .1 && plasma-desktop
X-DBUS-StartupType=multi

hope the crashes won't occur any more. Thanks for the help everyone.

cfr · 2013-08-22 21:41:49

You edited it to add the sleep, right? That's not the default...

Arch Linux

#1 2013-08-20 01:31:20

[KDE4 on i686] Unable to start KDE4 ( plasma error )

#2 2013-08-20 01:41:36

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#3 2013-08-20 02:19:06

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#4 2013-08-20 02:26:12

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#5 2013-08-20 02:29:17

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#6 2013-08-20 03:09:11

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#7 2013-08-21 11:07:28

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#8 2013-08-21 12:46:27

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#9 2013-08-21 15:33:05

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#10 2013-08-21 15:37:02

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#11 2013-08-21 16:43:42

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#12 2013-08-21 17:43:15

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#13 2013-08-22 10:45:25

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

#14 2013-08-22 21:41:49

Re: [KDE4 on i686] Unable to start KDE4 ( plasma error )

Board footer