Ubuntu 12.04 session don't open with lightdm

[GuyR]

Ubuntu 12.04 Beta1

lightdm 1.1.7-0ubuntu1

After ugraded from Oneiric to Pangolin 12.04 beta1 the session don't open with lightdm, it autoclose and goes back to lightdm login screen. here are some log

[+75.89s] DEBUG: Greeter start authentication for guy

[+75.89s] DEBUG: Started session 4115 with service 'lightdm', username 'guy'

[+75.92s] DEBUG: Session 4115 got 1 message(s) from PAM

[+75.92s] DEBUG: Prompt greeter with 1 message(s)

[+101.80s] DEBUG: Continue authentication

[+101.83s] DEBUG: Session 4115 authentication complete with return value 0: Success

[+101.83s] DEBUG: Authenticate result for user guy: Success

[+101.84s] DEBUG: User guy authorized

[+101.84s] DEBUG: Greeter requests session gnome-classic

[+101.84s] DEBUG: Using session gnome-classic

[+101.84s] DEBUG: Stopping greeter

[+101.84s] DEBUG: Session 4046: Sending SIGTERM

[+101.93s] DEBUG: Session 4046 exited with return value 0

[+101.93s] DEBUG: Greeter quit

[+102.00s] DEBUG: Dropping privileges to uid 1000

[+102.00s] DEBUG: Restoring privileges

[+102.01s] DEBUG: Dropping privileges to uid 1000

[+102.01s] DEBUG: Writing /home/guy/.dmrc

[+102.04s] DEBUG: Restoring privileges

[+102.08s] DEBUG: Starting session gnome-classic as user guy

[+102.08s] DEBUG: Session 4115 running command /usr/sbin/lightdm-session gnome-session --session=gnome-classic

[+102.12s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session2

[+102.12s] DEBUG: Greeter closed communication channel

[+102.13s] DEBUG: Session 4115 exited with return value 1

[+102.13s] DEBUG: User session quit

[+102.13s] DEBUG: Stopping display

[+102.13s] DEBUG: Sending signal 15 to process 4043

[+102.22s] DEBUG: Process 4043 exited with return value 0

[+102.22s] DEBUG: X server stopped

[+102.22s] DEBUG: Removing X server authority /var/run/lightdm/root/:0

[+102.22s] DEBUG: Releasing VT 7

[+102.22s] DEBUG: Display server stopped

[+102.22s] DEBUG: Display stopped

[+102.22s] DEBUG: Active display stopped, switching to greeter

[+102.22s] DEBUG: Switching to greeter

[+102.22s] DEBUG: Starting new display for greeter

[+102.22s] DEBUG: Starting local X display

[+102.22s] DEBUG: Using VT 7

[+102.22s] DEBUG: Logging to /var/log/lightdm/x-0.log

[+102.22s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0

[+102.23s] DEBUG: Launching X Server

[+102.23s] DEBUG: Launching process 5421: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

[+102.23s] DEBUG: Waiting for ready signal from X server :0

[+102.54s] DEBUG: Got signal 10 from process 5421

[+102.54s] DEBUG: Got signal from X server :0

[+102.54s] DEBUG: Connecting to XServer :0

[+102.54s] DEBUG: Starting greeter

[+102.54s] DEBUG: Started session 5424 with service 'lightdm', username 'lightdm'

[+102.59s] DEBUG: Session 5424 authentication complete with return value 0: Success

[+102.59s] DEBUG: Greeter authorized

[+102.62s] DEBUG: Launching process 5436: /usr/bin/numlockx on

[+102.62s] DEBUG: Process 5436 exited with return value 0

[+102.62s] DEBUG: Exit status of /usr/bin/numlockx on: 0

[+102.62s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log

[+102.63s] DEBUG: Session 5424 running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter

[+102.90s] DEBUG: Greeter connected version=1.1.7

[+102.90s] DEBUG: Greeter connected, display is ready

[+102.90s] DEBUG: New display ready, switching to it

[+102.90s] DEBUG: Activating VT 7

[+102.90s] DEBUG: Stopping greeter display being switched from

[+103.91s] DEBUG: Greeter start authentication for guy

[+103.91s] DEBUG: Started session 5494 with service 'lightdm', username 'guy'

[+103.93s] DEBUG: Session 5494 got 1 message(s) from PAM

[+103.93s] DEBUG: Prompt greeter with 1 message(s)

[+230.27s] DEBUG: Session 5424 exited with return value 9

[+230.27s] DEBUG: Greeter quit

[+230.27s] DEBUG: Failed to start greeter

[+230.27s] DEBUG: Stopping display

[+230.27s] DEBUG: Sending signal 15 to process 5421

[+230.29s] DEBUG: Process 5421 exited with return value 0

[+230.29s] DEBUG: X server stopped

[+230.29s] DEBUG: Removing X server authority /var/run/lightdm/root/:0

[+230.29s] DEBUG: Releasing VT 7

[+230.29s] DEBUG: Display server stopped

[+230.29s] DEBUG: Display stopped

[+230.29s] DEBUG: Active display stopped, switching to greeter

[+230.29s] DEBUG: Switching to greeter

[+230.29s] DEBUG: Starting new display for greeter

[+230.29s] DEBUG: Starting local X display

[+230.29s] DEBUG: Using VT 7

[+230.29s] DEBUG: Logging to /var/log/lightdm/x-0.log

[+230.29s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0

[+230.29s] DEBUG: Launching X Server

[+230.29s] DEBUG: Launching process 9103: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

[+230.29s] DEBUG: Waiting for ready signal from X server :0

[+230.62s] DEBUG: Got signal 10 from process 9103

[+230.62s] DEBUG: Got signal from X server :0

[+230.62s] DEBUG: Connecting to XServer :0

[+230.62s] DEBUG: Starting greeter

[+230.62s] DEBUG: Started session 9108 with service 'lightdm', username 'lightdm'

[+230.62s] DEBUG: Greeter closed communication channel

[+230.62s] DEBUG: Session 9108 exited with return value 1

[+230.62s] DEBUG: Session 9108 failed during authentication

[+230.62s] DEBUG: Greeter failed authentication

[+230.62s] DEBUG: Greeter failed to start

[+230.62s] DEBUG: Stopping display

[+230.62s] DEBUG: Sending signal 15 to process 9103

[+230.71s] DEBUG: Process 9103 exited with return value 0

[+230.71s] DEBUG: X server stopped

[+230.71s] DEBUG: Removing X server authority /var/run/lightdm/root/:0

[+230.71s] DEBUG: Releasing VT 7

[+230.71s] DEBUG: Display server stopped

[+230.71s] DEBUG: Display stopped

[+230.71s] DEBUG: Stopping X local seat, failed to start a display

[+230.71s] DEBUG: Stopping seat

[+230.71s] DEBUG: Seat stopped

[+230.71s] DEBUG: Required seat has stopped

[+230.71s] DEBUG: Stopping display manager

[+230.71s] DEBUG: Display manager stopped

[+230.71s] DEBUG: Stopping daemon

[+230.71s] DEBUG: Exiting with return value 1

If I use gdm I can open session after a freeze of almost 40 secondes with the totally pink picture.

[Sebastien Bacher (seb128)]

Thank you for your bug report, can you try to log in, then go to a vt (ctrl-alt-f1), copy ~/.xsession-errors and add it to the bug?

[GuyR (guy-rouger)]

Hello Sebastien,

[GuyR (guy-rouger)]

Hello Sebastien,
Please could you give me the trick to use gdm once I am in vt terminal?
I modify the /etc/X11/default-display-manager using vim to write gdm, kill the process lightdm but it always come back to lightdm login.
Finally I sudo apt-get remove lighdm, then I can use gdm , wich I am using to write this, but this not very useful :)
I attache the error file when I use gdm as there is a freeze of almost 40 secondes before having the desktop
Best regards
Guy

[GuyR (guy-rouger)]

Hello
Have a look on this
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/951429

[GuyR (guy-rouger)]

Hello
Bellow the error when I use an other user whixh is not the admin.
It can login with lightdm with errors.

[GuyR (guy-rouger)]

Bingo,
Once I downgrade lightdm package to Oneiric version http://security.ubuntu.com/ubuntu/pool/main/l/lightdm/lightdm_1.0.6-0ubuntu1.4_i386.deb
all things are ok

[Sebastien Bacher (seb128)]

it seems like xorg is closing under the session, could you add your /var/log/syslog, Xorg.0.log, Xorg.0.log.old to the bug?

[Sebastien Bacher (seb128)]

The issue is specific to your user then? the bug seems a bit similar to bug #944736...

[Sebastien Bacher (seb128)]

bug #951794, bug #952149 and bug #951429 are similar, it's a bit weird, those users have the issue with their account and not other accounts on the same box and the .xsession-errors behaves like if gnome-session or xorg was closing...

[GuyR (guy-rouger)]

HELLO,
Now I comeback to 1.1.7-0ubuntu1 and after some cleaning in ~/.config/autostart and
ubuntu-desktop:/etc/xdg/autostart$ sudo rm gsettings-data-convert.desktop
I can login after having a very bad picture with a lot of zebra.

[Sebastien Bacher (seb128)]

the syslog log lists gdm processes so I guess it's not from a failed session login but from a working one with gdm? did you keep your ~/.config/autostart to see if restoring it brings back the issue? I wonder if something makes gnome-session bug...

[GuyR (guy-rouger)]

No I totally delete the files, it remains this:

guy@ubuntu-desktop:~/.config/autostart$ ls
gdu-notification-daemon.desktop gnome-user-share.desktop
gnome-power-manager.desktop indicator-weather.desktop

Attached the syslog of the last login using lightdm

[Lucazade (lucazade)]

is there any news on this bug?
is this related to "Fatal IO error 11 on X server :0." present in .xsession-errors?

[DFOXpro (dfoxpro)]

May be this bug have a relation with https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/964607

[Sebastien Bacher (seb128)]

does login into a guest session work? could you try to move your user .config to see if that makes a difference?

[GuyR (guy-rouger)]

Hello,
For the moment I can't use lightdm. The screen is blinking and so I can't login.
This occurs as of updates from march 27th.
http://forum.ubuntu-fr.org/viewtopic.php?id=862431
when switch to gdm I can login and a crash in unity-greeter is displayer. I report the bug
https://bugs.launchpad.net/bugs/966362
So now I remain in gdm waiting for fix.

[GuyR (guy-rouger)]

Hello
It is going worse
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/969589

[Sebastien Bacher (seb128)]

GuyR, the bug you pointed is a different one, it was a unity-greeter issue and has been fixed with a recent update ... could somebody having the issue still respond to my previous comment? is that specific to an user?

[Sebastien Bacher (seb128)]

Who need somebody having the issue to move forward, useful infos would be to reply to those question:

- does starting a guest session with unity-3d works?
- does start a non unity session with your user work?
- could you rm .xsession-errors for you user, logout, try to log in, get the bug, go to a vt and copy .xsession-errors, then attach it to the bug?

[Gene Hilton (genehilton)]

I'm not sure if this is the same bug, but neither lightdm or gdm will start a session for me. For both lightdm and gdm with any kind of session (unity, unity2d, classic, xfce ...) the gui dies and flashes what was on console 7 and then restarts. My only way in is console 1 text login, stopping lightdm and running startx.

It happened about not quite 2 weeks ago - I am running 12.04 beta. I had hoped the 12.04 release would fix it but no dice.

The .xsession-errors follows but isn't particularly enlightening

No protocol specified
No protocol specified
xrdb: Resource temporarily unavailable
xrdb: Can't open display ':0'
No protocol specified
No protocol specified
xrdb: Resource temporarily unavailable
xrdb: Can't open display ':0'
No protocol specified
No protocol specified
xhost: unable to open display ":0"
No protocol specified
No protocol specified
xhost: unable to open display ":0"
openConnection: connect: No such file or directory
cannot connect to brltty at :0
No protocol specified
No protocol specified
No protocol specified
No protocol specified

** (gnome-session:5675): WARNING **: Cannot open display:

[Richard Sellam (richard-sellam)]

I had the same bug. Well, at least the same symptoms: being able to log in with gdm, but lightdm giving a black screen for a few seconds, then autoclosing and going back to the login screen, whatever the session selected in lightdm.

Trying to investigate, i looked into .xsession-errors but it was empty so not giving any clue. I'd suggest to look at /var/log/lightdm/.
It appears my /etc/lightdm/lightdm.conf had some troublesome entries (like session-setup-script=...) which would cause lightdm to crash without telling why.
Restoring default /etc/lightdm/lightdm.conf fixed it for me.

bug in #23 ( https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/951404/comments/23 ) looks totally different, and it would be better to open another bug report for this one.

[Gene Hilton (genehilton)]

I am also not convinced this is the same bug. I bet this machine has been upgraded one time too many and has some horrible cruft somewhere. The workaround for now is kdm - all session types seem to work fine.

[MarcoBertolini (bertolini)]

I am experiencing the same bug with lightdm 1.2.1-0ubuntu1.
I can login with another user and with the guest user. Tried to purge lightdm and reinstall, but didn't work. Most likely there is some configuration filer in my home that cuase lightdm to crash. Workaround is to use gdm.
I am not posting logs as they look pretty much the same as the ones already posted

[Sebastien Bacher (seb128)]

the bug described original there seems to have been resolved and the ticket is getting confusing mixing other issues, could the users who still have some issues open a new report using this command: ubuntu-bug lightdm

[GReboute (linux-dr-z)]

I had the same bug.
Tried disabling /etc/xdg/autostart/gsettings-data-convert.desktop as in https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/951429/comments/3
with no success.

I noticed my ~/.xsession-errors didn't changed for few days. Tried with rm, no new file.
I wrote down my home dir permission, changed my whole $HOME with chmod 777 $HOME/ (not recursive)

Tried to log with X session, ....tadam ! It worked !
I rechanged my $HOME permission back - all seems to be OK for now on.

I suspected a process running outside my user and trying to write to my home.

[A.RICHARD (1-contactmonsieur-floss)]

I'd like to share a 3 hours hint success here, because I used the keywords "ubuntu logout bug" and went through here during my search.

But my answer was here: ".Xauthority sometimes owned by root, which blocks login"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/871667/comments/30

[\|Bruce L (fq-bruce-x0)]

I experienced this problem under saucy. lightdm behaves badly (No login session option, kicks back to lightdm when logging into unity, etc.) No useful help in the log files. chown'ing .Xauthority did the trick. Thanks A. Richard.