lightdm user owns several /dev/pts/* devices in 14.04, none in 13.10

Bug #1304640 reported by Jamie Strandboge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

On a fresh boot in 14.04 and sitting at the greeter, various /dev/pts devices are open, but in 13.10 and ealier they are not. I'm not sure if this is a problem, but it seems odd and worth understanding why it is happening. Ie:

ubuntu@test-trusty-desktop:~$ dpkg -l|grep greeter
ii unity-greeter 14.04.9-0ubuntu1 amd64 Unity Greeter

ubuntu@test-trusty-desktop:~$ dpkg -l|grep lightdm
ii liblightdm-gobject-1-0 1.10.0-0ubuntu1 amd64 LightDM GObject client library
ii lightdm 1.10.0-0ubuntu1 amd64 Display Manager

ubuntu@test-trusty-desktop:~$ ls -l /dev/pts/*|grep lightdm
crw--w---- 1 lightdm tty 136, 10 Apr 8 14:56 /dev/pts/10
crw--w---- 1 lightdm tty 136, 11 Apr 8 14:56 /dev/pts/11
crw--w---- 1 lightdm tty 136, 12 Apr 8 14:56 /dev/pts/12
crw--w---- 1 lightdm tty 136, 4 Apr 8 14:56 /dev/pts/4
crw--w---- 1 lightdm tty 136, 6 Apr 8 14:56 /dev/pts/6

ubuntu@test-trusty-desktop:~$ loginctl
   SESSION UID USER SEAT
        c1 112 lightdm seat0
         1 1000 ubuntu

2 sessions listed.
ubuntu@test-trusty-desktop:~$ loginctl session-status c1
c1 - lightdm (112)
           Since: Tue 2014-04-08 14:56:55 CDT; 2min 28s ago
          Leader: 1667 (lightdm)
            Seat: seat0; vc7
         Display: :0
         Service: lightdm-greeter; type x11; class greeter
           State: active
          CGroup: systemd:/user/112.user/c1.session
                  ├─1667 lightdm --session-child 16 19
                  ├─1684 /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/sbi...
                  ├─1695 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 ...
                  ├─1700 /usr/sbin/unity-greeter
                  ├─1728 /usr/lib/at-spi2-core/at-spi-bus-launcher --launch-immedi...
                  ├─1732 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility...
                  ├─1735 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-sessi...
                  ├─1740 /usr/lib/gvfs/gvfsd
                  ├─1755 /usr/lib/gvfs/gvfsd-fuse /run/user/112/gvfs -f -o big_wri...
                  ├─1766 /usr/lib/dconf/dconf-service
                  ├─1798 init --user --startup-event indicator-services-start
                  ├─1800 nm-applet
                  ├─1802 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-b...
                  ├─1804 /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power...
                  ├─1806 /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-da...
                  ├─1808 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound...
                  ├─1816 /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --us...
                  ├─1819 /usr/lib/x86_64-linux-gnu/indicator-session/indicator-ses...
                  ├─1830 /usr/lib/unity-settings-daemon/unity-settings-daemon
                  ├─1867 /usr/bin/pulseaudio --start --log-target=syslog
                  ├─1901 /usr/lib/x86_64-linux-gnu/notify-osd
                  └─2023 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2

ubuntu@test-trusty-desktop:~$ for i in 10 11 12 4 6 ; do sudo lsof |grep "/dev/pts/$i$" ; done
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/112/gvfs
      Output information may be incomplete.
indicator 1806 lightdm 1u CHR 136,10 0t0 13 /dev/pts/10
indicator 1806 lightdm 2u CHR 136,10 0t0 13 /dev/pts/10
dconf 1806 1832 lightdm 1u CHR 136,10 0t0 13 /dev/pts/10
dconf 1806 1832 lightdm 2u CHR 136,10 0t0 13 /dev/pts/10
gmain 1806 1833 lightdm 1u CHR 136,10 0t0 13 /dev/pts/10
gmain 1806 1833 lightdm 2u CHR 136,10 0t0 13 /dev/pts/10
gdbus 1806 1840 lightdm 1u CHR 136,10 0t0 13 /dev/pts/10
gdbus 1806 1840 lightdm 2u CHR 136,10 0t0 13 /dev/pts/10
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/112/gvfs
      Output information may be incomplete.
indicator 1808 lightdm 1u CHR 136,11 0t0 14 /dev/pts/11
indicator 1808 lightdm 2u CHR 136,11 0t0 14 /dev/pts/11
gdbus 1808 1849 lightdm 1u CHR 136,11 0t0 14 /dev/pts/11
gdbus 1808 1849 lightdm 2u CHR 136,11 0t0 14 /dev/pts/11
dconf 1808 1851 lightdm 1u CHR 136,11 0t0 14 /dev/pts/11
dconf 1808 1851 lightdm 2u CHR 136,11 0t0 14 /dev/pts/11
gmain 1808 1970 lightdm 1u CHR 136,11 0t0 14 /dev/pts/11
gmain 1808 1970 lightdm 2u CHR 136,11 0t0 14 /dev/pts/11
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/112/gvfs
      Output information may be incomplete.
indicator 1819 lightdm 1u CHR 136,12 0t0 15 /dev/pts/12
indicator 1819 lightdm 2u CHR 136,12 0t0 15 /dev/pts/12
dconf 1819 1831 lightdm 1u CHR 136,12 0t0 15 /dev/pts/12
dconf 1819 1831 lightdm 2u CHR 136,12 0t0 15 /dev/pts/12
gdbus 1819 1844 lightdm 1u CHR 136,12 0t0 15 /dev/pts/12
gdbus 1819 1844 lightdm 2u CHR 136,12 0t0 15 /dev/pts/12
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/112/gvfs
      Output information may be incomplete.
indicator 1802 lightdm 1u CHR 136,4 0t0 7 /dev/pts/4
indicator 1802 lightdm 2u CHR 136,4 0t0 7 /dev/pts/4
gdbus 1802 1805 lightdm 1u CHR 136,4 0t0 7 /dev/pts/4
gdbus 1802 1805 lightdm 2u CHR 136,4 0t0 7 /dev/pts/4
dconf 1802 1812 lightdm 1u CHR 136,4 0t0 7 /dev/pts/4
dconf 1802 1812 lightdm 2u CHR 136,4 0t0 7 /dev/pts/4
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/112/gvfs
      Output information may be incomplete.
indicator 1804 lightdm 1u CHR 136,6 0t0 9 /dev/pts/6
indicator 1804 lightdm 2u CHR 136,6 0t0 9 /dev/pts/6
gdbus 1804 1809 lightdm 1u CHR 136,6 0t0 9 /dev/pts/6
gdbus 1804 1809 lightdm 2u CHR 136,6 0t0 9 /dev/pts/6
dconf 1804 1811 lightdm 1u CHR 136,6 0t0 9 /dev/pts/6
dconf 1804 1811 lightdm 2u CHR 136,6 0t0 9 /dev/pts/6

description: updated
summary: - lightdm owns several /dev/pts/* devices in 14.04, none in 13.10
+ lightdm user owns several /dev/pts/* devices in 14.04, none in 13.10
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.