SUMMARY After quit the process "dolphin" is keep running in background. When the option "restore last session" is set dolphin appears after login automatically. STEPS TO REPRODUCE 1. Login to KDE 2. Make sure that "restore last session" is set 3. Launch Dolphin 4. Close Doplhin 5. Logout 6. Login to KDE OBSERVED RESULT The process "dolphin" is always running in background after quit. EXPECTED RESULT Quit Dolphin must end the process. SOFTWARE/OS VERSIONS Operating System: Fedora 31 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Kernel Version: 5.4.15-200.fc31.x86_64 OS Type: 64-bit ADDITIONAL INFORMATION My workaround is to kill the process "dolphin" before I logout. That prevents Dolphin to appear automatically after login.
Yes, the background daemon is to support the "open new folders in tabs rather than new windows" feature. If you don't want a daemonized Dolphin running, you can turn off this feature. That said, it's a bug if the daemonized Dolphin triggers session restore. It shouldn't do that. Will investigate.
In my case "open new folders in tabs" is not set. However it seems that Dolphin is running daemonized.
Just tested on neon-user-20200207-1737.iso. I can't see any "dolphin-process" after quitting Dolphin. This means to me, Dolphin never runs deamonized in both cases when "open new folders in tabs" is set or not.
FWIW I cannot reproduce the issue.
(In reply to Nate Graham from comment #4) > FWIW I cannot reproduce the issue. Hi, what do you mean by you cannot reproduce the issue? How did you test it? Did you try NEON? Like I said everything is OK on NEON. No bug. Or did you try Fedora 31? If not, would you mind to install somewhere Fedora 31 (KDE spin) to test it? I can always reproduce this bug on all of my installations. It doesn't matter if it's a laptop or desktop PC.
(In reply to Nate Graham from comment #1) > Yes, the background daemon is to support the "open new folders in tabs > rather than new windows" feature. If you don't want a daemonized Dolphin > running, you can turn off this feature. Not exactly, the deamon is to support the freedesktop's File Manager DBus Interface and cannot be turned off. There is nothing to fix here, really.
(In reply to Elvis Angelaccio from comment #6) > (In reply to Nate Graham from comment #1) > > Yes, the background daemon is to support the "open new folders in tabs > > rather than new windows" feature. If you don't want a daemonized Dolphin > > running, you can turn off this feature. > > Not exactly, the deamon is to support the freedesktop's File Manager DBus > Interface and cannot be turned off. > > There is nothing to fix here, really. Hi, you are right when you say there is nothing to fix because you have answered to comment 1 but the summary of my bug report was something like: "doplhin is running in background after quitting". This has been changed by someone here to "Daemonized Dolphin inappropriately triggers session restoration". Please read my description. So the bug is definitely still there and it is always reproducible. I am a user and don't know much about KDE's mechanism, but Nate gave me the idea about "triggering session restoration". When I quit Doplhin the process is still running in the background and therfore it can not "untrigger" session restoration. That is my thought. Please allow my to say that I am a bit upset, because the bug is always reproducible and someone set the status to "resolved intentional". I don't report bugs just for kicks. Please REOPEN this report and CHANGE the status and the summary.
I would say, "yes, this is definitely not intentional behavior from a user perspective; re-opening" but I cannot reproduce the issue on my machine (openSUSE Tumbleweed). I use session restore and Dolphin doesn't come up on boot.
It sounds like this bug is on Fedora and perhaps on some other distros, but not on openSuse. That's why I have specified "Fedora RPMs" as platform.
Hi, I have just tested on Fedora 32, Dolphin 19.12.2 and I can still reproduce this bug always on several computers. Please reopen this bug report. Do you need some additional information? Is there anything I can do as a user to fix this bug?
From what I can gather this appears to be a legitimate issue, but people have trouble reproducing it. I'm setting the status to REPORTED and hope that eventually someone will be able to reproduce reliably.
Created attachment 130039 [details] Before logout
Created attachment 130040 [details] After login
Created attachment 130041 [details] After login dolphin launched
This could help perhaps to investigate the issue. It is always reproducible. Please see the attached scrennshots. 1. Before I logout, I make sure that the process "dolphin" is not running. 2. Logout. 3. Login again. 4. There is already running one "dolphin" process. 5. Launch Dolphin. 6. There are two "dolphin" processes running. 7. Interesting is that only one "dolphin" process got an icon.
I think I'm facing this bug with Kubuntu 20.04.1 (I had it in previous releases, but cannot remember how many). Each time I restart my machine, I get an additional new window of Dolphin. So there is the usual one with some tabs open, and one or several with my home folder opened. It's a bit annoying because if I don't close the new ones, I end up having many opened. In my ~/.config/ksmserverrc, I can see I have: program12=/usr/bin/dolphin program13=/usr/bin/dolphin restartCommand12=/usr/bin/dolphin,-session,10cde26262000160098025700000070490020_1601048614_510748 restartCommand13=/usr/bin/dolphin,-session,10cde26262000160104804000000021040011_1601048614_510564 In ~/.config/session, I can see that I have one file for the first (with data about the tabs), but not for the other one. I don't know more about ksmserver and how the programs manage the session saving and restoration, so I cannot provide right away more insight. If you think it's not the same bug, I can open another one.
Regarding my previous comment, tt turns out that for an unknown reason I had a file "~/.config/autostart/dolphin.desktop" which started "dolphin --deamon". After removing it, the additional Dolphin window/process does not show up any more in a new session. "dolphin --deamon" is not started automatically any more, but I don't know what will be the impact for me.
(In reply to Fabsk from comment #17) > Regarding my previous comment, tt turns out that for an unknown reason I had > a file "~/.config/autostart/dolphin.desktop" which started "dolphin > --deamon". After removing it, the additional Dolphin window/process does not > show up any more in a new session. "dolphin --deamon" is not started > automatically any more, but I don't know what will be the impact for me. In my case the directory "~/.config/autostart/" is empty. Dolphin continues to run in the background after it has been closed. I can watch it when I press Crtl+Esc.
@attila, could you run in a command line (Konsole for example) the following command after your login (as described in your summary): ps -efj |grep dolphin to see with which arguments the mysterious instance was launched (is it launched with "--deamon" or other parameters?). Also the 3rd column will tell you the process ID of the parent (excepted if it is "1"). In term of end-user experience, why is it a problem to have this additional problem? In my case I had an unwanted Dolphin window opened, but in your case I don't see (excepted some memory wasted maybe).
Here you go. The output of the command "ps -efj |grep dolphin" myusername 1446 1 1445 1445 1 10:49 ? 00:00:00 /usr/bin/dolphin --daemon The process ID is "1" and it is launched with "--daemon". Is this exactly what you expected? The process ID "1" is the init process which is responsible for starting and shutting down the system and so on. Do you have any idea what I can try? Do you need more information?
One more additional information. I have changed the setting from "restore last session" to "start with an empty session". The output of the command "ps -efj |grep dolphin" is the same. Process ID "1" and "--daemon". The only difference is that "Dolphin" doesn't come up.
I'm afraid I don't know more that you about the cause of the issue. There must be a configuration specific to Fedora that launches "dolphin --deamon". I'm too lazy to investigate any further. Again, does it cause any trouble to the end user (excepted having an additional unwanted dolphin process)? PPID == 1 can mean that the parent process has finished.
I think I have got it, but first let me just mention something. In your case Dolphin was autostarted because of "~/.config/autostart/dolphin.desktop". You had that file for an unknown reason and the behaviour was intended and OK. In my case the behaviour was unintended and really annoying plus a bad user experience. It has turned out that there is a file in "/etc/xdg/autostart/org.kde.dolphin.desktop" which is provided by the RPM "dolphin". This file contains a line "Exec=dolphin --daemon". I have deleted the file and Dolphin doesn't come up. Tt wasn't a big deal to me as a user to investigate a little further. Somehow I have to inform the Fedora packagers to remove the file "org.kde.dolphin.desktop", but I don't know how. Any idea?
Fedora does autostart 'dolphin --daemon' for plasma sessions, I can confirm this. I implemented it on purpose. It's a workaround to not rely on dbus activation, since there can be multiple providers. I believe that's been discussed at length in another bug
Related bug references, https://bugzilla.redhat.com/show_bug.cgi?id=1394927 https://bugzilla.redhat.com/show_bug.cgi?id=1808716 https://bugs.kde.org/show_bug.cgi?id=418322
Dupe of Bug 418322 I guess. Hopefully it will eventually fixed for Fedora users. *** This bug has been marked as a duplicate of bug 418322 ***
(In reply to Rex Dieter from comment #24) > Fedora does autostart 'dolphin --daemon' for plasma sessions, I can confirm > this. I implemented it on purpose. > > It's a workaround to not rely on dbus activation, since there can be > multiple providers. I believe that's been discussed at length in another bug There is one more workaround. I have added a new line to the file "/etc/xdg/autostart/org.kde.dolphin.desktop" with the following: Hidden=true It has the effect that dolphin won't come up unintentionally after login. I don't notice any problem after the file "org.kde.dolphin.desktop" has been deleted or I add a new line to the file "Hidden=true". It works for me in both cases. Would this new line solve the issue?
I'll echo here what I also said in the other bug. I'd argue this is still a bug worth solving on the kde side. dolphin --daemon processes should *not* be restored via session management.
That said, if autostarting 'dolphin --daemon' is going to be explicitly not supported by kde as a solution to the issue I highlighted, Red Hat bugzilla Bug 1394927 - Dolphin takes over the desktop folder in GNOME in F25 https://bugzilla.redhat.com/show_bug.cgi?id=1394927 Then, I'll revert it. But then I expect that issue should be addressed by kde some other (better?) way. Thoughts?
(In reply to Rex Dieter from comment #28) > I'll echo here what I also said in the other bug. > > I'd argue this is still a bug worth solving on the kde side. dolphin > --daemon processes should *not* be restored via session management. Seems fixable. I'm still not clear why you need this workaround on Fedora in the first place though. If dbus activation isn't reliable for Dolphin, isn't, like, the rest of the system broken too? We use dbus activation for a lot of things, and even more in Plasma 5.20 and beyond. Basically I want to understand the problem so we can see if the best solution is you removing the workaround, or us explicitly supporting it.
The full saga is in the linked bug, Bug 1394927 - Dolphin takes over the desktop folder in GNOME in F25 https://bugzilla.redhat.com/show_bug.cgi?id=1394927 Cliff's notes: As the title suggests, by default dolphin ships a dbus activation file at /usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service problem is that this file is offered unconditionally to all desktops, not just plasma. So, it can sometimes intercept org.freedesktop.FileManager1 dbus calls in gnome, for example. Workaround is instead of relying on the dbus activation, autostart 'dolphin --daemon' in plasma sessions only, that will listen on that dbus interface. In practice this works to solve that problem well... modulo this side-effect issue with session management.
@Rex: this should probably be discussed on plasma-devel. From the dolphin side I don't think we would have problems with plasma autostarting `dolphin --daemon`.
*** Bug 427905 has been marked as a duplicate of this bug. ***
I don't know of that's necessarily the best solution. I don't want a daemonized Dolphin instance always running in the background, consuming some resources, when dbus activtion works just fine for me. We could make the daemonized Dolphin not trigger session restoration I guess. That seems sensible enough.
(In reply to Nate Graham from comment #34) > I don't know of that's necessarily the best solution. I don't want a > daemonized Dolphin instance always running in the background, consuming some > resources, when dbus activtion works just fine for me. > I agree. Why wasting resources with a daemonized Dolphin instance always running in the background? It's been now three weeks since I have removed the file "/etc/xdg/autostart/org.kde.dolphin.desktop" and everything seems to work so far.
I'll re-iterate the background I outlined in comment #24 and comment #25, See dolphin's org.kde.dolphin.FileManager1.service file installed for dbus activation, contains: Name=org.freedesktop.FileManager1 It is possible for there to be multiple providers for org.freedesktop.FileManager1 (e.g. dolphin and nautlus). If you'd reviewed the old bugs I referenced, what happened was that dolphin was getting dbus-activated under gnome, for example, instead of nautilus. DBus activation has no way to prefer one provider over another. There's a very old bug open with dbus upstream about that, I've doubts it'll ever get addressed. So, in fedora we did 2 things: 1. omitted the dbus service file from packaging, to ensure it never gets dbus-activated (esp on non-plasma desktops) 2. set dolphin to autostart (in daemon mode), which allows dolphin to listen on those dbus interfaces at runtime Yes, it kinda sucks that another executable is running under plasma (dolphin --daemon) that may never get used, but the alternative is arguably worse... unexpectedly seeing nautilus running under plasma or dolphin running under gnome responding to org.freedesktop.FileManager1 dbus calls.
*** Bug 428207 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/88
Git commit bf11c835ebd934d9916327262f23edb25aeb8ab8 by Nate Graham. Committed on 29/10/2020 at 21:00. Pushed by ngraham into branch 'master'. Disable session management for daemon We don't need to autostart the daemon if it was running at logout. FIXED-IN: 20.12 M +9 -0 src/main.cpp https://invent.kde.org/system/dolphin/commit/bf11c835ebd934d9916327262f23edb25aeb8ab8