[Bug 1206897] Re: logind fails to work, falling back to ConsoleKit when /run/users has wrong permissions

[Robert Ancell]

Turns out this is a bug in ubuntu-touch-session - specifically in
ubuntu-touch-session-setup.conf:

    mkdir -p "$XDG_RUNTIME_DIR"
    chmod 0700 "$XDG_RUNTIME_DIR"
    chown "$uid:$gid" "$XDG_RUNTIME_DIR"

It needs to be 0755, not 0700 for logind to work.

** Summary changed:

- logind fails to work, falling back to ConsoleKit when /run/users already exists
+ logind fails to work, falling back to ConsoleKit when /run/users has wrong permissions

** Package changed: systemd (Ubuntu) => session-manager-touch

-- 
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 has
  wrong permissions

Status in Ubuntu Touch Session management:
  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/session-manager-touch/+bug/1206897/+subscriptions