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?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1377727

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

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  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)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to