Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
seagullOffline
Post subject: [SOLVED] Kwin crashes. Dbus Problems?  PostPosted: 19.04.2011, 20:08



Joined: 2010-09-11
Posts: 38

Status: Offline
.xsession-errors:
      Code:
Xsession: X session started for tom at Di 19. Apr 20:13:51 CEST 2011
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 43: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 44: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 46: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 48: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_klauncher.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kconf_update.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
kded(2443)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kcminit_startup.so
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_ksmserver.so
<unknown program name>(2440)/ KStartupInfo::createNewStartupId: creating:  "aptosidbox;1303236837;109154;2440_TIME0" : "unnamed app"
kephald starting up
XRANDR error base:  180
RRInput mask is set!!
RandRScreen::loadSettings - adding mode:  438 1280 x 1024
RandRScreen::loadSettings - adding mode:  439 1280 x 1024
RandRScreen::loadSettings - adding mode:  440 1280 x 1024
RandRScreen::loadSettings - adding mode:  441 1280 x 960
RandRScreen::loadSettings - adding mode:  442 1280 x 960
RandRScreen::loadSettings - adding mode:  443 1152 x 921
RandRScreen::loadSettings - adding mode:  444 1152 x 921
RandRScreen::loadSettings - adding mode:  445 1152 x 864
RandRScreen::loadSettings - adding mode:  446 1152 x 864
RandRScreen::loadSettings - adding mode:  447 1152 x 864
RandRScreen::loadSettings - adding mode:  448 1152 x 864
RandRScreen::loadSettings - adding mode:  449 1152 x 864
RandRScreen::loadSettings - adding mode:  450 1024 x 768
RandRScreen::loadSettings - adding mode:  451 1024 x 768
RandRScreen::loadSettings - adding mode:  452 1024 x 768
RandRScreen::loadSettings - adding mode:  453 1024 x 768
RandRScreen::loadSettings - adding mode:  454 960 x 600
RandRScreen::loadSettings - adding mode:  455 960 x 540
RandRScreen::loadSettings - adding mode:  456 840 x 525
RandRScreen::loadSettings - adding mode:  457 840 x 525
RandRScreen::loadSettings - adding mode:  458 840 x 525
RandRScreen::loadSettings - adding mode:  459 832 x 624
RandRScreen::loadSettings - adding mode:  460 800 x 600
RandRScreen::loadSettings - adding mode:  461 800 x 600
RandRScreen::loadSettings - adding mode:  462 800 x 600
RandRScreen::loadSettings - adding mode:  463 800 x 600
RandRScreen::loadSettings - adding mode:  464 800 x 600
RandRScreen::loadSettings - adding mode:  465 800 x 600
RandRScreen::loadSettings - adding mode:  466 800 x 512
RandRScreen::loadSettings - adding mode:  467 720 x 450
RandRScreen::loadSettings - adding mode:  468 680 x 384
RandRScreen::loadSettings - adding mode:  469 680 x 384
RandRScreen::loadSettings - adding mode:  470 640 x 512
RandRScreen::loadSettings - adding mode:  471 640 x 512
RandRScreen::loadSettings - adding mode:  472 640 x 480
RandRScreen::loadSettings - adding mode:  473 640 x 480
RandRScreen::loadSettings - adding mode:  474 640 x 480
RandRScreen::loadSettings - adding mode:  475 640 x 480
RandRScreen::loadSettings - adding mode:  476 640 x 480
RandRScreen::loadSettings - adding mode:  477 640 x 480
RandRScreen::loadSettings - adding mode:  478 576 x 432
RandRScreen::loadSettings - adding mode:  479 576 x 432
RandRScreen::loadSettings - adding mode:  480 576 x 432
RandRScreen::loadSettings - adding mode:  481 576 x 432
RandRScreen::loadSettings - adding mode:  482 512 x 384
RandRScreen::loadSettings - adding mode:  483 512 x 384
RandRScreen::loadSettings - adding mode:  484 512 x 384
RandRScreen::loadSettings - adding mode:  485 416 x 312
RandRScreen::loadSettings - adding mode:  486 400 x 300
RandRScreen::loadSettings - adding mode:  487 400 x 300
RandRScreen::loadSettings - adding mode:  488 400 x 300
RandRScreen::loadSettings - adding mode:  489 400 x 300
RandRScreen::loadSettings - adding mode:  490 320 x 240
RandRScreen::loadSettings - adding mode:  491 320 x 240
RandRScreen::loadSettings - adding mode:  492 320 x 240
RandRScreen::loadSettings - adding crtc:  436
RandRScreen::loadSettings - adding output:  437
Setting CRTC 436 on output "default" (previous 0 )
CRTC outputs: (437)
Output name: "default"
Output refresh rate: 50
Output rect: QRect(0,0 1280x1024)
Output rotation: 1
XRandROutputs::init
  added output  437
adding an output 0 with geom:  QRect(0,0 1280x1024)
output: "SCREEN-0" QRect(0,0 1280x1024) 1952543855 true true
load xml
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1280x1024)
looking for a matching configuration...
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
found outputs, known: false
activate external configuration!!
registered the service: true
screens registered on the bus: true
outputs registered on the bus: true
configurations registered on the bus: true
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::crashHandler() called with signal 11; recent crashes: 1
KCrash: Application 'kwin' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2508): 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::crashHandler() called with signal 11; recent crashes: 2
KCrash: Application 'kwin' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2522): 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::crashHandler() called with signal 11; recent crashes: 3
kdeinit4: preparing to launch /usr/bin/plasma-desktop
KCrash: Application 'kwin' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2544): 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::crashHandler() called with signal 11; recent crashes: 4
KCrash: Application 'plasma-desktop' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
plasma-desktop(2541): 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" "

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" "

kcminit(2501)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_emoticons.so"
kcminit(2501)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_hotkeys.so"
kdeinit4: preparing to launch /usr/bin/kaccess
<unknown program name>(2596)/ kdemain: Xlib XKB extension major= 1  minor= 0
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kxkb.so
kaccess(2596) kdemain: X server XKB extension major= 1  minor= 0
QMetaObject::invokeMethod: No such method KAccessApp::loadCommandLineOptionsForNewInstance()
QMetaObject::invokeMethod: No such method KXKBApp::loadCommandLineOptionsForNewInstance()
kcminit(2501)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkcm_keys.so"
kdeinit4: preparing to launch /usr/bin/kmixctrl
kdeinit4: preparing to launch /usr/bin/krunner
kdeinit4: preparing to launch /usr/bin/nepomukserver
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kdeinit4: preparing to launch /usr/bin/kglobalaccel
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "kmix"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "kwin"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "plasma"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "krunner"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "kxkb"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "plasma-desktop"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "khotkeys"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "amarok"
kglobalaccel(2614) GlobalShortcut::setKeys: "decreaseVolume" skipping because key "" is already taken
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "kded"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "juk"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "yakuake"
kglobalaccel(2614) GlobalShortcutsRegistry::loadSettings: Loading group  "klipper"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+K" for "kxkb" : "Switch to Next Keyboard Layout"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Alt+F2" for "krunner" : "Run Command"
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Alt+Shift+F2" for "krunner" : "Run Command on clipboard contents"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Esc" for "krunner" : "Show System Activity"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+Ins" for "krunner" : "Switch User"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+L" for "krunner" : "Lock Session"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+Del" for "krunner" : "Log Out"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+Shift+Del" for "krunner" : "Log Out Without Confirmation"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+Shift+PgDown" for "krunner" : "Halt Without Confirmation"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Ctrl+Alt+Shift+PgUp" for "krunner" : "Reboot Without Confirmation"
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.
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.28'
kdeinit4: preparing to launch /usr/bin/kmix
KCrash: Application 'krunner' crashing...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
drkonqi(2621): Unable to find an internal debugger that can work with the KCrash backend
kdeinit4: preparing to launch /usr/bin/konsole
QMetaObject::invokeMethod: No such method KMixApp::loadCommandLineOptionsForNewInstance()
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Volume Up" for "kmix" : "increase_volume"
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Volume Down" for "kmix" : "decrease_volume"
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.
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Volume Mute" for "kmix" : "mute"
kdeinit4: preparing to launch /usr/bin/dolphin
konsole(2639)/kdeui (kdelibs): Attempt to use QAction "change-profile" with KXMLGUIFactory!
kmix(2624): _refcount already 0
kdeinit4: preparing to launch
Could not find 'hp-systray' executable.
kdeinit4: preparing to launch /usr/bin/kmix
<unknown program name>(2606)/: Communication problem with  "krunner" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
kded(2443)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_networkmanager07.so" does not offer a qt_plugin_instance function.
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Display" for "kded" : "display"
QDBusObjectPath: invalid path ""
kdeinit4: preparing to launch /usr/bin/knotify4
kglobalaccel(2614) GlobalShortcutsRegistry::registerKey: Registering key "Print" for "khotkeys" : "{1b17b8da-35f8-42d1-b96f-a638b72298ba}"
kglobalaccel(2614) KdeDGlobalAccel::Component::cleanUp: 1
QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance()
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.
<unknown program name>(2618)/: Communication problem with  "krunner" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

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.


64bit, newest kernel, prop nvidia driver
 
 View user's profile Send private message  
Reply with quote Back to top
oldieOffline
Post subject: RE: Kwin crashes. Dbus Problems?  PostPosted: 19.04.2011, 21:27



Joined: 2010-09-12
Posts: 25

Status: Offline
same here 64 bit

oldie
 
 View user's profile Send private message  
Reply with quote Back to top
devilOffline
Post subject: RE: Kwin crashes. Dbus Problems?  PostPosted: 19.04.2011, 22:51



Joined: 2010-08-26
Posts: 491
Location: Berlin
Status: Offline
libdbus-1-3 from testing fixes it for now.
feel free to issue a bugreport, i cant, i am not hit by the bug.

greetz
devil
 
 View user's profile Send private message  
Reply with quote Back to top
se7enOffline
Post subject: RE: Kwin crashes. Dbus Problems?  PostPosted: 20.04.2011, 02:09



Joined: 2010-09-11
Posts: 164

Status: Offline
the problem is dbus?
and if is it 1.4.8-2 0?

_________________
Don't mention the war!
Meine Meinung steht fest! Bitte verwirren Sie mich nicht mit Tatsachen!
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 20.04.2011, 14:44



Joined: 2010-09-11
Posts: 183

Status: Offline
@seagull: Are you running KDE4.4 from sid or 4.6 from experimental-snapshots?
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 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?
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 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.
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 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?
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 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)
 
 View user's profile Send private message  
Reply with quote Back to top
seagullOffline
Post subject:   PostPosted: 20.04.2011, 16:12



Joined: 2010-09-11
Posts: 38

Status: Offline
kde-things-installed:
      Code:
kdepim-runtime                           4:4.4.7-1                            http://debian.tu-bs.de/debian/       sid/main         
libakonadi-kde4                          4:4.4.5-2                            http://debian.tu-bs.de/debian/       sid/main         
libkdewebkit5                            4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdemultimedia-kio-plugins                4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdebase-bin                              4:4.4.5-3                            http://debian.tu-bs.de/debian/       sid/main         
python-kde4                              4:4.4.5-5                            http://debian.tu-bs.de/debian/       sid/main         
libkdecorations4                         4:4.4.5-8                            http://debian.tu-bs.de/debian/       sid/main         
system-config-printer-kde                4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kde-l10n-de                              4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdepasswd                                4:4.4.5-3                            http://debian.tu-bs.de/debian/       sid/main         
kdepimlibs-kio-plugins                   4:4.4.5-2                            http://debian.tu-bs.de/debian/       sid/main         
libkde3support4                          4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kde-style-qtcurve                        1.8.5-1                              http://debian.tu-bs.de/debian/       sid/main         
kdebase-data                             4:4.4.5-3                            http://debian.tu-bs.de/debian/       sid/main         
kdelibs-bin                              4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdelibs5-data                            4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdebase-workspace-data                   4:4.4.5-8                            http://debian.tu-bs.de/debian/       sid/main         
libkdesu5                                4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdebase-runtime-data                     4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdelibs5-plugins                         4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kde-config-cron                          4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdeadmin                                 4:4.4.5-4                            http://debian.tu-bs.de/debian/       sid/main         
kdebase-workspace-kgreet-plugins         4:4.4.5-8                            http://debian.tu-bs.de/debian/       sid/main         
oxygencursors                            0.0.2010-05-10-kde4.4.3-1            http://debian.tu-bs.de/debian/       sid/main         
kdebase-workspace                        4:4.4.5-8                            http://debian.tu-bs.de/debian/       sid/main         
kdebase-apps                             4:4.4.5-3                            http://debian.tu-bs.de/debian/       sid/main         
libkdegames5                             4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdegames-card-data                       4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdegames-mahjongg-data                   4:4.4.5-1                            http://debian.tu-bs.de/debian/       sid/main         
kdegraphics-libs-data                    4:4.4.5-2                            http://debian.tu-bs.de/debian/       sid/main         
libkdepim4                               4:4.4.7-3                            http://debian.tu-bs.de/debian/       sid/main         
kdepim-kresources                        4:4.4.7-3                            http://debian.tu-bs.de/debian/       sid/main         
kdepim-groupware                         4:4.4.7-3                            http://debian.tu-bs.de/debian/       sid/main         
kdepim-wizards                           4:4.4.7-3                            http://debian.tu-bs.de/debian/       sid/main         
kdelirc                                  4:4.4.5-1+b1                         http://debian.tu-bs.de/debian/       sid/main         
kde-plasma-desktop                       5:66                                 http://debian.tu-bs.de/debian/       sid/main         

      Code:

libdbus-1-3                              1.4.8-2                              http://debian.tu-bs.de/debian/       sid/main         
libdbus-glib-1-2                         0.92-1                               http://debian.tu-bs.de/debian/       sid/main         
dbus                                     1.4.8-2                              http://debian.tu-bs.de/debian/       sid/main         
libqt4-dbus                              4:4.7.2-3                            http://debian.tu-bs.de/debian/       sid/main         
python-dbus                              0.83.1-1+b1                          http://debian.tu-bs.de/debian/       sid/main         
dbus-x11                                 1.4.8-2                              http://debian.tu-bs.de/debian/       sid/main         
python-qt4-dbus                          4.8.3-2+b1                           http://debian.tu-bs.de/debian/       sid/main         

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.
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 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?
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 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
 
 View user's profile Send private message  
Reply with quote Back to top
seagullOffline
Post subject:   PostPosted: 20.04.2011, 16:42



Joined: 2010-09-11
Posts: 38

Status: Offline
A fresh (and! other) user changes nothing

      Code:
Xsession: X session started for tom2 at Mi 20. Apr 18:35:14 CEST 2011
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 43: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 44: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 46: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 48: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden
---- Kaboom Settings Dump ----
kdehome - "/home/tom2/.kde" - exists?: NO
kde4home - "/home/tom2/.kde4" - exists?: NO
kde3backup - "/home/tom2/kde3-backup" - exists?: NO
kaboom stamp - "/home/tom2/.local/kaboom" - exists?:  NO
kaboom log - "/home/tom2/.kaboom.log"
---- -------------------- ----
Stamp's parent directory does not exist. Creating...
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_klauncher.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kbuildsycoca4(4349) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/pppoeconf.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(4349) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/nxclient.desktop" is not compliant with XDG standard (missing trailing semicolon).
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kconf_update.so
"KConfigIni: In file /tmp/kde-tom2/kconf_updateAD4353.tmp, line 1: " Invalid entry (missing '=')
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)
kded(4348)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kded(4348)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_hal_power.so" does not offer a qt_plugin_instance function.
Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
kded(4348)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kcminit_startup.so
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_ksmserver.so
<unknown>(4345)/ KStartupInfo::createNewStartupId: creating:  "aptosidbox;1303317318;642521;4345_TIME0" : "unnamed app"
kephald starting up
XRANDR error base:  180
RRInput mask is set!!
RandRScreen::loadSettings - adding mode:  438 1280 x 1024
RandRScreen::loadSettings - adding mode:  439 1280 x 1024
RandRScreen::loadSettings - adding mode:  440 1280 x 1024
RandRScreen::loadSettings - adding mode:  441 1280 x 960
RandRScreen::loadSettings - adding mode:  442 1280 x 960
RandRScreen::loadSettings - adding mode:  443 1152 x 921
RandRScreen::loadSettings - adding mode:  444 1152 x 921
RandRScreen::loadSettings - adding mode:  445 1152 x 864
RandRScreen::loadSettings - adding mode:  446 1152 x 864
RandRScreen::loadSettings - adding mode:  447 1152 x 864
RandRScreen::loadSettings - adding mode:  448 1152 x 864
RandRScreen::loadSettings - adding mode:  449 1152 x 864
RandRScreen::loadSettings - adding mode:  450 1024 x 768
RandRScreen::loadSettings - adding mode:  451 1024 x 768
RandRScreen::loadSettings - adding mode:  452 1024 x 768
RandRScreen::loadSettings - adding mode:  453 1024 x 768
RandRScreen::loadSettings - adding mode:  454 960 x 600
RandRScreen::loadSettings - adding mode:  455 960 x 540
RandRScreen::loadSettings - adding mode:  456 840 x 525
RandRScreen::loadSettings - adding mode:  457 840 x 525
RandRScreen::loadSettings - adding mode:  458 840 x 525
RandRScreen::loadSettings - adding mode:  459 832 x 624
RandRScreen::loadSettings - adding mode:  460 800 x 600
RandRScreen::loadSettings - adding mode:  461 800 x 600
RandRScreen::loadSettings - adding mode:  462 800 x 600
RandRScreen::loadSettings - adding mode:  463 800 x 600
RandRScreen::loadSettings - adding mode:  464 800 x 600
RandRScreen::loadSettings - adding mode:  465 800 x 600
RandRScreen::loadSettings - adding mode:  466 800 x 512
RandRScreen::loadSettings - adding mode:  467 720 x 450
RandRScreen::loadSettings - adding mode:  468 680 x 384
RandRScreen::loadSettings - adding mode:  469 680 x 384
RandRScreen::loadSettings - adding mode:  470 640 x 512
RandRScreen::loadSettings - adding mode:  471 640 x 512
RandRScreen::loadSettings - adding mode:  472 640 x 480
RandRScreen::loadSettings - adding mode:  473 640 x 480
RandRScreen::loadSettings - adding mode:  474 640 x 480
RandRScreen::loadSettings - adding mode:  475 640 x 480
RandRScreen::loadSettings - adding mode:  476 640 x 480
RandRScreen::loadSettings - adding mode:  477 640 x 480
RandRScreen::loadSettings - adding mode:  478 576 x 432
RandRScreen::loadSettings - adding mode:  479 576 x 432
RandRScreen::loadSettings - adding mode:  480 576 x 432
RandRScreen::loadSettings - adding mode:  481 576 x 432
RandRScreen::loadSettings - adding mode:  482 512 x 384
RandRScreen::loadSettings - adding mode:  483 512 x 384
RandRScreen::loadSettings - adding mode:  484 512 x 384
RandRScreen::loadSettings - adding mode:  485 416 x 312
RandRScreen::loadSettings - adding mode:  486 400 x 300
RandRScreen::loadSettings - adding mode:  487 400 x 300
RandRScreen::loadSettings - adding mode:  488 400 x 300
RandRScreen::loadSettings - adding mode:  489 400 x 300
RandRScreen::loadSettings - adding mode:  490 320 x 240
RandRScreen::loadSettings - adding mode:  491 320 x 240
RandRScreen::loadSettings - adding mode:  492 320 x 240
RandRScreen::loadSettings - adding crtc:  436
RandRScreen::loadSettings - adding output:  437
Setting CRTC 436 on output "default" (previous 0 )
CRTC outputs: (437)
Output name: "default"
Output refresh rate: 50
Output rect: QRect(0,0 1280x1024)
Output rotation: 1
XRandROutputs::init
  added output  437
adding an output 0 with geom:  QRect(0,0 1280x1024)
output: "SCREEN-0" QRect(0,0 1280x1024) 1952543855 true true
load xml
save xml
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1280x1024)
looking for a matching configuration...
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
found outputs, known: false
activate external configuration!!
registered the service: true
screens registered on the bus: true
outputs registered on the bus: true
configurations registered on the bus: true
process 4348: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.


I did not more like an ordinary d-u.


Last edited by seagull on 20.04.2011, 16:55; edited 3 times in total
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 20.04.2011, 16:48



Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
      seagull wrote:
A fresh (and! other) user changes nothing


and did you add any new plasmoids?
 
 View user's profile Send private message  
Reply with quote Back to top
kilgoretroutOffline
Post subject:   PostPosted: 20.04.2011, 17:18



Joined: 2011-04-20
Posts: 4

Status: Offline
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.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio