You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Friday, July 4th 2008, 9:02pm

KDE4 crash and recovery

Hi
Already posted the crash as a bug under 165743
But what I want to do is to get an operational KDE system again and I am out of my depth.
found in .xsession-errors the following lines

[i]Plasma crashed, attempting to automatically recover
plasma(4874): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "
[/i]
[i]kdeinit4: preparing to launch /usr/bin/krunner
QObject: Do not delete object, 'unnamed', during its event handler!
KCrash: Application 'plasma' crashing...
kdeinit4: preparing to launch /usr/lib64/kde4/libexec/drkonqi
plasma(4893)/libplasma Plasma::Applet::Private::mainConfigGroup: requesting config for "Comic Strip" without a containment!
Object::connect: No such slot Plasma::DataEngine::checkForUpdates()
Object::connect: No such slot Plasma::DataEngine::startInit()
plasma(4892): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " [/i]

Which will hopefully be meaningful to someone.
But what I need is to get back a working system

Can anyone help?

ToddIsBored

Unregistered

2

Saturday, July 5th 2008, 10:01am

To make sure I understand you correctly.....

Are you receiving this error when trying to log into a session for your system, essentially making the login screen the furthest point you can get to?

Or is that comic plasmoid simply crashing and you want to know how to get it functioning on your desktop properly again??

3

Sunday, July 6th 2008, 9:30am

Answer and solution

Hi
Thanks for the response. I have solved the problem see below. but more on the crash first
Running under Suse 11 after failed 4.1 upgrade, system starts with KDE 4.1 startup. The startup screen reaches the point of seeing the big K when all goes black and stays that way. It will accept commands such ALT + F2 which are visible.
Solution was to fire up YAST and downgrade all KDE 4 back to 4.0.X. This works and I now have an operational system again.
Regards

4

Monday, July 7th 2008, 5:01pm

Bug resolved also

Hi

Resolved the bug by reinstalling 4.1 from Suse factory and this time no probs. Everything fine.
Still do not like absence of icons for open windows or lack of options to tailor each window but I guess these are features rather than bugs!

Similar threads