Bug#909027: Leaves daemons running after purge
Control: severity -1 important This at least isn't an RC issue. I'm thinking about closing this bug unless there is something clear that should be done in the gvfs packaging for this issue. Thanks, Jeremy Bicha
Bug#909027: Leaves daemons running after purge
On Mon, 17 Sep 2018 at 15:36:48 -0400, Jeremy Bicha wrote: > On Mon, Sep 17, 2018 at 12:47 PM Steve McIntyre wrote: > > >I appear to have had some of the gvfs packages installed by accident > > >on my machine, I guess through dependencies. I noticed this a few days > > >ago and purged them all. I saw no errors when I did that. I noticed > > >again today that I still have gvfs programs running. This is clearly > > >not right. > > The gvfs daemon are system user services. I assume this was meant to say "systemd user services" (that is, services that are managed by the systemd --user process that runs under your own uid, as opposed to systemd system services, which are managed by pid 1). Various other packages install per-user daemons, some of which are managed by systemd, some of which are not, and many of which can go either way depending on whether systemd --user is in use. We've had per-user daemons for a long time, some of them longer than I've been involved in Debian - prominent examples include ssh-agent, gpg-agent, configuration synchronization points like dconf and gconf, IPC systems like D-Bus and CORBA, and sound mixers like pulseaudio, esd and arts. > These services keep running > after removal; another example is gpg-agent. All you need to do is log > out for the services to be stopped. I don't think Debian has ever had a general solution to terminating per-user services on remove or purge. The least-bad option I can see would be to use pkill or killall from the postinst, but that comes with a serious risk of accidentally terminating processes other than the one being removed (for example if you'd removed the packaged gvfs services in order to run your own /usr/local/bin/gvfsd, you'd be upset if the maintainer script killed that). Even if we can assume that all interesting per-user daemons are systemd user services, it's generally considered to be an anti-pattern for a system-wide operation (removing a package) to reach into user sessions and do things there. In particular, it can't use D-Bus on the session bus, because the trust relationships would be wrong: D-Bus clients trust their dbus-daemon, but maintainer scripts running as root must not trust a dbus-daemon running as a user. smcv
Bug#909027: Leaves daemons running after purge
On Mon, Sep 17, 2018 at 12:47 PM Steve McIntyre wrote: > On Mon, Sep 17, 2018 at 05:23:53PM +0100, Steve McIntyre wrote: > >Package: gvfsd-metadata > >Version: 1.30.4-1 > >Severity: serious > > > >Hi folks, > > > >I appear to have had some of the gvfs packages installed by accident > >on my machine, I guess through dependencies. I noticed this a few days > >ago and purged them all. I saw no errors when I did that. I noticed > >again today that I still have gvfs programs running. This is clearly > >not right. To verify, I've just reinstalled gvfs-daemons and purged it > >again. I still have things running: Steve, thank you for filing this bug. However, it doesn't look release-critical to me since I don't think Debian Policy says anywhere that daemons or services must be stopped on package removal. For instance, Firefox or any app keeps running after you remove it. Many GNOME apps now are D-Bus-activated and keep running in the background even though they may not appear to be running unless someone looks closely. The gvfs daemon are system user services. These services keep running after removal; another example is gpg-agent. All you need to do is log out for the services to be stopped. Maybe, this ends up being a duplicate of https://bugs.debian.org/764678 or maybe it needs a new bug not in gvfs. Or maybe we don't even need to change the behavior here. But we have others on the Debian GNOME team that know a lot more about dbus and systemd than I do. Thanks, Jeremy Bicha
Bug#909027: Leaves daemons running after purge
Control: reassign -1 gvfs-daemons Arg, failed at cut and paste for the package name. -ENOSLEEP :-( On Mon, Sep 17, 2018 at 05:23:53PM +0100, Steve McIntyre wrote: >Package: gvfsd-metadata >Version: 1.30.4-1 >Severity: serious > >Hi folks, > >I appear to have had some of the gvfs packages installed by accident >on my machine, I guess through dependencies. I noticed this a few days >ago and purged them all. I saw no errors when I did that. I noticed >again today that I still have gvfs programs running. This is clearly >not right. To verify, I've just reinstalled gvfs-daemons and purged it >again. I still have things running: > >tack:~$ ps wwwaux | grep gvfs >steve 5547 0.0 0.0 193744 0 ?Ssl Sep04 0:00 >/usr/lib/gvfs/gvfsd-metadata >steve13027 0.0 0.0 284500 0 ?Ssl Aug27 0:00 >/usr/lib/gvfs/gvfsd >steve16920 0.0 0.0 12784 980 pts/30 S+ 17:22 0:00 grep gvfs >steve26728 0.0 0.0 360488 6268 ?Ssl Aug29 11:39 >/usr/lib/gvfs/gvfs-udisks2-volume-monitor >steve26738 0.0 0.0 281776 1416 ?Ssl Aug29 0:00 >/usr/lib/gvfs/gvfs-gphoto2-volume-monitor >steve26742 0.0 0.0 269564 0 ?Ssl Aug29 0:00 >/usr/lib/gvfs/gvfs-goa-volume-monitor >steve26746 0.0 0.0 370236 0 ?Ssl Aug29 0:00 >/usr/lib/gvfs/gvfs-afc-volume-monitor >steve26751 0.0 0.0 271708 1812 ?Ssl Aug29 0:00 >/usr/lib/gvfs/gvfs-mtp-volume-monitor >steve26756 0.0 0.0 360640 4068 ?Sl Aug29 2:05 >/usr/lib/gvfs/gvfsd-trash --spawner :1.8 /org/gtk/gvfs/exec_spaw/0 >steve26769 0.0 0.0 436600 3904 ?Sl Aug29 0:00 >/usr/lib/gvfs/gvfsd-network --spawner :1.8 /org/gtk/gvfs/exec_spaw/1 >steve26775 0.0 0.0 724220 4272 ?Sl Aug29 0:00 >/usr/lib/gvfs/gvfsd-smb-browse --spawner :1.8 /org/gtk/gvfs/exec_spaw/2 >steve26788 0.0 0.0 371776 3508 ?Sl Aug29 0:01 >/usr/lib/gvfs/gvfsd-dnssd --spawner :1.8 /org/gtk/gvfs/exec_spaw/3 > >This is clearly not right! > >-- System Information: >Debian Release: 9.5 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') >Architecture: amd64 (x86_64) >Foreign Architectures: i386 > >Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) >Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), >LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) >Shell: /bin/sh linked to /bin/dash >Init: systemd (via /run/systemd/system) > -- Steve McIntyre, Cambridge, UK.st...@einval.com "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." -- Edward Snowden
Bug#909027: Leaves daemons running after purge
Package: gvfsd-metadata Version: 1.30.4-1 Severity: serious Hi folks, I appear to have had some of the gvfs packages installed by accident on my machine, I guess through dependencies. I noticed this a few days ago and purged them all. I saw no errors when I did that. I noticed again today that I still have gvfs programs running. This is clearly not right. To verify, I've just reinstalled gvfs-daemons and purged it again. I still have things running: tack:~$ ps wwwaux | grep gvfs steve 5547 0.0 0.0 193744 0 ?Ssl Sep04 0:00 /usr/lib/gvfs/gvfsd-metadata steve13027 0.0 0.0 284500 0 ?Ssl Aug27 0:00 /usr/lib/gvfs/gvfsd steve16920 0.0 0.0 12784 980 pts/30 S+ 17:22 0:00 grep gvfs steve26728 0.0 0.0 360488 6268 ?Ssl Aug29 11:39 /usr/lib/gvfs/gvfs-udisks2-volume-monitor steve26738 0.0 0.0 281776 1416 ?Ssl Aug29 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor steve26742 0.0 0.0 269564 0 ?Ssl Aug29 0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor steve26746 0.0 0.0 370236 0 ?Ssl Aug29 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor steve26751 0.0 0.0 271708 1812 ?Ssl Aug29 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor steve26756 0.0 0.0 360640 4068 ?Sl Aug29 2:05 /usr/lib/gvfs/gvfsd-trash --spawner :1.8 /org/gtk/gvfs/exec_spaw/0 steve26769 0.0 0.0 436600 3904 ?Sl Aug29 0:00 /usr/lib/gvfs/gvfsd-network --spawner :1.8 /org/gtk/gvfs/exec_spaw/1 steve26775 0.0 0.0 724220 4272 ?Sl Aug29 0:00 /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.8 /org/gtk/gvfs/exec_spaw/2 steve26788 0.0 0.0 371776 3508 ?Sl Aug29 0:01 /usr/lib/gvfs/gvfsd-dnssd --spawner :1.8 /org/gtk/gvfs/exec_spaw/3 This is clearly not right! -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
