A thread on the Fedora Users list (see: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...)
mentioned an instance of Dolphin being started without the user configuring it as an Autostart item. I do use Autostart to fire up several Dolphin windows at login, but lately I've been noticing an extra one that I haven't asked for. A little research shows it apparently being started by systemd.
Anyone know what's going on?
poc
On 2/26/20 7:52 AM, Patrick O'Callaghan wrote:
A thread on the Fedora Users list (see: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...)
mentioned an instance of Dolphin being started without the user configuring it as an Autostart item. I do use Autostart to fire up several Dolphin windows at login, but lately I've been noticing an extra one that I haven't asked for. A little research shows it apparently being started by systemd.
Anyone know what's going on?
poc
I just spent a good amount of time on this same issue. For my session, I use "a previously saved session". I found suggestions to switch to starting with an empty session a couple of times, then switching back to a saved session. Saving a session creates ~/.config/session so before saving a session I deleted that to make sure there was nothing left over there. Originally I had noticed a dolphin related file in there. Saving a session when I had no dolphin window displayed removed it. However, upon logging off the session, one mysteriously appeared so the next time I logged in a dolphin window appeared.
I also found dolphin mentioned in the file ~/.config/ksmserverrc. I tried renaming that (so I would not lose it), then I logged out and logged in a few times and a new ksmserverrc was created. That, in combination with making sure there was no mention of dolphin in ~/.config/session and starting with an empty session for a bit and then going back to a saved session seems to have kept the dolphin window from showing up when I log in. However, there is still a dolphin process running no matter what I've tried.
ps -ef | grep dolphin charlie 3324 1 0 Feb22 ? 00:00:03 /usr/bin/dolphin --daemon
(Now, if I could just get pulseaudio to stop resetting volume to 100% after a logout/login, and yes I know about flat-volumes=no and removing ~/.pulse so PA can create a new one, but that's a problem for a different thread!)
Charles Dennett 30 year UNIX/Linux sys admin, retired!
That's legit, there's a 'dolphin --daemon' process autostart'd as part of f31+ plasma sessions to address bugs, https://bugzilla.redhat.com/show_bug.cgi?id=1394927 https://bugzilla.redhat.com/show_bug.cgi?id=1754395
-- Rex
On Wed, 2020-02-26 at 18:39 +0000, Rex Dieter wrote:
That's legit, there's a 'dolphin --daemon' process autostart'd as part of f31+ plasma sessions to address bugs, https://bugzilla.redhat.com/show_bug.cgi?id=1394927 https://bugzilla.redhat.com/show_bug.cgi?id=1754395
What's legit? When replying via HyperKitty please quote the context.
Even if a dolphin daemon is running, why does it throw up an unrequested Dolphin window? Also, I don't see the relevance of these two bug reports. One is about Gnome, and the other about themes. Neither appears to have anything to do with what's being asked about in this thread.
poc
On Wed, 2020-02-26 at 18:39 +0000, Rex Dieter wrote:
What's legit?
My apologies, I typically use gmane, but that appears to be not working on this list currently.
It was suggested in the referenced thread that the background dolphin process could be a bug. I was highlighting that is not true... it is not a bug and is intentional.
Even if a dolphin daemon is running, why does it throw up an unrequested Dolphin window?
I don't know, but it appears to have something with session restores. It is not caused by the autostart'd dolphin process, but could be related to it somehow.
Also, I don't see the relevance of these two bug reports.
That was only to give some background as to *why* this change was introduced (to run 'dolphin --daemon' on login).
-- Rex
On Thu, 2020-02-27 at 14:09 +0000, Rex Dieter wrote:
On Wed, 2020-02-26 at 18:39 +0000, Rex Dieter wrote:
What's legit?
My apologies, I typically use gmane, but that appears to be not working on this list currently.
It was suggested in the referenced thread that the background dolphin process could be a bug. I was highlighting that is not true... it is not a bug and is intentional.
Even if a dolphin daemon is running, why does it throw up an unrequested Dolphin window?
I don't know, but it appears to have something with session restores. It is not caused by the autostart'd dolphin process, but could be related to it somehow.
It's apparently also happening to people who don't have autostarted Dolphin, but presumably not everyone or there'd be more comments about it.
poc
On Thu, 27 Feb 2020, Patrick O'Callaghan wrote:
On Thu, 2020-02-27 at 14:09 +0000, Rex Dieter wrote:
I don't know, but it appears to have something with session restores. It is not caused by the autostart'd dolphin process, but could be related to it somehow.
It's apparently also happening to people who don't have autostarted Dolphin, but presumably not everyone or there'd be more comments about it.
It happens also to me but it something that I could leave with. It seems to affect the last version of KDE.
Walter
--
The real fix for bug #1754395 is to remove the Lmod package from your system. The 'dolphin --daemon' command doesn't actually fix the issue. That said, I don't have any of the problems the other people in this thread have been describing.
On 2020-02-26 1:39 p.m., Rex Dieter wrote:
That's legit, there's a 'dolphin --daemon' process autostart'd as part of f31+ plasma sessions to address bugs, https://bugzilla.redhat.com/show_bug.cgi?id=1394927 https://bugzilla.redhat.com/show_bug.cgi?id=1754395
-- Rex _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On Wed, 2020-02-26 at 23:08 -0500, Pizza Dude wrote:
The real fix for bug #1754395 is to remove the Lmod package from your system. The 'dolphin --daemon' command doesn't actually fix the issue. That said, I don't have any of the problems the other people in this thread have been describing.
I don't have the Lmod package.
poc
I apologize for late reply! At this moment my subscription request to kde fedora is still pending... So, i do not have the lmod package but i did solved the problem by removing /etc/xdg/servicemenu.knsrc So far i see no downsides to this.. Thanks! Adrian
On Thu, 2020-02-27 at 15:21 +0000, Adrian Sevcenco wrote:
I apologize for late reply! At this moment my subscription request to kde fedora is still pending... So, i do not have the lmod package but i did solved the problem by removing /etc/xdg/servicemenu.knsrc So far i see no downsides to this..
I guess it is /etc/xdg/autostart/org.kde.dolphin.desktop
Thanks! Adrian _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On Fri, 2020-02-28 at 06:27 +0000, Sérgio Basto wrote:
On Thu, 2020-02-27 at 15:21 +0000, Adrian Sevcenco wrote:
I apologize for late reply! At this moment my subscription request to kde fedora is still pending... So, i do not have the lmod package but i did solved the problem by removing /etc/xdg/servicemenu.knsrc So far i see no downsides to this..
I guess it is /etc/xdg/autostart/org.kde.dolphin.desktop
To repeat: some people are getting this even when Autostart has not been enabled for Dolphin.
poc
On Fri, Feb 28, 2020 at 6:59 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Fri, 2020-02-28 at 06:27 +0000, Sérgio Basto wrote:
[snip]
I guess it is /etc/xdg/autostart/org.kde.dolphin.desktop
To repeat: some people are getting this even when Autostart has not been enabled for Dolphin.
Perhaps, but removing that file fixed it for me.
And the blame looks like it's the packager for dolphin:
garry@vfr$ sudo dnf provides /etc/xdg/autostart/org.kde.dolphin.desktop Last metadata expiration check: 22:17:29 ago on Thu 27 Feb 2020 12:38:17 PM EST. dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : @System Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop
dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : updates Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop
garry@vfr$ uname -r 5.5.5-200.fc31.x86_64 garry@vfr$
By the way, System Settings -> Startup and Shutdown -> Autostart never showed Dolphin, even when the desktop file was in /etc/xdg/autostart. (That was the first thing I checked when this started happening.)
I believe this started when I upgraded to FC31, but I am not sure.
On Fri, 2020-02-28 at 11:10 -0500, Garry Williams wrote:
On Fri, Feb 28, 2020 at 6:59 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Fri, 2020-02-28 at 06:27 +0000, Sérgio Basto wrote:
[snip]
I guess it is /etc/xdg/autostart/org.kde.dolphin.desktop
To repeat: some people are getting this even when Autostart has not been enabled for Dolphin.
Perhaps, but removing that file fixed it for me.
And the blame looks like it's the packager for dolphin:
garry@vfr$ sudo dnf provides /etc/xdg/autostart/org.kde.dolphin.desktop Last metadata expiration check: 22:17:29 ago on Thu 27 Feb 2020
12:38:17 PM EST. dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : @System Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop
dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : updates Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop garry@vfr$ uname -r 5.5.5-200.fc31.x86_64 garry@vfr$
So the install is creating an autostart file? Definitely looks like a bug. However I'm not sure that is enough. I have Dolphin autostarted anyway, so it's no surprise to find that file there, but I'm still getting an extra window.
By the way, System Settings -> Startup and Shutdown -> Autostart never showed Dolphin, even when the desktop file was in /etc/xdg/autostart. (That was the first thing I checked when this started happening.)
I believe this started when I upgraded to FC31, but I am not sure.
I also think this is the case. It never happened with F30.
poc
On 2/28/20 11:10 AM, Garry Williams wrote:
And the blame looks like it's the packager for dolphin:
garry@vfr$ sudo dnf provides /etc/xdg/autostart/org.kde.dolphin.desktop Last metadata expiration check: 22:17:29 ago on Thu 27 Feb 2020
12:38:17 PM EST. dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : @System Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop
dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : updates Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop garry@vfr$ uname -r 5.5.5-200.fc31.x86_64 garry@vfr$
and I'll verify that a slightly different way:
[charlie@redwood ~]$ rpm -ql dolphin | head -4 /etc/xdg/autostart/org.kde.dolphin.desktop /etc/xdg/servicemenu.knsrc /usr/bin/dolphin /usr/bin/servicemenuinstaller
I've also experienced the same issue. I replied to this tread couple of days ago but I didn't see it come back to the list. I had found dolphin mentioned in the file ~/.config/.ksmserverrc. A combination of removing that file, switching to starting with an empty session, logout/login, switching back to a saved session and then saving the session fixed it for me.
Charlie
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
On 2/28/20 11:10 AM, Garry Williams wrote:
And the blame looks like it's the packager for dolphin:
garry@vfr$ sudo dnf provides /etc/xdg/autostart/org.kde.dolphin.desktop Last metadata expiration check: 22:17:29 ago on Thu 27 Feb 2020
12:38:17 PM EST. dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : @System Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop
dolphin-19.12.1-1.fc31.x86_64 : KDE File Manager Repo : updates Matched from: Filename : /etc/xdg/autostart/org.kde.dolphin.desktop garry@vfr$ uname -r 5.5.5-200.fc31.x86_64 garry@vfr$
and I'll verify that a slightly different way:
[charlie@redwood ~]$ rpm -ql dolphin | head -4 /etc/xdg/autostart/org.kde.dolphin.desktop /etc/xdg/servicemenu.knsrc /usr/bin/dolphin /usr/bin/servicemenuinstaller
I've also experienced the same issue. I replied to this tread couple of days ago but I didn't see it come back to the list. I had found dolphin mentioned in the file ~/.config/.ksmserverrc. A combination of removing that file, switching to starting with an empty session, logout/login, switching back to a saved session and then saving the session fixed it for me.
I suggest you file a bug report against Dolphin including that experience. If you post the URL here then others can comment.
poc
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin [poc@Bree ~]$ file /usr/bin/dolphin /bin/dolphin /usr/bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped /bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped [poc@Bree ~]$ rpm -qf /usr/bin/dolphin /bin/dolphin dolphin-19.12.1-1.fc31.x86_64 dolphin-19.12.1-1.fc31.x86_64
and are both installed from the package. That has to be an error, surely.
poc
On Sat, 2020-02-29 at 12:31 +0000, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin [poc@Bree ~]$ file /usr/bin/dolphin /bin/dolphin /usr/bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped /bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped [poc@Bree ~]$ rpm -qf /usr/bin/dolphin /bin/dolphin dolphin-19.12.1-1.fc31.x86_64 dolphin-19.12.1-1.fc31.x86_64
and are both installed from the package. That has to be an error, surely.
poc
I've filed this as https://bugs.kde.org/show_bug.cgi?id=418322
poc
On 2020-02-29 20:43, Patrick O'Callaghan wrote:
On Sat, 2020-02-29 at 12:31 +0000, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin [poc@Bree ~]$ file /usr/bin/dolphin /bin/dolphin /usr/bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped /bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped [poc@Bree ~]$ rpm -qf /usr/bin/dolphin /bin/dolphin dolphin-19.12.1-1.fc31.x86_64 dolphin-19.12.1-1.fc31.x86_64
and are both installed from the package. That has to be an error, surely.
poc
I've filed this as https://bugs.kde.org/show_bug.cgi?id=418322
Oh, I keep forgetting....
[egreshko@f31k ~]$ ls -lid /usr/bin /bin 12 lrwxrwxrwx. 1 root root 7 Jul 25 2019 /bin -> usr/bin 916871 dr-xr-xr-x. 2 root root 69632 Feb 25 12:13 /usr/bin
So, not a hard link.
On Sat, 2020-02-29 at 21:52 +0800, Ed Greshko wrote:
On 2020-02-29 20:43, Patrick O'Callaghan wrote:
On Sat, 2020-02-29 at 12:31 +0000, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin [poc@Bree ~]$ file /usr/bin/dolphin /bin/dolphin /usr/bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped /bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped [poc@Bree ~]$ rpm -qf /usr/bin/dolphin /bin/dolphin dolphin-19.12.1-1.fc31.x86_64 dolphin-19.12.1-1.fc31.x86_64
and are both installed from the package. That has to be an error, surely.
poc
I've filed this as https://bugs.kde.org/show_bug.cgi?id=418322
Oh, I keep forgetting....
[egreshko@f31k ~]$ ls -lid /usr/bin /bin 12 lrwxrwxrwx. 1 root root 7 Jul 25 2019 /bin -> usr/bin 916871 dr-xr-xr-x. 2 root root 69632 Feb 25 12:13 /usr/bin
So, not a hard link.
Yes, newbie mistake on my part. Still a bug though.
https://bugzilla.redhat.com/show_bug.cgi?id=1808716
poc
On 2020-03-01 00:38, Patrick O'Callaghan wrote:
Yes, newbie mistake on my part. Still a bug though.
I made some comments in that BZ. But, to summerize here.
I deleted the ksmserverrc and logged in to KDE with a "Blank Session".
Checking from a remote system I see
[egreshko@f31k .config]$ ls ksmserverrc ls: cannot access 'ksmserverrc': No such file or directory
[egreshko@f31k .config]$ ps -eaf | grep dolp egreshko 1228 1 0 11:05 ? 00:00:00 /usr/bin/dolphin --daemon
No dolphin window is open.
I then check, in systemsettings, "Restore Previous Session" and logout
Checking again from remote a ksmserverrc exists and contains
[egreshko@f31k .config]$ cat ksmserverrc [General] confirmLogout=true excludeApps= loginMode=restorePreviousLogout offerShutdown=true shutdownType=0
[LegacySession: saved at previous logout] count=0
[Session: saved at previous logout] clientId1=1013516517d1ac000158303194800000011660005 clientId2=1013516517d1ac000158303194900000011660009 clientId3=1013516517d1ac000158303195000000011660010 clientId4=1013516517d1ac000158303195100000011660012 count=4 discardCommand1[$e]=rm,$HOME/.config/session/kwin_1013516517d1ac000158303194800000011660005_1583032124_413499 program1=/usr/bin/kwin_x11 program2=/usr/bin/dolphin program3=/usr/bin/korgac program4=pulseaudio restartCommand1=/usr/bin/kwin_x11,-session,1013516517d1ac000158303194800000011660005_1583032124_413499 restartCommand2=/usr/bin/dolphin,-session,1013516517d1ac000158303194900000011660009_1583032124_391506 restartCommand3=/usr/bin/korgac,-session,1013516517d1ac000158303195000000011660010_1583032124_391665 restartCommand4= restartStyleHint1=0 restartStyleHint2=0 restartStyleHint3=0 restartStyleHint4=0 userId1=egreshko userId2=egreshko userId3=egreshko userId4=egreshko wasWm1=true wasWm2=false wasWm3=false wasWm4=false
And, sure enough, a dolphin window appears on login.
I would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
On 2020-03-01 00:38, Patrick O'Callaghan wrote:
Yes, newbie mistake on my part. Still a bug though.
I made some comments in that BZ. But, to summerize here.
I deleted the ksmserverrc and logged in to KDE with a "Blank Session".
Checking from a remote system I see
[egreshko@f31k .config]$ ls ksmserverrc ls: cannot access 'ksmserverrc': No such file or directory
[egreshko@f31k .config]$ ps -eaf | grep dolp egreshko 1228 1 0 11:05 ? 00:00:00 /usr/bin/dolphin --daemon
No dolphin window is open.
I then check, in systemsettings, "Restore Previous Session" and logout
Checking again from remote a ksmserverrc exists and contains
[egreshko@f31k .config]$ cat ksmserverrc [General] confirmLogout=true excludeApps= loginMode=restorePreviousLogout offerShutdown=true shutdownType=0
[LegacySession: saved at previous logout] count=0
[Session: saved at previous logout] clientId1=1013516517d1ac000158303194800000011660005 clientId2=1013516517d1ac000158303194900000011660009 clientId3=1013516517d1ac000158303195000000011660010 clientId4=1013516517d1ac000158303195100000011660012 count=4 discardCommand1[$e]=rm,$HOME/.config/session/kwin_1013516517d1ac00015 8303194800000011660005_1583032124_413499 program1=/usr/bin/kwin_x11 program2=/usr/bin/dolphin program3=/usr/bin/korgac program4=pulseaudio restartCommand1=/usr/bin/kwin_x11,- session,1013516517d1ac000158303194800000011660005_1583032124_413499 restartCommand2=/usr/bin/dolphin,- session,1013516517d1ac000158303194900000011660009_1583032124_391506 restartCommand3=/usr/bin/korgac,- session,1013516517d1ac000158303195000000011660010_1583032124_391665 restartCommand4= restartStyleHint1=0 restartStyleHint2=0 restartStyleHint3=0 restartStyleHint4=0 userId1=egreshko userId2=egreshko userId3=egreshko userId4=egreshko wasWm1=true wasWm2=false wasWm3=false wasWm4=false
And, sure enough, a dolphin window appears on login.
I would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
That it , if you have [1] and you save the session, on logout/login will appear one dolphin window , but if after close dolphin, you kill the process of the dolphin (kill 1228) and after you save the session, on logout/login it will *not* appears the dolphin window.
[1] ps -ef | grep dolp 1228 1 0 11:05 ? 00:00:00 /usr/bin/dolphin --daemon
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
On 2020-03-01 00:38, Patrick O'Callaghan wrote:
Yes, newbie mistake on my part. Still a bug though.
I made some comments in that BZ. But, to summerize here.
I deleted the ksmserverrc and logged in to KDE with a "Blank Session".
Checking from a remote system I see
[egreshko@f31k .config]$ ls ksmserverrc ls: cannot access 'ksmserverrc': No such file or directory
[egreshko@f31k .config]$ ps -eaf | grep dolp egreshko 1228 1 0 11:05 ? 00:00:00 /usr/bin/dolphin --daemon
No dolphin window is open.
I then check, in systemsettings, "Restore Previous Session" and logout
Checking again from remote a ksmserverrc exists and contains
[egreshko@f31k .config]$ cat ksmserverrc [General] confirmLogout=true excludeApps= loginMode=restorePreviousLogout offerShutdown=true shutdownType=0
[LegacySession: saved at previous logout] count=0
[Session: saved at previous logout] clientId1=1013516517d1ac000158303194800000011660005 clientId2=1013516517d1ac000158303194900000011660009 clientId3=1013516517d1ac000158303195000000011660010 clientId4=1013516517d1ac000158303195100000011660012 count=4 discardCommand1[$e]=rm,$HOME/.config/session/kwin_1013516517d1ac000158303194800000011660005_1583032124_413499 program1=/usr/bin/kwin_x11 program2=/usr/bin/dolphin program3=/usr/bin/korgac program4=pulseaudio restartCommand1=/usr/bin/kwin_x11,-session,1013516517d1ac000158303194800000011660005_1583032124_413499 restartCommand2=/usr/bin/dolphin,-session,1013516517d1ac000158303194900000011660009_1583032124_391506 restartCommand3=/usr/bin/korgac,-session,1013516517d1ac000158303195000000011660010_1583032124_391665 restartCommand4= restartStyleHint1=0 restartStyleHint2=0 restartStyleHint3=0 restartStyleHint4=0 userId1=egreshko userId2=egreshko userId3=egreshko userId4=egreshko wasWm1=true wasWm2=false wasWm3=false wasWm4=false
And, sure enough, a dolphin window appears on login.
I would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
Well spotted. The /bin/dolphin - /usr/bin/dolphin thing looks like a distraction (I see it in old ksmserverrc files from before F31).
That would imply that's an actual bug rather than a packaging error.
poc
On 2020-03-01 18:40, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
It would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
Well spotted. The /bin/dolphin - /usr/bin/dolphin thing looks like a distraction (I see it in old ksmserverrc files from before F31).
That would imply that's an actual bug rather than a packaging error.
Yes, a bug against what component? I have no idea what is responsible for saving session info on logout.
On Sun, 2020-03-01 at 19:13 +0800, Ed Greshko wrote:
On 2020-03-01 18:40, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
It would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
Well spotted. The /bin/dolphin - /usr/bin/dolphin thing looks like a distraction (I see it in old ksmserverrc files from before F31).
That would imply that's an actual bug rather than a packaging error.
Yes, a bug against what component? I have no idea what is responsible for saving session info on logout.
Me neither. I guess this should go upstream, but I'm not that familiar with who decides these things. When I originally reported it to bugs.kde.org I was told it was a packaging error and to refer it to my distro, which I did, but that now looks to be wrong. Hopefully some responsible person at Fedora Orbiting HQ will Do the Right Thing.
poc
On 2020-03-01 20:07, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 19:13 +0800, Ed Greshko wrote:
On 2020-03-01 18:40, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
It would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
Well spotted. The /bin/dolphin - /usr/bin/dolphin thing looks like a distraction (I see it in old ksmserverrc files from before F31).
That would imply that's an actual bug rather than a packaging error.
Yes, a bug against what component? I have no idea what is responsible for saving session info on logout.
Me neither. I guess this should go upstream, but I'm not that familiar with who decides these things. When I originally reported it to bugs.kde.org I was told it was a packaging error and to refer it to my distro, which I did, but that now looks to be wrong. Hopefully some responsible person at Fedora Orbiting HQ will Do the Right Thing.
Maybe it would be sufficient to file it under plasma-workspace and let maintainers decided if it should be reassigned?
On Mon, 2020-03-02 at 10:10 +0800, Ed Greshko wrote:
On 2020-03-01 20:07, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 19:13 +0800, Ed Greshko wrote:
On 2020-03-01 18:40, Patrick O'Callaghan wrote:
On Sun, 2020-03-01 at 11:11 +0800, Ed Greshko wrote:
It would seem that /usr/bin/dolphin --daemon running on logout was treated as an open window.
Well spotted. The /bin/dolphin - /usr/bin/dolphin thing looks like a distraction (I see it in old ksmserverrc files from before F31).
That would imply that's an actual bug rather than a packaging error.
Yes, a bug against what component? I have no idea what is responsible for saving session info on logout.
Me neither. I guess this should go upstream, but I'm not that familiar with who decides these things. When I originally reported it to bugs.kde.org I was told it was a packaging error and to refer it to my distro, which I did, but that now looks to be wrong. Hopefully some responsible person at Fedora Orbiting HQ will Do the Right Thing.
Maybe it would be sufficient to file it under plasma-workspace and let maintainers decided if it should be reassigned?
I'll do that and see what happens.
poc
On 2020-03-03 18:27, Patrick O'Callaghan wrote:
On Tue, 2020-03-03 at 16:11 +0800, Ed Greshko wrote:
On 2020-03-02 18:54, Patrick O'Callaghan wrote:
I'll do that and see what happens.
Post the BZ# when you do.
I reopened the KDE bug report and added a comment pointing back to the Fedora BZ.
Oh, I kinda thought it would deserve a new BZ with a Description which actually reflects what is going on. I mean, we know that having linked directories isn't at all the issue.
On Tue, 2020-03-03 at 19:08 +0800, Ed Greshko wrote:
On 2020-03-03 18:27, Patrick O'Callaghan wrote:
On Tue, 2020-03-03 at 16:11 +0800, Ed Greshko wrote:
On 2020-03-02 18:54, Patrick O'Callaghan wrote:
I'll do that and see what happens.
Post the BZ# when you do.
I reopened the KDE bug report and added a comment pointing back to the Fedora BZ.
Oh, I kinda thought it would deserve a new BZ with a Description which actually reflects what is going on. I mean, we know that having linked directories isn't at all the issue.
Rex has corrected the description and added some comments.
poc
On 2020-02-29 20:31, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin
[egreshko@f31k ~]$ ls -li /usr/bin/dolphin /bin/dolphin 917553 -rwxr-xr-x. 1 root root 16072 Jan 15 23:14 /bin/dolphin 917553 -rwxr-xr-x. 1 root root 16072 Jan 15 23:14 /usr/bin/dolphin
Same inode.
Hard link.
On Sat, 2020-02-29 at 21:46 +0800, Ed Greshko wrote:
On 2020-02-29 20:31, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin
[egreshko@f31k ~]$ ls -li /usr/bin/dolphin /bin/dolphin 917553 -rwxr-xr-x. 1 root root 16072 Jan 15 23:14 /bin/dolphin 917553 -rwxr-xr-x. 1 root root 16072 Jan 15 23:14 /usr/bin/dolphin
Same inode.
Hard link.
Not a hard link (or the link count would be > 2) but as you point out separately, /bin is symlinked to /usr/bin. I updated the BZ report (the Fedora one, not the KDE one).
poc
On Sat, 2020-02-29 at 12:31 +0000, Patrick O'Callaghan wrote:
On Fri, 2020-02-28 at 13:37 -0500, Charles R. Dennett wrote:
I had found dolphin mentioned in the file ~/.config/.ksmserverrc.
That would be ~/.config/ksmserverrc I presume. I'm seeing two Dolphin lines in mine as well, but on closer examination it appears as two different programs, /bin/dolphin and /usr/bin/dolphin.
Furthermore, these two actually exist as separate files:
$ ls -l /usr/bin/dolphin /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /bin/dolphin -rwxr-xr-x. 1 root root 16072 Jan 15 15:14 /usr/bin/dolphin [poc@Bree ~]$ file /usr/bin/dolphin /bin/dolphin /usr/bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped /bin/dolphin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9f3b25cfd17490fb978dd8e16b0020e83739a07d, for GNU/Linux 3.2.0, stripped [poc@Bree ~]$ rpm -qf /usr/bin/dolphin /bin/dolphin dolphin-19.12.1-1.fc31.x86_64 dolphin-19.12.1-1.fc31.x86_64
ll /bin /bin -> usr/bin
/usr/bin/dolphin and /bin/dolphin are the same file
rpm -qf /etc/xdg/autostart/org.kde.dolphin.desktop dolphin-19.12.1-1.fc31.x86_64
/etc/xdg/autostart/org.kde.dolphin.desktop is installed by dolphin package
and are both installed from the package. That has to be an error, surely.
poc _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On Sat, 2020-02-29 at 17:20 +0000, Sérgio Basto wrote:
/etc/xdg/autostart/org.kde.dolphin.desktop is installed by dolphin package
I know. As the BZ report says, the probable origin of the problem is that the dolphin executable has two names, and (at least in some circumstances) the ksmserverrc file refers to both of them, making them look like two different programs. I assume that's why Dolphin is being started twice.
Possibly the name change occurred in the update from F30 to F31, so ksmserverrc files retained from F30 have acquired a new entry because of the name change. I'm just guessing.
One test would be to remove one (or even both) entries from that file and restart the session to see what happens.
poc