Desktop permissions (e.g shutdown, network, users) broken for all accounts after upgrade to 14.10

[Laurens Bosscher]

I reported this bug before as Bug #1372187 but it has been brought to my attention that Ubuntu switched from console-kit to logind after the 13.10 release.

1. System worked without any problems under 14.04
2. Upgrade to 14.10
3. Upgrade went without any problems
4. Notice that standby has disappeared from the "gears" menu
5. notice that I cannot disconnect or change the network connection (exact error is: "(32) Not authorized to control networking.")
6. I can't see, change or unlock setting under Settings > User accounts
7. Running "dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop" from the terminal results in the error: "Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized"
8. Running "sudo pam-auth-update --force" doesn't solve any errors
9. Creating a new user account (sudo adduser) and switching to the account results in the same permission problems.

Output of:

laurens@laurens-desktop:~$ loginctl list-sessions
   SESSION UID USER SEAT
        c1 110 lightdm seat0
        c2 1000 laurens seat0

2 sessions listed.

Sudo works as expected so I can help to further debug this problem and provide relevant information. Unfortunately I have very limited experience with Logind and PAM so I hope I have reported this to the right package.

If someone could point me in the right direction (wiki, man page, tutorial) I would be more than happy to see if I can see what went wrong and if I can debug this myself.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libpam-systemd 208-8ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
Uname: Linux 3.16.0-17-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 5 22:34:02 2014
InstallationDate: Installed on 2013-04-21 (531 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130421)
SourcePackage: systemd
UpgradeStatus: Upgraded to utopic on 2014-09-14 (21 days ago)

[Martin Pitt (pitti)]

> 7. Running "dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop" from the terminal results in the error: "Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized"

That won't work indeed, as ConsoleKit has been dead since Ubuntu 13.10. There the change to logind and libpam_systemd happened, so if it worked under 14.04 I presume that libpam-systemd got configured correctly in /etc/pam.d/common-session. It should have a line like "session optional pam_systemd.so". If not, that's the problem, can you confirm?

Do you have the policykit-desktop-privileges package installed?

[Laurens Bosscher (laurens-laurensbosscher)]

It seems that I have policykit-desktop-privileges installed:

laurens@laurens-desktop:~$ dpkg --list > test.txt
laurens@laurens-desktop:~$ cat test.txt | grep 'policykit-desktop-privileges'
ii policykit-desktop-privileges 0.19 all run common desktop actions without password

I've also checked it in Synaptic and it also showed it as installed.

I've attached my /etc/pam.d/common-session file. It seems that I have the required line. If there's anything else I can do or a debug guide I can follow I'll be happy to spend some time on this.

[Laurens Bosscher (laurens-laurensbosscher)]

I fixed this by removing upstart from my Ubuntu installation. I know it's not the best solution but I finally got a working desktop again :)

I hope this helps in debugging this bug!

[Martin Pitt (pitti)]

Err, you removed upstart? That means that you are running systemd as pid 1? That's not supported yet in 14.10 (although it should work for the desktop for the most part). Please check your current session name in "loginctl" (probably "c2"), and then give me the output of "loginctl show-session c2" (replace "c2" with the actual session). Perhaps there's something wrong with that.

[Martin Pitt (pitti)]

Ping?

[Martin Pitt (pitti)]

No further response in two months, closing. I'll reopen once there is some more information. Thanks!

[Jimmie Butler (jimmiebtlr)]

I believe I'm having the same bug since I upgraded to 14.10.

The only difference in output I've gotten was

loginctl list-sessions

   SESSION UID USER SEAT
        c1 112 lightdm seat0
         1 1000 jimmie seat0
        c2 1000 jimmie seat0

I also gave a try at removing upstart, and it does indeed make the errors go away. (it seems to autoinstall systemd-sysv:amd64 to replace it).

Should I open another bug report, or keep on this one?

[Laurens Bosscher (laurens-laurensbosscher)]

I would like to further diagnose this problem unfortunately my desktop broke down so I can't do any further debugging. Once I have a new PC I'll see if I can recreate this same problem. Until then I can't do anything.