Bug#920460: nautilus: org.freedesktop.FileManager1.service conflict
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2019-01-25 at 15:40 -0700, Jason Crain wrote: > This issue was discussed a while ago in a Debian bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860796#56. smcv's > comment in that bug includes some suggestions. To fix the file conflict, > probably no file manager should install the > org.freedesktop.FileManager1.service file. To fix the service name > conflict, he mentions the posibility of modifying the service file > specification so that a service can declare that it implements the > org.freedesktop.FileManager1 service under a certain DE. Hi, thanks for the feedback. On Xfce upstream bug report ( https://bugzilla.xfce.org/show_bug.cgi?id=15088) there's also an ongoing discussion. For now they renamed the file so the file conflict is gone, but the service name conflict is still there. > > Alternatively, when a DE starts up, it could grab the FileManager1 name > so any requests will be forwarded to the correct file manager for that > desktop, instead of relying on D-Bus activation. Right now, Xfce should start Thunar daemon by default, so it should grab the service name if it's not already taken. But in other desktops, depending on if you want to use Thunar or not, it might be a problem. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlxOufAACgkQ3rYcyPpX RFsMvwgAw9zLCkjplolJh6tM9DF3mZcJ2/8cz9nmdvbpo6tCAZFtPFhAE/7hsHpN 2ctxvuhYn+R2v3mJrTgro0cn3HjHjNMW9VXud+lrW7onD6YTr3RE6tz75EbbWCCk cM2n+bC6SAewHN2X8/+WA3EZPIx/2MV/NKUip2iLz3PVKXBdSJGC8cmwMUKz7Z0v Xig3R09cdalO52+AkpwPz4/ms+JVcuF3qbgK/UeqD4wjK7pk/0qu8/7/DV1NoULM SBoYI/KYYIquzGkGJmxXSptDeMX5AV9uZmPuj9kiagh1xrOWVjFJ/tw3ZTQep/wu hH/D8bZ7qvPjOvMCbq9dk9lDuxvwxg== =iCLR -END PGP SIGNATURE-
Bug#920460: nautilus: org.freedesktop.FileManager1.service conflict
> Until now, Nautilus was the only package providing this, Seems like dolphin as well provides the service in "org.kde.dolphin.FileManager1.service". That's why I thought renaming would be sufficient. For the concrete packaging of thunar 1.8.3: Arch solved it like that: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/thunar&id=c8928f211dbe01f9a3ba03bdc4b894cb3381d03e But today this one popped up: https://bugzilla.xfce.org/show_bug.cgi?id=15088 So I wonder if it possibly would be the safest to revert the related thunar commit ( c06074065460e63cf78ef1c5b7eb819fa6a86430 ) At least until it is clear which way to go.
Bug#920460: nautilus: org.freedesktop.FileManager1.service conflict
On Fri, Jan 25, 2019 at 09:01:54PM +0100, Yves-Alexis Perez wrote: > this is a “preemptive” bug about a future file conflict. Latest Thunar > upstream version (1.8.3) gained support for the > org.freedesktop.FileManager1 DBus name > (https://bugzilla.xfce.org/show_bug.cgi?id=12414). Funny, org.freedesktop.FileManager1 was just mentioned earlier today on GNOME's #gnome-hackers IRC channel. My understanding of how this service name was originally used is that the desktop environment automatically started its file manager when the desktop session began, possibly so it could manage the desktop icons and background, and the file manager registered the org.freedesktop.FileManager1 name. Then, if any program sends a message to FileManager1, they'll get the one started by the desktop environment. But current GNOME doesn't start nautilus on session start, so if you have multiple desktop environments installed and send a message to FileManager1, D-Bus activation starts a file manager and it's unpredictable which one it will run. This issue was discussed a while ago in a Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860796#56. smcv's comment in that bug includes some suggestions. To fix the file conflict, probably no file manager should install the org.freedesktop.FileManager1.service file. To fix the service name conflict, he mentions the posibility of modifying the service file specification so that a service can declare that it implements the org.freedesktop.FileManager1 service under a certain DE. Alternatively, when a DE starts up, it could grab the FileManager1 name so any requests will be forwarded to the correct file manager for that desktop, instead of relying on D-Bus activation.
Bug#920460: nautilus: org.freedesktop.FileManager1.service conflict
Source: nautilus Version: 3.30.5-1 Severity: normal Hi, this is a “preemptive” bug about a future file conflict. Latest Thunar upstream version (1.8.3) gained support for the org.freedesktop.FileManager1 DBus name (https://bugzilla.xfce.org/show_bug.cgi?id=12414). This is a generic Freedesktop name which is supposed to be used to open the file manager of the current desktop. Until now, Nautilus was the only package providing this, but now we have a problem. First is obviously a file conflict if I upload Thunar 1.8.3-1 as-is, the second beeing a conflict on the service name itself, even if I (for example) rename the file. It's not the first time we have issues like this, generic DBus names aren't really practical for distributions. I'm open to sugestions on how to handle this. Regards, -- Yves-Alexis -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
