Control: forwarded -1 https://bugs.launchpad.net/debian/+source/lightdm/+bug/1366534
On dim., 2014-09-07 at 14:57 +0200, Samuel Thibault wrote:
> Package: lightdm
> Version: 1.10.1-3
> Severity: important
> User: debian-accessibility@lists.debian.org
> USertags: a11y
>
> Hello,
>
> After a fresh Jessie install of Debian with the XFCE desktop and logging
> in with the user created at installation ("joe"), there are some
> processes left behind by lightdm, running ad lightdm user, notably:
>
> lightdm 509 0.0 0.0 24340 588 ? S 14:45 0:00 /usr/bin/dbus-launch --autolaunch 1b4e071b23e9498f9e505e31c68727f0 --binary-syntax --close-stderr
> lightdm 510 0.0 0.1 41580 1116 ? Ss 14:45 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
> lightdm 512 0.0 0.3 337456 3180 ? Sl 14:45 0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
> lightdm 516 0.0 0.1 41580 1720 ? S 14:45 0:00 \_ /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
> lightdm 519 0.0 0.3 125220 3512 ? Sl 14:45 0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
>
> The at-spi-bus-launcher and at-spi2-registryd are problematic: since
> they are there on the X display, joe's session can not start its own
> at-spi-bus-launcher and at-spi2-registryd, thus leading to an
> inaccessible desktop.
>
> Lightdm must make sure not to leave behind at-spi-bus-launcher and
> at-spi2-registryd running on the display.
>
Forwarded to
https://bugs.launchpad.net/debian/+source/lightdm/+bug/1366534
--
Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part