I think there is more to it than this. I found bug #204728 first by searching for the error message ("KLauncher could not be reached via D-Bus, error when calling start_service_by_desktop_path: empty").
Unfortunately, my error occurs right as KDE4 is starting up, not when starting Kate. If I click on the Ok button in the error window, the entire desktop crashes and I have to reboot (Ctrl-Alt-Backspace won't even kill X, and Ctrl-Alt-F1 won't go to the first console).
If I leave the error window on screen I can work well enough -- I haven't dived in to many other apps to see what else might be broken though.
What information do I need to gather to determine what program is calling KLauncher or D-Bus and causing the problem?
I think there is more to it than this. I found bug #204728 first by searching for the error message ("KLauncher could not be reached via D-Bus, error when calling start_service_ by_desktop_ path: empty").
Unfortunately, my error occurs right as KDE4 is starting up, not when starting Kate. If I click on the Ok button in the error window, the entire desktop crashes and I have to reboot (Ctrl-Alt-Backspace won't even kill X, and Ctrl-Alt-F1 won't go to the first console).
If I leave the error window on screen I can work well enough -- I haven't dived in to many other apps to see what else might be broken though.
What information do I need to gather to determine what program is calling KLauncher or D-Bus and causing the problem?
Dan