Ubuntu
lightdm package

lightdm gets confused after multiple login/logouts

Bug #1248948 reported by b3nmore
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Got this on xubuntu 13.10:
When I logout and login again and start gdmflexiserver (or any other dbus call to displaymanager), the screen turns black with the mouse cursor still visible. The session is still running since I can terminate it by executing 'blindly' the normal logout process.

A fishy side aspect: When i switch to ttyX via ctrl+alt+fX and login, the username AND password is also written to .bash_history of the user with the crippled X-session(if he left a shell open with focus). So you might want consider this as a security issue.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-27 (11 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
LightdmConfig:
 [SeatDefaults]
 greeter-session=lightdm-gtk-greeter
 user-session=xubuntu
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1002): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/sessions': No such file or directory

 ** (lightdm-gtk-greeter:1002): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory

 ** (lightdm-gtk-greeter:1002): WARNING **: Failed to load user image: Failed to open file '/home/kiran/.face': No such file or directory
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:2580): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/sessions': No such file or directory

 ** (lightdm-gtk-greeter:2580): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory

 ** (lightdm-gtk-greeter:2580): WARNING **: Failed to load user image: Failed to open file '/home/kiran/.face': No such file or directory
MarkForUpload: True
Package: lightdm 1.8.4-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Tags: saucy third-party-packages
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

See original description
Revision history for this message
Quinn Balazs (qbalazs) wrote :

Please run "apport-collect 1248948" in order to fetch the necessary logs. After that has been done, mark this as new and someone will take a look at it.

Changed in lightdm (Ubuntu):
status: New → Incomplete
Revision history for this message
b3nmore (b3nmore) wrote : Dependencies.txt

apport information

tags: added: apport-collected saucy third-party-packages
description: updated
Revision history for this message
b3nmore (b3nmore) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
b3nmore (b3nmore) wrote : LightdmLog.txt

apport information

Revision history for this message
b3nmore (b3nmore) wrote : LightdmUsersConfig.txt

apport information

Revision history for this message
b3nmore (b3nmore) wrote : ProcEnviron.txt

apport information

Changed in lightdm (Ubuntu):
status: Incomplete → New
Revision history for this message
b3nmore (b3nmore) wrote :

It seems lightdm tries to open the new session at vt7 (where the orignal xsession is already running) instead of a vt8 (or whatever is unused). It partially succeeds, resulting is this weird state, where parts of both, original xsession and lightdm, are displayed and input is shared.

Revision history for this message
b3nmore (b3nmore) wrote :

From the crash file:
ProcCmdline: /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch

Starting a xserver with vt7, when there is already a xsession running on vt7 is a bad idea. Should this be even possible at all? Anyway, I think we should make sure, that either lightdm starts X with a correct vt-number or let X choose a vt number.

Revision history for this message
b3nmore (b3nmore) wrote :

First login after a fresh (re)start of lightdm, gdmflexiserver results in following X calls:
2330 /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
2587 /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch

After logout and login I get:
5268 /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
5726 /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Sean (scott-seanc) wrote :

Installing the 14.04 development version (1.9.7) in 13.10 resolved to issue for me. I've been free of it for one week now.

Revision history for this message
Sean (scott-seanc) wrote :

Possible duplicate of 1256150 (not really dup since this one is older). Propsed fix in 1256150.

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

I think you're right, this is the same bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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