Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session

[Laurent Bigonville]

Le Mon, 12 May 2014 12:02:12 +0200,
Benjamin Menant <benjamin.menant at gmail.com> a écrit :

> Hello Laurent,

Hello,
 
> I upgraded my system and got gdm3:amd64 3.8.4-8.1 installed. After
> reboot, I opened a VC to strace systemd-logind, then I tried to login
> through gdm.
> I attached the log results.

I actually installed a VM during the weekend to test on a pure unstable
installation with and without systemd as PID1, and I cannot reproduce
this :/

Grepping the strace I see the following ENOENT error

access("/var/lib/systemd/linger/Debian-gdm", F_OK) = -1 ENOENT (No such file or directory)
lstat("/run/systemd/system/", 0x7fffe42a8d20) = -1 ENOENT (No such file or directory)
lstat("/run/systemd/system/", 0x7fffe42a8e10) = -1 ENOENT (No such file or directory)
open("/proc/2262/cgroup", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
unlink("/run/systemd/inhibit/1")        = -1 ENOENT (No such file or directory)
unlink("/run/systemd/inhibit/2")        = -1 ENOENT (No such file or directory)
unlink("/run/systemd/inhibit/3")        = -1 ENOENT (No such file or directory)

What is really puzzling me is the "seat" entry in the following line:

gdm3][2892]: pam_systemd(gdm3:session): Asking logind to create session: uid=1000 pid=2892 service=gdm3 type=x11 class=user seat=/org/freedesktop/ConsoleKit/Seat1 vtnr=0 tty= display=:0 remote=no remote_user= remote_host=

I'm a bit out of idea here :/

> 
> Eventually, I got back to 3.8.4-6.
> 
> Bob, are you talking about the Gnome Flashback session? I will give
> it a try next time.
> 
> Pascal, I also successfully tried lightdm. I got your point, and thank
> you very much for your messages.
> However, since GDM3 comes with Gnome 3, I am pretty sure it would be
> comfy for most users to just get GDM3 working & stable without
> installing any other package (even if those packages are better in any
> way; it is not the point).
> Also, I am using the **unstable** distribution, and I knew this
> distribution comes with issues. That’s fine. By the way, I guess my
> humble role as a GNU/Debian user is to report bugs, and give the most
> information I can to Maintainers so they can fix those bugs (or not).
> So, IMHO, running away to install an alternative is not a
> solution. ;-)

Thanks for this.

Cheers!

> 
> Thank you,
> Benjamin.