Not able to use updater: "You are not allowed to perform this action"

Could you add the output of the command id run in a terminal?

I am no longer finding this error.

sudo update-manager seems to run correctly.

Facing this issue after upgrade from 13.04 to 13.10

I am getting this issue after I upgraded from 13.04 to 13.10
Software Updater:
"[BOLD]You are not allowed to perform this action[/BOLD]
You don't have the required privileges to perform this action"

Also I am not able to shutdown/reboot from the menu. I have to run "sudo poweroff" or "sudo reboot" then only I can able to do.
All these issues starts after I upgraded to 13.10 only before no issues.

jj@jjux64:~$ id
uid=1000(jj) gid=1000(jj) groups=1000(jj),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),104(fuse),109(lpadmin),119(pulse),120(pulse-access),124(sambashare),130(vboxusers),131(nm-openconnect)

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

I have the same issue with the software updater after upgrading to 13.10

/home/rziemba$id
uid=1000(rziemba) gid=1000(rziemba) groups=1000(rziemba),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lpadmin),114(netdev),123(sambashare)

I realized that I was missing policykit-1-gnome. Installing this program solved my problems with update-manager.

I'm getting this exact same issue on Trusty after running a partial upgrade today, rebooting, and trying to run Software Updater from the Unity dash.

I got this issiue after running a partial upgrade today.

This has happened to me too, just as Christopher experienced: "after running a partial upgrade, rebooting, and trying to run Software Updater from the Unity dash".

Yep, happened to me as well after running a partial upgrade for Trusty. The software updater gives me the message, the Dash is slow and I'm unable to shutdown or reboot without using the terminal .

Heyyo, I'm getting the same problem. Ubuntu 14.04 64bit on Trusted Main.

It's even worse! I couldn't mount a USB after the update today due to the a USB driver!

And the CPU usage is very HIGH!

I downloaded the daily build of Ubuntu 14.04 and made a fresh installation, updated to everything latest, reboot and got the exactly same problems as I mentioned before!!!!!!!!!!!!!!!!!!!!!!

I already had policykit-1-gnome and reinstalling it didn't help.

I also ran into this after a partial upgrade of a 14.04 system today. I've seen this before on a different machine after upgrading to 13.10, but in that case 'sudo pam-auth-update --force' fixed the problem. This time that doesn't help.

I'm in the same boat. I thought I had broken it myself but thankfully this might get enough attention to be fixed quick. :( This has been the only serious issue I've encountered with 14.04.
I can't say I have much to contribute, but it's good to not be alone in this.

Also, can anyone else confirm the fact that the audio has stopped working as well?

Same issue happened to me today after a partial upgrade on 14.04. Video performance is very poor, no transparency in the dash, no sound, unable to run the update manager due to insufficient rights, unable to shutdown.

I confirm the problems after a partial upgrate
Ubuntu Release: 14.04
Problems:
 - Update manager do not work : "You are not allowed to perform this action"
- Audio do not work
- Shutdown/reboot not possible from GUI
- VPN and Network Config edit NOT Possible
- Even other root actions are not allowed from GUI

Regards
P.

Tring to install new software i have this error:

Software can't be installed or removed because the authentication service is not available. (org.freedesktop.PolicyKit.Error.Failed: ('system-bus-name', {'name': ':1.199'}): org.debian.apt.install-or-remove-packages

exact same error after a partial upgrade on Trusty

Partial upgrades end up getting logged as distribution upgrades so log files pertaining to the upgrade will be located in /var/log/dist-upgrade/. It'd be helpful if people who have experienced this were to upload those log files as soon as possible (i.e. before another partial upgrade happens). Thanks!

I'll gladly upload mine.

I'm also unable to install software from the Ubuntu Software Center. Not sure if that is caused by the same problem as this. Attached is a screenshot showing the exact error message.

By the ways, sudo apt-get install/update/upgrade in the terminal still work just fine as a workaround.

The symptoms are all over the place.
Can't get elevated privliges in GUI applications, can't mount other drives/partitions, no shutting down from the GUI prompts. Then other issues like audio not working at all, and the fact that Compiz has gone somewhat berzerk. It's using 270MB of memory, and tears through my CPU at the slightest action.

After todays update, most of my problems have gone away, thankfully.
However, I'm still getting some warning messages on bootup. When I click on the report button, nothing happens. I had this issue in previous releases, but not in 14.04 until now.

All of my issues have now been resolved after updating from the terminal.

Same as in comment #34. I'm no longer affected.

With latest updates, I am OK again.

All fixed after latest updates via terminal.

It has a severe impact on a large portion of Ubuntu users.

A /var/log/apt/history.log file from a affected system would be really helpful.

I can reproduce the issue here if I remove the package "policykit-1-gnome".

This bug was fixed in the package update-manager - 1:0.196.10

---------------
update-manager (1:0.196.10) trusty; urgency=low

  * debian/control:
    - add dependencies to the various policykit agents to ensure
      that update-manager is not run without policykit agent support
      in the session (LP: #1164558)
  * tests/test_update_list.py:
    - test improvements from Barry Warsaw (many thanks!)
 -- Michael Vogt <email address hidden> Mon, 07 Apr 2014 15:23:05 +0200

I am running version 1:0.196.12, and I had the bug from this afternoon only. I upgraded from 13.10 two weeks ago. I did not do any partial upgrades, and "policykit-1-gnome" is installed.
Is this a new bug?