aptosid.com

Upgrade Warnings - [SOLVED] Kwin crashes. Dbus Problems?

seagull - 19.04.2011, 20:08
Post subject: [SOLVED] Kwin crashes. Dbus Problems?
.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
oldie - 19.04.2011, 21:27
Post subject: RE: Kwin crashes. Dbus Problems?
same here 64 bit

oldie
devil - 19.04.2011, 22:51
Post subject: RE: Kwin crashes. Dbus Problems?
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
se7en - 20.04.2011, 02:09
Post subject: RE: Kwin crashes. Dbus Problems?
the problem is dbus?
and if is it 1.4.8-2 0?
arwa - 20.04.2011, 14:44
Post subject:
@seagull: Are you running KDE4.4 from sid or 4.6 from experimental-snapshots?
DeepDayze - 20.04.2011, 15:02
Post subject:
      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 - 20.04.2011, 15:05
Post subject:
@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 - 20.04.2011, 15:39
Post subject:
      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 - 20.04.2011, 15:46
Post subject:
      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)
seagull - 20.04.2011, 16:12
Post subject:
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.
arwa - 20.04.2011, 16:18
Post subject:
You could try to start KDE with a new/fresh user account. Maybe you are using an plasmoid that has problems?
DeepDayze - 20.04.2011, 16:21
Post subject:
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
seagull - 20.04.2011, 16:42
Post subject:
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.
DeepDayze - 20.04.2011, 16:48
Post subject:
      seagull wrote:
A fresh (and! other) user changes nothing


and did you add any new plasmoids?
kilgoretrout - 20.04.2011, 17:18
Post subject:
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.
seagull - 20.04.2011, 17:23
Post subject:
      Code:
apt-cache policy libdbus-1-3
libdbus-1-3:
  Installiert: 1.4.6-1
  Kandidat:    1.4.8-2
  Versionstabelle:
     1.4.8-2 0
        500 http://debian.tu-bs.de/debian/ sid/main amd64 Packages
 *** 1.4.6-1 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


as devil mentioned: a downgrade makes the error disappear in my case.
DeepDayze - 20.04.2011, 17:30
Post subject:
      seagull wrote:
      Code:
apt-cache policy libdbus-1-3
libdbus-1-3:
  Installiert: 1.4.6-1
  Kandidat:    1.4.8-2
  Versionstabelle:
     1.4.8-2 0
        500 http://debian.tu-bs.de/debian/ sid/main amd64 Packages
 *** 1.4.6-1 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


as devil mentioned: a downgrade makes the error disappear in my case.


I have a 32 bit system so this problem seems to just be in 64 bits...maybe a bug report against dbus/libdbus is in order. If you do file one paste in your logs into the bug report
devil - 20.04.2011, 17:43
Post subject:
it happens for 64-bit also, but not everywhere. i am not hit in either arch.

greetz
devil
arwa - 20.04.2011, 19:20
Post subject:
I do not use a quote or code block, because it will be too much work. I did compare the output with the one in mine ~/.xsession-errors when starting KDE4.6.1

/etc/X11/Xsession.d/98vboxadd-xclient: Zeile 43: /usr/bin/VBoxClient: Datei oder Verzeichnis nicht gefunden

=> I do not have such entries, but instead: "Failed to connect to the VirtualBox kernel service".

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

=> This warning does occur here, too. So this is not the problem. Further messages that are the same will be marked as "=> Ok".

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).

=> I do only have one such entry regarding "/usr/share/applications/aptosid/aptosid-manual.desktop".

"KConfigIni: In file /tmp/kde-tom2/kconf_updateAD4353.tmp, line 1: " Invalid entry (missing '=')

=> I do not have any entries regarding "KConfigIni".

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

=> Ok

QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString)

=> No (do not have it here)

DeviceAutomounter::deviceMountChanged(bool, const QString)

=> No

"/usr/lib/kde4/solid_hal_power.so" does not offer a qt_plugin_instance function.

=> No

Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection

=> Ok. All these introspection warnings do occur here, too.

kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kcminit_startup.so

=> No. "libkdeinit4" does not show up here. Maybe because I have KDE4.6?

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

=> No. I do not have any entries with "hald".

looking for current "SCREEN-0"
known "*" has score: 0.125
found outputs, known: false
activate external configuration!!
registered the service: true

=> No

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.

=> No

Perhaps you find more info in /var/log/Xorg.0.log

Also you can try if starting another window manager (like icewm or something) instead of KDE does work.
arwa - 20.04.2011, 19:40
Post subject:
Some more ideas:

If you have libgl1-mesa-dri-experimental installed: This currently breaks the dist-upgrade. Make sure that all packages are set up by executing "apt-get -f install".

Also, if you are using the nouveau driver: Have you set the composite backend in KDE to xrender?
~/.kde/share/config/kwinrc
=> Backend=XRender

If all this does not help you might want to try a step forward and install KDE4.6. I recommend this anyway, because it is so much faster than 4.4. => http://qt-kde.debian.net/ and http://aptosid.com/index.php?name=PNphp ... amp;t=1068
oldie - 20.04.2011, 20:13
Post subject:
"Also you can try if starting another window manager (like icewm or something) instead of KDE does work"

sorry - did not work - my 2 systems did nothing - only kdein unstable, no mouse, no keybord only flicker - thank you

says sid (unstable) does not work?? -

Description sid is wrong for 6 weeks - this job I can - but do not do

Backup - DU - test - crash - Importing backup - DU - test - backup - that makes no fun anymore - sorry.

oldie
kilgoretrout - 20.04.2011, 20:33
Post subject:
Please reread my prior post. I have just installed from the current KDE-Lite 32 bit. I did absolutely nothing to the default configuration of KDE or anything else. First boot was fine. Did a dist-upgrade and now have the exact same symptoms as seagull, i.e. cannot login to KDE, kwin repeatedly crashes and I get the same error/bug report windows as seagull. Installed LXDE from the command line and can login to LXDE from kdm just fine. I have a GeForce 9400 GT graphics card and am running the stock nouveau driver that is installed by default.

From the above, one can conclude that this is not a 64bit only problem and it is not caused by any odd plasmoids or experimental packages as I installed none; I just did a dist-upgrade after a fresh install to bring the system up to date.
devil - 20.04.2011, 20:43
Post subject:
the cause for this is clearly dbus/libdbus: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623492

greetz
devil
hunkirdowne - 20.04.2011, 23:51
Post subject:
      kilgoretrout wrote:
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.


Same problem here on a not-so-fresh install. Running 32 bit, with the nouveau driver. Followed devil's earlier advice and downgraded libdbus-1-3 to testing and put a hold on it. Works fine now. Thanks devil!

I stole the following from somewhere on the site and edited it to suit my needs.

      Quote:
# Downgrading

# The steps are using libdbus-1-3 as an example:

# 1. enable/uncomment testing sources in /etc/apt/sources.list.d/debian.list (delete the #) so that it reads
# deb http://ftp.us.debian.org/debian/ testing main contrib non-free

# 2. # apt-get update

# 3. # apt-get install libdbus-1-3/testing

# 4. Put the newly installed package on hold with:
# # echo libdbus-1-3 hold|dpkg --set-selections

# 5. comment the testing sources in /etc/apt/sources.list.d/debian.list

# 6. # apt-get update

# When you do want to get the latest version of the package just do this:

# echo libdbus-1-3 install|dpkg --set-selections
# apt-get update
# apt-get install libdbus-1-3


If you are still having problems and have not tried the above it is easy to do and easy to back out of if it didn't fix the problem.

All the credit goes to devil and to the fine person who wrote the above in the manual.

http://manual.aptosid.com/en/sys-admin-apt-en.htm then browse down to 'Downgrading' section.


Cheers!
smoo - 21.04.2011, 02:31
Post subject: Perhaps related?
I've just started having, today, what might be a related issue: With or without my dual-monitor setup, if I log into a kwin-associated manager (like XFCE4 or KDE), the monitors soon go dark and enter "power-saving mode".

Logging in via ssh from another computer shows that the x-manager still runs, and I can correctly forward various windows to the other computer (e.g. konqueror works just fine).

I tried putting libdbus-1-3 on hold, downgrading, and all of that, with no luck.

I also reinstalled the Geras XFCE version. This works fine until I try to dist-upgrade (even with libdbus-1-3 held), whereupon a restart gives me the same dying monitors problem.
dinub1 - 21.04.2011, 13:04
Post subject: RE: Perhaps related?
Mine occurred after doing upgrade with smxi. I did not have any issues with previous kernel. However I upgraded also to a new nVidia graphics card. Its a GTX 560 Ti. Could this bug be related?
Also if I remove the nvidia driver and go back to the regular xorg driver, would this temporarily solve the problem? I cannot get in to the GUI at all. The kwin crash error persists and does not go away.
DeepDayze - 21.04.2011, 13:31
Post subject: Re: RE: Perhaps related?
      dinub1 wrote:
Mine occurred after doing upgrade with smxi. I did not have any issues with previous kernel. However I upgraded also to a new nVidia graphics card. Its a GTX 560 Ti. Could this bug be related?
Also if I remove the nvidia driver and go back to the regular xorg driver, would this temporarily solve the problem? I cannot get in to the GUI at all. The kwin crash error persists and does not go away.


Be advised if you use 3rd party scripts you are basically on your own...just a heads up, as the aptosid team does not support systems that are maintained using any such 3rd party scripts.
Ice9 - 21.04.2011, 17:42
Post subject: RE: Re: RE: Perhaps related?
THANK YOU!!!!!!!!!!!!
My dist-upgrade from yesterday left me with an unusable computer, downgrading libdbus as described above fixed it.
/me bows to the wizards on this forum
DeepDayze - 21.04.2011, 19:13
Post subject: Re: RE: Perhaps related?
      dinub1 wrote:
Mine occurred after doing upgrade with smxi. I did not have any issues with previous kernel. However I upgraded also to a new nVidia graphics card. Its a GTX 560 Ti. Could this bug be related?
Also if I remove the nvidia driver and go back to the regular xorg driver, would this temporarily solve the problem? I cannot get in to the GUI at all. The kwin crash error persists and does not go away.


What version of KDE you running?
kilgoretrout - 21.04.2011, 19:16
Post subject:
A dist-upgrade today included two libdbus packages which have corrected the problem for me. I can now login to kde.
arwa - 22.04.2011, 09:17
Post subject:
      devil wrote:
the cause for this is clearly dbus/libdbus: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623492


As described there the bug seems to be corelated to powerdevil (Hi, devil Wink ). As my old system is not capable of doing power management things and the systemsettings for power management are deactivated (I cannot turn them on), this might be the reason why I am not affected by this problem.

@kilgoretrout: Which version oflibdbus do you have installed now?
Santa - 22.04.2011, 15:18
Post subject:
Hello,

      Quote:

[14:33] <xTs> santa_: the weird thing is that I didn't update kdebase workspace
[14:35] <santa_> xTs: well. its a bug in kdebase-workspace. however, what triggered this was the upload of dbus (which is a bit stricter than the previous version)
[14:35] <xTs> ah, i see
[14:36] <xTs> i updated dbus yesterday Smile


This is suposed to be fixed in kdebase-workspace-bin 4:4.4.5-9.

You can see the status of the building here:
https://buildd.debian.org/status/packag ... -workspace
As soon as it hits the 'Installed' status for your architecture it could be copied to your local mirror. The mirrors are usually updated about 3:00, 9:00, 15:00, 21:00 (all of them zulu)[1].

Sorry for the inconvenience.

[1] I't talking about Debian, I have no clue how aptosid works.
kilgoretrout - 22.04.2011, 16:29
Post subject:
arwa I have dbus 1.4.8-2 and it appears I spoke too soon. On a fresh boot this morning I ran into the same problem. Odd thing is, I killed kdm with an init 3 from a terminal and restarted kdm with init 5. I logged into LXDE fine then logged out and tried logging in to KDE and was able to do so without issue.
DeepDayze - 22.04.2011, 16:39
Post subject:
      kilgoretrout wrote:
arwa I have dbus 1.4.8-2 and it appears I spoke too soon. On a fresh boot this morning I ran into the same problem. Odd thing is, I killed kdm with an init 3 from a terminal and restarted kdm with init 5. I logged into LXDE fine then logged out and tried logging in to KDE and was able to do so without issue.

That shows this bug is an intermittent one, one that shows up when certain conditions occur at the right time to trigger the bug. Hopefully with the fixed kdebase-workspace will fix it once it becomes available
DeepDayze - 22.04.2011, 18:25
Post subject:
      Santa wrote:
Hello,

      Quote:

[14:33] <xTs> santa_: the weird thing is that I didn't update kdebase workspace
[14:35] <santa_> xTs: well. its a bug in kdebase-workspace. however, what triggered this was the upload of dbus (which is a bit stricter than the previous version)
[14:35] <xTs> ah, i see
[14:36] <xTs> i updated dbus yesterday Smile


This is suposed to be fixed in kdebase-workspace-bin 4:4.4.5-9.

You can see the status of the building here:
https://buildd.debian.org/status/packag ... -workspace
As soon as it hits the 'Installed' status for your architecture it could be copied to your local mirror. The mirrors are usually updated about 3:00, 9:00, 15:00, 21:00 (all of them zulu)[1].

Sorry for the inconvenience.

[1] I't talking about Debian, I have no clue how aptosid works.


Santa, Aptosid is a distro that's based on debian sid and is 100% compatible with it so your post is still quite relevant
devil - 22.04.2011, 18:32
Post subject:
thxx Santa,

as we use debian unstable, we should be the first to know Smile

greetz
devil
Praxis - 23.04.2011, 08:38
Post subject:
I did a DU 04-22 at about 19:00 UTC, I can't log in to KDE, I had to use XFCE. Not a very new install, 32 bit:
sidux 2008-01 ÎÏξ - kde-full - (200804120009)
vmlinuz-2.6.38-4.slh.1-aptosid-686

Just a data point.

Edit:
DUed the 23rd, KDE is working again, whoppee.

</rant> Still 4.4.5 more than 2.5 months after Squeeze went stable. Breaking, occasionaly, but still 4.4. I've played with 4.6.2, I know KDE 4 still doesn't stack up to 3.5 for me two years after it hit the sid repos, but I'm getting slightly weary of 4.4.<rant>
maxxedout - 23.04.2011, 12:34
Post subject:
Was having the problem of Kwin and krunner seg faulting on a 32bit system. After a DU this morning all seems to be OK
vachi - 24.04.2011, 00:55
Post subject:
I just DU last evening. Everything seems fine.
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits