Sometimes the following all stop working at once: 1) Opening a file with Kate from Dolphin stops working: it tells me "KDEInit could not launch '/usr/bin/kate'". (Same thing if I try an indirect method of opening kate, e.g. "xdg-open mytextfile" or "kde-open mytextfile".) 2) Trying to open Kate from the application menu (or a copied .desktop file) instantly fails (doesn't do anything). 3) Trying to open Konsole from the application menu (or a copied .desktop file) thinks for several seconds but ultimately does nothing. I can still launch konsole and kate from a command prompt, and other things seem to work okay. Simply terminating my klauncher process gets everything working again. No idea how to reproduce, but it is a recurring problem. Possibly DBUS related, since kate and konsole both try to open in existing processes. There was an existing konsole process, but no existing kate process. Reproducible: Sometimes
Does this still happen in recent releases? It sounds like a setup problem, I have never seen it reported elsewhere.
No reply, assuming it is working now.
This still happens on KDE 4.13.3 (Kubuntu 14.04). Nothing particularly out of the ordinary about my install/setup/configuration. I won't terminate klauncher for now, so I'm happy to try any suggestions between now and my next reboot if you want to help me catch this thing.
A little more info: Most programs launch just fine from the menus, and everything will start from the command line (provided it's NOT through a .desktop file - see point 1 in comment 1). The following programs don't work: class 1) Akregator Kate KsCD Rekonq System Settings class 2) Amarok Dragon Player Help K3b Konsole Nepomuk Cleaner Muon Muon Discover Muon Updater class 3) Speedcrunch For class 1, they fail instantly. If there is even a process created, I can't tell. For class 2, they fail, and I never see the process come up in Ksysguard, but the name and a spinner lingers on the task bar for several long moments. (For classes 1 and 2, if it's the first time starting the program, I might see them come up in Ksysguard briefly before dying. So it could be that the processes always start briefly but start and die too quickly to tell once they're cached in memory. There may be another explanation, though.) For class 3, it comes up instantly - the process is actually started but it dies instantly. Just like class 1 and 2, it works just fine starting it from the command line, so in this case something is actually killing the already launched process. (as in the special first-time cases for class 2 and maybe 1) In addition, case 3 is a perfect and repeatable test case for Bug 261255. If you have Ksysguard open at the time, you can build up lots of non-existing speedcrunch processes (they did exist, but only momentarily but still stuck on the list; pgrep or similar shows they really aren't there.) Is there anything useful that could be gained from some debugging tool like gdb? I'll try whatever - just not sure how/what to try that might help track it down.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
I haven't seen this bug in quite some time.