[Bug 1206897] Re: logind fails to work, falling back to ConsoleKit when /run/users already exists

[Martin Pitt]

That reminds me of a bug that Iain reported this morning and a while
ago: For him, sometimes /run/user/1000/pulse has root:root permissions
instead of being owned by Iain, but for him /run/user/1000 itself (and
all other directories) are correct. I really don't see what else other
than pulseaudio itself would handle/create/touch that directory. My
suspicion is that at some point in time pulseaudio must have been
running as root in the new session. Could that perhaps be a race
condition of some sort in lightdm that it drops root privileges too
late?

NB that this is pure speculation, and the two issues might not even be
related. I'm just bringing it up here as that's the second issue of
runtime dir permissions apparently being wrong.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1206897

Title:
  logind fails to work, falling back to ConsoleKit when /run/users
  already exists

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  When testing Mir I've found a case where logind fails and this causes
  the user to lose access the hardware accelerated rendering. The cause
  is (for some unknown reason) /run/user exists and logind aborts when
  trying to open a session.

  From /var/log/auth.log:

  Jul 31 13:25:07 alchemy lightdm: pam_unix(lightdm:session): session opened for user bob by (uid=0)
  Jul 31 13:25:07 alchemy systemd-logind[725]: Failed to create /run/user: File exists
  Jul 31 13:25:07 alchemy lightdm: pam_systemd(lightdm:session): Failed to create session: File exists

  When this first occurred it would persist between reboots and went
  away eventually (don't know if I did anything to cause that).

  The second time it occurred I did:
  $ sudo stop lightdm
  $ sudo umount /run/user
  $ sudo rmdir /run/user
  $ sudo start lightdm

  and this fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1206897/+subscriptions