Could not get session id for session

[dino99]

A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1).
On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting.

Here are the troubles met at the next cold boot (verbosy mode):

- the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??)

- second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again.

- third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd-shim 7-2
ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
Uname: Linux 3.16.0-12-generic i686
ApportVersion: 2.14.7-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Wed Sep 3 17:15:43 2014
SourcePackage: systemd-shim
UpgradeStatus: No upgrade log present (probably fresh install)

[dino99 (9d9)]

'nouveau' driver is not cleanly loaded, as it usually is

[dino99 (9d9)]

from /var/log/upstart/cups.log :

cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration

auth.log give some more details:

Sep 3 16:59:41 u32 gdm-password][2215]: pam_succeed_if(gdm-password:auth): requirement "user ingroup nopasswdlogin" not met by user "oem"
Sep 3 16:59:49 u32 gdm-password][2215]: pam_unix(gdm-password:session): session opened for user oem by (unknown)(uid=0)
Sep 3 16:59:49 u32 kernel: [ 202.752699] systemd-logind[1125]: Failed to start unit [e-mail]: Unknown unit: [e-mail]
Sep 3 16:59:49 u32 kernel: [ 202.752707] systemd-logind[1125]: Failed to start user service: Unknown unit: [e-mail]
Sep 3 16:59:49 u32 kernel: [ 202.758288] systemd-logind[1125]: New session c2 of user oem.
Sep 3 16:59:49 u32 kernel: [ 202.758310] systemd-logind[1125]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Sep 3 16:59:49 u32 gdm-launch-environment][1680]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Sep 3 16:59:49 u32 kernel: [ 202.985699] systemd-logind[1125]: Failed to abandon scope session-c1.scope
Sep 3 16:59:49 u32 kernel: [ 202.985709] systemd-logind[1125]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope
Sep 3 16:59:49 u32 polkitd(authority=local): Unregistered Authentication Agent for unix-session:c1 (system bus name :1.45, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ) (disconnected from bus)
Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings
Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings
Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
Sep 3 16:59:52 u32 gnome-keyring-daemon[2231]: message repeated 2 times: [ couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files]
Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The Secret Service was already initialized
Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The PKCS#11 component was already initialized
Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The SSH agent was already initialized
Sep 3 16:59:54 u32 gnome-keyring-daemon[2231]: The GPG agent was already initialized
Sep 3 16:59:56 u32 polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.80 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Sep 3 17:01:00 u32 sudo: oem : TTY=pts/7 ; PWD=/home/oem ; USER=root ; COMMAND=/usr/sbin/synaptic
Sep 3 17:01:00 u32 sudo: pam_unix(sudo:session): session opened for user root by oem(uid=0)
Sep 3 17:03:59 u32 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Sep 3 17:03:59 u32 pkexec[2739]: oem: Executing command [USER=root] [TTY=unknown] [CWD=/home/oem] [COMMAND=/usr/lib/update-notifier/package-system-locked]
Sep 3 17:04:21 u32 gno...

[Robert Ancell (robert-ancell)]

Please attach /var/log/lightdm/lightdm.log after a failed boot.

[dino99 (9d9)]

latest lightdm.log before switching to gdm

[Laércio de Sousa (lbssousa)]

Reading your lightdm log, it seems LightDM cannot load seat0 for your case.

Do you have any custom config file under /etc/lightdm/lightdm.conf.d (or /etc/lightdm/lightdm.conf)? Specially, do you set option "start-default-seat=false" explicitly?

[Launchpad Janitor (janitor)]

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

[Elfy (elfy)]

I appear to see the same thing - though in an install I accepted ALL except lightdm update.

This is an Xubuntu install - nothing in lightdm.conf.d/ and no /etc/lightdm/lightdm.conf at all

reported lp:1365336 against lightdm

[dino99 (9d9)]

@lbssousa

as per the initial description: "and its a fresh standard installation using upstart for booting."

so that is, no fancy things except the default ones (seems these 2 packages have not been able the cleanly upgrade, as the system was fine before using these upgrades)

[Martin Pitt (pitti)]

Wile systemd-shim 7-1 → 7-2 is essentially a no-op (i. e. harmless), you really shouldn't have gotten that version automatically yet -- it's still in proposed. Pretty pretty please do *not* run utopic-proposed! It's pretty much guaranteed to break your computer and is not supported. As for the lightdm failure, I just heard from Chris confirming that there's apparently some trouble with last night's version (bug 1365336).

For this, please run "sudo apt-get -f install" to fix a (probably) half-broken installation, and disable -proposed.