[hardy] Problem launching Kate by choosing a textfile from Dolphin

Bug #205517 reported by Jonas Thorell
46
Affects Status Importance Assigned to Milestone
kdelibs
Fix Released
High
kde4libs (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

When I try to launch Kate from dolphin (KDE4) by clicking on a textfile, Kate does pop up with the file in question.

However, a few seconds later I get an error message claiming:

"Klauncher could not be reached by D-bus, error when calling start_service_by_desktop_path: empty"

I haven't run into any other problems with the program though.

Revision history for this message
mark ferguson (alchimera) wrote :

Same here. running Kubuntu(hardy):kde4:beta freshly installed and updated.

When text doc is opened through service menu (both Kate and Kword) Dolphin/Konqueror goes mainly blank for about 30 seconds, and re-appears with the error message above. The document itself is opened without delay or problem.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for reporting this problem and helping to make ubuntu better.

I can confirm this behaviour on hardy BETA. The error message pops up after kate is closed. it seems to be only a wrong error message given by dolphin. Therefore, I have set it only to wishlist as a usability issue.

I have mostly the same error messages in the terminal, however, no error message or printout appears after kate is closed. Therefore, I would think that all the out put in the terminal is unrelated.

Revision history for this message
Jonas Thorell (jthorell) wrote :

For me it doesn't happen when Kate is closed - only when I launch it. I agree it is not a showstopper though, and a temporary workaround is to set KWrite as the default application instead of Kate. I prefer Kate, but this way I at least won't be bothered by what seems to be an erroneous error message.

Changed in kdelibs:
status: Unknown → New
Revision history for this message
kgoeser (kevin-kevin-online) wrote :

This seems to be the same like bug #204728 - isn't it?

Revision history for this message
Jonas Thorell (jthorell) wrote :

Certainly looks like it's the same bug, yes.

Revision history for this message
Michael Ummels (urmel291) wrote :

In my opinion, the reason for this behaviour is a wrong file association. If you open System Settings and choose "File Associations" from the Advanced tab and look at the entry for text/plain for example (select "Kate" and click on "Edit..."), you will see that the command to open Kate is "/usr/lib/kde4/bin/kate %U". I changed %U into %u, and everything works fine.

Revision history for this message
Jonas Thorell (jthorell) wrote :

@Michael,

Now THAT is what I call an easy fix! Worked great, and I just wonder why I didn't think of that myself...thanks!

Revision history for this message
dan_linder (dan-linder) wrote :

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

Revision history for this message
kiev1 (sys-sys-admin) wrote :

KLauncher недоступен через D-Bus, ошибка вызова start_service_by_desktop_path:
empty
Heelp!!!

Revision history for this message
Oliver Jensen (ojensen) wrote :

Thanks Michael, your solution worked for me. I was surprised since fixing the settings for text/plain fixed the problem even when opening php files for example, but it works fabulously now. Thanks again! That was the last thing that was -really- annoying left for me... except for the stupid clock not resizing to smaller panel sizes, but *sigh* there'll be a fix for that eventually, too =)

Changed in kdelibs:
status: New → Fix Released
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Fixed in trunk, should be in Intrepid soon.

Changed in kde4libs:
assignee: txwikinger → nobody
status: Confirmed → Fix Committed
Changed in kdelibs:
status: Fix Released → Confirmed
Changed in kde4libs:
status: Fix Committed → Confirmed
Revision history for this message
Götz Christ (g-christ) wrote :

That is great!
Does this mean that this fix will be in KDE 4.1 or 4.2? If it is in 4.2 will be it back ported to Intrepid?

Revision history for this message
alepac (alessandro-pacifici) wrote :

This didn't solve the problem. I think it should be related to the fact that closing kate with the X on the top-right corner dosn't close the application (ps aux | grep kate) shows the first call to kate. Calling kate, with the --use option, try to reuse the same session without success. If you call kate without the --use option you will have one session of the application per file. The only way to close correctly kate is with the File->Exit command.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Fixed in Intrepid.

Changed in kde4libs:
status: Confirmed → Fix Released
Changed in kdelibs:
status: Confirmed → Fix Released
Changed in kdelibs:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.