Bug 411537

Summary: problems using kde4-kate as text editor in dolphin
Product: [openSUSE] openSUSE 11.0 Reporter: Bernhard Koenig <b.a.koenig>
Component: KDE4 ApplicationsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: andreas.pfaller, badshah400, linuxdreas, rwampler, wstephenson
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Bernhard Koenig 2008-07-23 11:09:11 UTC
Say I set kde4-kate (version 3.0.4) as default application for txt-files in Dolphin. Then I click on a txt-file and kate opens up as normal. But now dolphin freezes in the background (even though kate is active). If I quit kate with the frozen dolphin in the background it says:

"KDEInit could not launch '/usr/bin/kate'."

openSUSE is 11.0 and Dolphin 1.0.2 and KDE 4.0.4.
I do not have the same problem with Kwrite or Emacs as default txt-editor.
Comment 1 Bernhard Koenig 2008-07-23 11:13:05 UTC
Btw, kate doesn't have to be default editor. When in dolphin, just open any text file with kate and dolphin will freeze.
Comment 2 Lubos Lunak 2008-07-25 11:55:32 UTC
Please provide exact steps how to reproduce this problem with a new user account.
Comment 3 Bernhard Koenig 2008-07-25 12:27:13 UTC
If I remember correctly, all I did was install kde4-kate. Then open dolphin and right-click on any text file: choose "Open with ... Kate". Then dolphin freezes in my system.

Don't know if everybody has this problem but I do. Couldn't there be a confusion with the programs "kate" and "kde4-kate" (I don't have KDE3 kate installed).
Comment 4 Bernhard Koenig 2008-07-25 12:29:06 UTC
Needed information (hopefully) provided.
Comment 5 Lubos Lunak 2008-07-30 14:49:11 UTC
*** Bug 403944 has been marked as a duplicate of this bug. ***
Comment 6 Lubos Lunak 2008-07-30 14:55:56 UTC
Cannot reproduce. This problem gets occassionally reported, but AFAIK nobody has yet found a way to reliably reproduce it.
Comment 7 Bernhard Koenig 2008-07-30 15:01:07 UTC
I can guarantee that it happens to me every single time.

I have a pretty recent install from the live CD. All you would need to do to reproduce the bug imho is:

1) install from most recent live CD, openSUSE 11.0, KDE 4
2) sudo zypper dup
3) zypper in kde4-kate

and

4) open dolphin to find it crashes every single time I open a text file with Kate.
Comment 8 Bernhard Koenig 2008-07-30 15:11:24 UTC
Btw, I can confirm 403944 on my machine as well.

Just a wild guess, but I noticed that 403944 is also using a 64bit processor.
Comment 9 Lubos Lunak 2008-07-30 15:15:44 UTC
*** Bug 191388 has been marked as a duplicate of this bug. ***
Comment 10 Andreas Pfaller 2008-07-30 16:57:09 UTC
I have had this problem in the past (4.1RC versions of KDE) and
changing the command to launch kate from "kate %U" to "kate %u"
(in file properties) solved it for me. However I just changed
it back to "%U" in 4.1 final (from the factory tree) and it
seems to work now (only lightly tested).
Comment 11 Bernhard Koenig 2008-07-30 21:23:02 UTC
Yes!

I changed (in file properties) "kate %U" to "kate %u" and the problem disappeared. Maybe somebody understands the problem now?

I got even bolder now and switched "kate %u" to "kate --use %u" (the --use option should be standard btw) and the problem is back! Dolphin says

KDEInit could not launch '/usr/bin/kate'.

after opening the second file to a session (not when opening the first file).
Comment 12 Bernhard Koenig 2008-07-30 21:28:43 UTC
Really funny because I cannot reproduce it myself anymore even after switching back to "kate %U", so the bug is very fickle. If you want to see another instance of it, try changing the file properties to

kate --use %u

and open two text files with kate into one session (with dolphin).
Comment 13 Bernhard Koenig 2008-08-01 16:59:56 UTC
*** Bug 361609 has been marked as a duplicate of this bug. ***
Comment 14 Will Stephenson 2008-09-21 11:58:17 UTC

*** This bug has been marked as a duplicate of bug 420150 ***