clone 657751 -1
retitle -1 '/etc/init.d/gdm3 stop' does not terminate Debian-gdm's dbus-daemons
etc.
severity -1 normal
thanks
On Sun, 02 Sep 2012 at 21:41:21 +0200, Salvatore Bonaccorso wrote:
> I tried to reproduce this via an installation in a VM, login in a user
> and then purging gdm3. The removal went without the problems
> described.
Perhaps you didn't have a complete GNOME system, only gdm3 itself? I can
reproduce this in two ways:
* install the GNOME desktop task in a VM
* switch to tty1 and purge gdm3, gnome-core, gnome and task-gnome-desktop
and
* install the GNOME desktop task in a VM
* log in to X as a user (on tty7)
* user menu -> Switch User (moves you to tty8 with a GDM "greeter")
* switch to tty1 and purge gdm3, gnome-core, gnome and task-gnome-desktop
Not all of the "greeter" processes die when /etc/init.d/gdm3 stop is run:
default|archetype% ssh wheezy-desktop ps -U Debian-gdm -u Debian-gdm u ~
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
108 2842 0.0 0.1 30188 1192 ? Ss 21:25 0:00
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
108 2864 0.0 0.2 53628 2328 ? S 21:25 0:00
/usr/lib/gvfs/gvfsd
108 2870 0.0 0.3 152956 3296 ? Sl 21:25 0:00
/usr/lib/at-spi2-core/at-spi-bus-launcher
108 2874 0.0 0.1 29920 1508 ? S 21:25 0:00
/usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork
--print-address 3
> [But anyway, Paul already did an analysis which in any case (even not
> triggered here) should further 'stabilize' the possible purge process
> for gdm3.]
This does seem to fix it; I've uploaded it.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
