Kate refuses to open any documents from dolphin or terminal as a user. As a workaround I can open kate directly and then open documents from its file menu or drag dropping the file. If I attempt to open a document from terminal, like "kate lib_aux.c" it waits for about 0.5 seconds and then nothing happens. However "sudo kate lib_aux.c" does work and so does launching "sudo dolphin" and then opening documents there. I don't know what logs and configs I should attach so ask me what and I will. Reproducible: Couldn't Reproduce
I forgot to mention this has been happening to me shortly after a clean install the last 4 or so installs of kubuntu. I'm currently using the neon packages but same happened there. It works initially but then it stops working somehow.
I saw a recent comment on a forum that indicated this was because there was an existing process of kate running, so when you try to open it via double-clicking on a text file or from the command line, kate doesn't open because it is already running. Check for a running kate (ps aux | grep kate) when it refuses to open. Force closing that running instance (killall kate) should allow you to run kate by command line again. The forum report indicated that this was due to closing kate via the corner x and not via File->Quit, which supposedly avoids the issue. The bug is also reported fixed, but I just encountered it, thus the Googling! On a related note, kate should check for exactly this situation and display a popup dialog indicating that kate is currently running somewhere else...
(In reply to Greg Lepore from comment #2) > I saw a recent comment on a forum that indicated this was because there was > an existing process of kate running, so when you try to open it via > double-clicking on a text file or from the command line, kate doesn't open > because it is already running. > > Check for a running kate (ps aux | grep kate) when it refuses to open. Force > closing that running instance (killall kate) should allow you to run kate by > command line again. > > The forum report indicated that this was due to closing kate via the corner > x and not via File->Quit, which supposedly avoids the issue. The bug is also > reported fixed, but I just encountered it, thus the Googling! > > On a related note, kate should check for exactly this situation and display > a popup dialog indicating that kate is currently running somewhere else... Turns out there was about 20 instances of kate running and if I close those I can open documents from dolphin again. This is caused by some other issue where on boot about 100 instances of kate will open and I guess closing kate is broken ish. https://bugs.kde.org/show_bug.cgi?id=360066 Maybe plasma attempts to restore the hidden kate processes on reboot which stacks up after a while since they don't always close
(In reply to Greg Lepore from comment #2) > On a related note, kate should check for exactly this situation and display > a popup dialog indicating that kate is currently running somewhere else... So should this be closed and a new report opened for that suggestion?
Yes as this is no longer an issue so thanks for reminding me. Closing kate (by pressing x) exits kate properly but I'm not sure when this was fixed. I'm using the neon unstable developer edition right now.
Great, let's set to WFM as we have no idea of the fix.