KCrash: Application 'kwin' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2562): Unable to find an internal debugger that can work with the KCrash backend
drkonqi(2565): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
plasma-desktop(2561): Communication problem with "plasma-desktop" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.plasma-desktop was not provided by any .service files" "

dolphin(2645) KXMLGUI::ActionList::plug: Index 19 is not within range (0 - 11
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
knotify(2882) KNotify::event: 1 ref= 0
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
drkonqi(2701): Unable to find an internal debugger that can work with the KCrash backend
QMetaObject::invokeMethod: No such method KMixApp::loadCommandLineOptionsForNewInstance()
kdeinit4: preparing to launch /usr/lib/kde4/kio_trash.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
QMetaObject::invokeMethod: No such method DolphinApplication::loadCommandLineOptionsForNewInstance()
dolphin(2645)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2907): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2928): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
Application asked to unregister timer 0x60000005 which is not registered in this thread. Fix application.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2949): Unable to find an internal debugger that can work with the KCrash backend
Application asked to unregister timer 0x4a000004 which is not registered in this thread. Fix application.
Application asked to unregister timer 0x1f000004 which is not registered in this thread. Fix application.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
Application asked to unregister timer 0x6b000004 which is not registered in this thread. Fix application.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2973): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2996): Unable to find an internal debugger that can work with the KCrash backend
Application asked to unregister timer 0x3d000005 which is not registered in this thread. Fix application.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
Application asked to unregister timer 0x4a000003 which is not registered in this thread. Fix application.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3021): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
Application asked to unregister timer 0x64000005 which is not registered in this thread. Fix application.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3044): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3066): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3092): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3115): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3197): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3259): Unable to find an internal debugger that can work with the KCrash backend
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
process 2443: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
knotify(2882) NotifyByPopup::notify: 2 active notifications: () ()
knotify(2882) NotifyBySound::notify: going to play "/usr/share/sounds/KDE-Sys-App-Message.ogg"
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(3288): Unable to find an internal debugger that can work with the KCrash backend
drkonqi: Fatal IO error: client killed
drkonqi: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kwin: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
klauncher: Exiting on signal 1
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
QProcess: Destroyed while process is still running.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
NepomukServer(2608)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kded4: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

@seagull: Are you running KDE4.4 from sid or 4.6 from experimental-snapshots?

DeepDayze

Post subject:Posted: 20.04.2011, 15:02

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

arwa wrote:

@seagull: Are you running KDE4.4 from sid or 4.6 from experimental-snapshots?

I haven't had any issue with dbus with either KDE 4.4 or the 4.6 from e-s. Is this a possible dbus configuration issue? I have dbus 1.4.8-2 as well.

Also what was the application you were trying to run via krunner?

arwa

Post subject:Posted: 20.04.2011, 15:05

Joined: 2010-09-11
Posts: 183

Status: Offline

@DeepDayze: Is your system up to date and running libdbus-1-3 (1.4.8-2)? If yes, I will try an upgrade to report here what happens.

DeepDayze

Post subject:Posted: 20.04.2011, 15:39

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

arwa wrote:

@DeepDayze: Is your system up to date and running libdbus-1-3 (1.4.8-2)? If yes, I will try an upgrade to report here what happens.

yes it is fully updated. I have one system running standard KDE 4.4.5 plus one that's running KDE 4.6.1 from E-S. Does this dbus issue affect ALL apps or just certain ones?

arwa

Post subject:Posted: 20.04.2011, 15:46

Joined: 2010-09-11
Posts: 183

Status: Offline

DeepDayze wrote:

Does this dbus issue affect ALL apps or just certain ones?

This indeed would be interesting. I now have dist-upgraded my system (using KDE4.6.1) and all looks fine. I did start konqueror via krunner. The alt+F1 menu seems to work. So I think I do not have any problem with the installation. (32bit)

I do not remember to install anything from experimental. The crash happens during/short after kde-login. The desktop doesn't appear, instead a blue background. Konsole starts without title-bar etc. and very many kde-bug-report windows.

arwa

Post subject:Posted: 20.04.2011, 16:18

Joined: 2010-09-11
Posts: 183

Status: Offline

You could try to start KDE with a new/fresh user account. Maybe you are using an plasmoid that has problems?

DeepDayze

Post subject:Posted: 20.04.2011, 16:21

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

Go to init 3 and move .kde to .kde-bak (do not delete .kde just rename it temporarily) then return to init 5 and try to login again. Moving .kde out of the way will reset your desktop to default. This can help identify whether your kde desktop profile's messed up or not.

arwa wrote:

You could try to start KDE with a new/fresh user account. Maybe you are using an plasmoid that has problems?

that's a possibility as well...there are some plasmoids that are broken

Perhaps someone can look at the log posted by the OP and help find the culprit

Same problem here on a fresh install of 2011-kde-min. Changed nothing from the default kde setup; first boot was fine; did a dist-upgrade; on reboot have the identical problem as seagul. Running 32 bit, with the nouveau driver.