You are not logged in.

#1 2010-08-01 19:13:23

dhave
Arch Linux f@h Team Member
From: Outside the matrix.
Registered: 2005-05-15
Posts: 1,112

[SOLVED] KDE4.4.5 multiple krunner errors at launch

All of a sudden KDE won't launch properly. I get a series of 70+ KDE Crash Handler messages, all with some variation on this:

"Details: Executable: krunner PID: 6078 Signal: 7 (Bus error)"

This is all that I get when I check the debug info:

Application: Run Command Interface (krunner), signal: Bus error
[KCrash Handler]
#5  0x00007f64023af58b in KPixmapCache::Private::mmapFile(QString const&, KPixmapCache::Private::MmapInfo*, int) () from /usr/lib/libkdeui.so.5
#6  0x00007f64023b1afd in KPixmapCache::Private::mmapFiles() () from /usr/lib/libkdeui.so.5
#7  0x00007f64023b0a90 in KPixmapCache::recreateCacheFiles() () from /usr/lib/libkdeui.so.5
#8  0x00007f64023b1141 in KPixmapCache::Private::checkFileVersion(QString const&) () from /usr/lib/libkdeui.so.5
#9  0x00007f64023b17f0 in KPixmapCache::Private::init() () from /usr/lib/libkdeui.so.5
#10 0x00007f64023b1979 in KPixmapCache::timestamp() const () from /usr/lib/libkdeui.so.5
#11 0x00007f64028e3e50 in Plasma::Theme::findInCache(QString const&, QPixmap&, unsigned int) () from /usr/lib/libplasma.so.3
#12 0x00007f64028e1b06 in ?? () from /usr/lib/libplasma.so.3
#13 0x00007f64028dd296 in Plasma::Svg::pixmap(QString const&) () from /usr/lib/libplasma.so.3
#14 0x00007f6405a10084 in ?? () from /usr/lib/libkdeinit4_krunner.so
#15 0x00007f6405a0cd34 in ?? () from /usr/lib/libkdeinit4_krunner.so
#16 0x00007f6405a0d9e3 in ?? () from /usr/lib/libkdeinit4_krunner.so
#17 0x00007f6405a0da35 in ?? () from /usr/lib/libkdeinit4_krunner.so
#18 0x00007f6405a0e1c5 in kdemain () from /usr/lib/libkdeinit4_krunner.so
#19 0x00007f64056a6c4d in __libc_start_main () from /lib/libc.so.6
#20 0x00000000004005c9 in _start ()

I don't see that I've updated any packages in the past 24 hours or so. This problem wasn't there last night, but when I rebooted this morning, ugh.

Any help greatly appreciated.

Aside: While this problem may well be due to user error (or user ignorance), I'm starting to feel as if KDE is becoming nearly as opaque as Windows in its behavior and error reporting.

Thanks.

Last edited by dhave (2010-08-02 14:47:38)


Donate to Arch!

Tired? There's a nap for that. --anonymous

Offline

#2 2010-08-01 19:41:30

dhave
Arch Linux f@h Team Member
From: Outside the matrix.
Registered: 2005-05-15
Posts: 1,112

Re: [SOLVED] KDE4.4.5 multiple krunner errors at launch

Additional info from OP:

Since KDE4.4.5 starts fine as root, I archived then deleted the contents of my ~/.kde4. When I rebooted and tried to relaunch KDE as user, it gave me the same error as reported in the post above.

Is there other config info that may be at fault and whose deletion may permit kde to launch for my user?

Thanks.


Donate to Arch!

Tired? There's a nap for that. --anonymous

Offline

#3 2010-08-01 20:15:27

Vamp898
Member
From: 東京
Registered: 2009-01-03
Posts: 909
Website

Re: [SOLVED] KDE4.4.5 multiple krunner errors at launch

Oh damm that looks bad... i never had an issue like that but it doesn´t looks like its KDEs fault but try this

rm -rf .kde4 .config/akonadi

then when you start KDE from KDM tail -f the output of /var/log/messages.log and tail -f the output of $HOME/.xsession-errors

Offline

#4 2010-08-02 01:52:58

dhave
Arch Linux f@h Team Member
From: Outside the matrix.
Registered: 2005-05-15
Posts: 1,112

Re: [SOLVED] KDE4.4.5 multiple krunner errors at launch

Thanks, Vamp898. I'll give this a shot and get back to you.


Donate to Arch!

Tired? There's a nap for that. --anonymous

Offline

#5 2010-08-02 02:03:49

dhave
Arch Linux f@h Team Member
From: Outside the matrix.
Registered: 2005-05-15
Posts: 1,112

Re: [SOLVED] KDE4.4.5 multiple krunner errors at launch

I got it fixed.

The cause: I had done an overnight backup to what I thought was a remote location. In fact, I misconfigured my backup script and sent the backup to a local file instead. The result was that one of my partitions filled to the brim.

I wish the system had let me know. Maybe it tried and I didn't notice or didn't check system mail or something.

At any rate, rather than sending out some kind of warning, KDE, when it didn't have space to launch properly, ran through a humongous number of krunner attempts and logged a fairly non-informative screen message each time (see first post).

I got the solution from a stray message on one of the LinuxQuestions.org forums that reported similar symptoms when some tmp or log files grew so big that KDE didn't have room to launch. That's when I finally decided to run df and see what the status of my partitions was. Zero percent free in /dev/sda3 was the culprit. I normally have about 60 percent free on that partition. Zapping those wrongly placed backup files gave me my space back and let KDE start.

Thanks!

Last edited by dhave (2010-08-02 02:07:44)


Donate to Arch!

Tired? There's a nap for that. --anonymous

Offline

Board footer

Powered by FluxBB