update-manager crashed with SystemExit in exit(): 0

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

Also happened after system boot

No, it don't even start at boootup.

Same for x64 Arch kernel 3.10.0-6-generic
---------------------------------------------------------------------
ERROR:root:Could not find any typelib for Dbusmenu
ERROR:root:Could not find any typelib for Unity
WARNING:root:can not import unity GI cannot import name Dbusmenu
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 92, in commit
    _("Installing updates…"), True)
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 159, in _show_transaction
    yield trans.run()
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 103, in commit
    error_string=None, error_desc=None)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py", line 72, in _action_done
    self.window_main.exit()
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 182, in exit
    sys.exit(0)
SystemExit: 0
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/aptdaemon/gtk3widgets.py", line 522, in _on_download_changed
    iter = self._download_map[uri]ERROR:root:Could not find any typelib for Dbusmenu
ERROR:root:Could not find any typelib for Unity
WARNING:root:can not import unity GI cannot import name Dbusmenu
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 92, in commit
    _("Installing updates…"), True)
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 159, in _show_transaction
    yield trans.run()
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 103, in commit
    error_string=None, error_desc=None)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py", line 72, in _action_done
    self.window_main.exit()
  File "/usr/lib/python...

I recreated this on a freshly installed Saucy system and look at /var/log/apt/term.log and /var/log/apt/history.log the installation process seems to have finished although there is still an update-manager process and an aptd process running. There is also a defunct [debconf-communi] process.

I ran 'aptd -d' and experienced the crash in bug 450662 which then killed? / stopped the aptd process. Then running update-manager again I received a "The computer needs to restart" dialog.

Here is my apt history.log entry for the time when the crash occurred.

Start-Date: 2013-08-15 07:46:54
Commandline: aptdaemon role='role-commit-packages' sender=':1.68'
Install: linux-headers-3.11.0-2:amd64 (3.11.0-2.5), linux-headers-3.11.0-2-generic:amd64 (3.11.0-2.5), linux-image-3.11.0-2-generic:amd64 (3.11.0-2.5), linux-image-extra-3.11.0-2-generic:amd64 (3.11.0-2.5)
Upgrade: hplip:amd64 (3.13.4-1build1, 3.13.8-0ubuntu1), libfontembed1:amd64 (1.0.34-3ubuntu1, 1.0.36-0ubuntu2), unity-greeter:amd64 (13.10.1- 0ubuntu4, 13.10.2-0ubuntu1), linux-headers-generic:amd64 (3.11.0.1.2, 3.11.0.2.3), libegl1-mesa:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), cups-server-common:amd64 (1.6.3-1, 1.6.3-1ubuntu2), libopenvg1-mesa:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), libqt5sql5-sqlite:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0. 2+dfsg1-7ubuntu8), libegl1-mesa-drivers:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), libsane-hpaio:amd64 (3.13.4-1build1, 3.13.8-0ubuntu1), libqt5opengl5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), whoopsie:amd64 (0.2.20, 0.2.22), at-spi2-core:amd64 (2.9.4-1ubuntu3, 2.9.5- 1ubuntu1), libgl1-mesa-dri:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), unity:amd64 (7.1.0+13.10.20130812.1-0ubuntu1, 7.1.0+13.10.20130813.1-0ubuntu1), libcups2:amd64 (1.6.3-1, 1.6.3-1ubuntu2), cups-daemon:amd64 (1.6.3-1, 1.6.3-1ubuntu2), ubuntu-mono:amd64 (13.04+13.10.20130807-0ubuntu1, 13.04+13. 10.20130812-0ubuntu1), libunity-core-6.0-7:amd64 (7.1.0+13.10.20130812.1-0ubuntu1, 7.1.0+13.10.20130813.1-0ubuntu1), libhpmud0:amd64 (3.13.4- 1build1, 3.13.8-0ubuntu1), libqt5sql5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), libcupsmime1:amd64 (1.6.3-1, 1.6.3-1ubuntu2), cups-client:amd64 (1.6.3-1, 1.6.3-1ubuntu2), libcupsimage2:amd64 (1.6.3-1, 1.6.3-1ubuntu2), libido3-0.1-0:amd64 (13.10.0+13.10.20130731-0ubuntu1, 13.10.0+13.10.20130814-0ubuntu1), landscape-client-ui-install:amd64 (12.12-0ubuntu3, 13.07.1-0ubuntu2), xserver-xorg-core:amd64 (1.14.2-0ubuntu9, 1.14.2.901- 2ubuntu1), libglapi-mesa:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), cups:amd64 (1.6.3-1, 1.6.3-1ubuntu2), libqt5core5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), libgutenprint2:amd64 (5.2.9-1ubuntu1, 5.2.9-1ubuntu2), unity-services:amd64 (7.1.0+13.10.20130812.1-0ubuntu1, 7.1.0+13.10. 20130813.1-0ubuntu1), ubuntu-artwork:amd64 (13.04+13.10.20130807-0ubuntu1, 13.04+13.10.20130812-0ubuntu1), printer-driver-postscript-hp:amd64 (3.13.4-1build1, 3.13.8-0ubuntu1), libimobiledevice4:amd64 (1.1.5-0ubuntu1, 1.1.5-0ubuntu2), xserver-common:amd64 (1.14.2-0ubuntu9, 1.14.2.901-2ubuntu1), libsndfile1:amd64 (1.0.25-7, 1.0.25-7ubuntu1), libwhoopsie0:amd64 (0.2.20, 0.2.22), libqt5xml5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), libatk-bridge2.0-0:amd64 (2.9.4-1ubuntu1, 2.9.5-1), cups-browsed:amd64 (1.0.34-3ubuntu1, 1.0.36-0ubuntu2), libgl1-mesa-glx:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), libqt5test5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), printer-driver-gutenprint:amd64 (5.2.9-1ubuntu1, 5.2.9-1ubuntu2), libxatracker1:amd64 (9.1.4-0ubuntu8, 9.1.6-2ubuntu2), libqt5printsupport5:amd64 (5.0.2+dfsg1-7ubuntu7, 5.0.2+dfsg1-7ubuntu8), gir1.2-atspi-2.0: amd64 (2.9....

It was a small update that quit.

Update manager quit {for some reason" in the Razor desktop> Aptitude update/dist-upgrade showed no updates (could this be a factor?)

Yes, it showed some and I have installed these via Aptitude.

Update-manager can crash with this error if the authorization dialogue times out or you enter three times the false password

I have always typed the right Password. This can't be possible.

It crashes with this error message when the conditions that I described occur. I have never said that it can also crash with the condition that you describe!

edit: can't

my system just flashed out. then after few seconds ..... the error !

Pretty much as above. I try to update... and the update manager fails.

A crash was reported but the update still finished in the background and then software updater notification popped up and showed the update was complete

It is keeping my Nvidia card from working right.

My wifi stopped working.
Flashes of errors .

updater just crashed running ubuntu saucy gnome 3.9.92 gnome3team and the staging repositories installed not the ricotz rep
it crashed after this rapport was made it gave an error that i did not have the right i dont know exact translation because it was in dutch
im running updater again without any fix or anything seems to be working fine now

This happened to me today and I received a dialog from the Software Updater indicating that "Task cannot be monitored or controlled" … "The connection to the daemon was lost. Most likely the background daemon crashed.".

I experienced this bug a few days ago. The cause was the password timeout issue mentioned above. Normally, Saucy doesn't require sudo password when running the updater, so starting it up and leaving the computer is normal user behavior. Something in this update, however, triggered the password requirement, but since I was afk it timed out and the error was all I saw upon returning.

saucy when i click cancel for update

I've been able to recreate this by clicking cancel at the authentication dialog regarding installing packages.

The Software Updater dialog changes to one indicating that "You are not allowed to perform this action".

Additionally, if you wait long enough at the authentication dialog the software updater window will become only like a pixel or two high.

Running Software Updater after boot it crashed sometime after I OK'd the listed updates - I was away from the machine whilst it was downloading the updated packages - but when I re-ran the Updater it finished OK.

UK13.10 -> UK14.04: Command to upgrade error!

Exists in amd64, i386 is OK!

Trusty i386 is affected :(

It doesn't truly crash, as the updates continue to install, and the confirmation message appears as usual. What's missing from time to time is the GUI progress.

Trusty amd64 is affected

As other have mentioned, Trusty amd64 is also affected. For some reason, my 'about this system' in control panel still says I'm running Saucy, probably unrelated, but I'm not sure. The update process still appears to be running, but the window is only the top bar and nothing else. I assume the updates are installing, as there is a progress bar on the icon like usual. I'll let it run and see what happens.

Shutdown in process.

Crash is repeatable by chossing the "cancel" button on the authorizaton window.

The crash apears also in the second alpha of Ubuntu 14.04.

Bug still appears in i386

@eEdu@rdOo._.J.N.J.: Please do not change bug's statuses without a comment. Please use the "This bug affects meet too" link below this bug's title if you want to mark this bug as affecting you. Thanks in advance.

additionally to Dave(dlgawley): Crash appeared after three times entering wrong password into auth box.

Update-Manager doesn't ask me my password for install updates and then closes

Crashed in Ubuntu 14.04.

yep, crashed in Ubuntu 14.04.

crashed while waiting a long time for typing in the root password to confirm a "system-update".

No password requested during update, or password dialog did not appear. Updater finishedd with message dialog 'Package Operation Failed - The installation or removal of a software package failed'.

The error always occurs when a password is requested and it isn't entered immediately. (Same behavior as starkus described).

Crashed in Ubuntu 14.04

Crashed in ubuntu 14.04 as well under "normal" circumstances, password bar showed up, began reading repository... crash

I saw this same error when updating an AMD64 laptop running 14.04. I left the room after starting the update, and the computer had turned the screen off and locked due to inactivity. When I came back and unlocked the computer, the system error dialog had popped up. I am re-running the update, and keeping the computer active. Everything is going fine so far.

Crashed in ubuntu 14.04 as well under "normal" circumstances, password bar showed up, began reading repository... crash

The error always occurs when a password is requested and it isn't entered immediately.

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

Regarding this bug (1202754) and bug 1272776 (labeled a duplicate of bug 1237569) - my experience in both cases delay in entering the password results in a hiccup.

Delaying password entry for an update results in the update manager falsely reporting that it is out of action; the requested update will go on to completion without problems to the next step - requesting a restart or reporting the system as up to date.

Delaying password entry in the startup window results in no response to the hardware keyboard or the mouse until, for example, clicking on the speaker icon twice. Bringing up the on screen keyboard works to enter a password, as well as clicking the onscreen keyboard access icon twice and entering the password via the hardware keyboard.

Running Trusty Tahr, last updated at ~1715 (Zone -8) on 07Mar2014
    nvsoar

I now don't have the opportunity to enter the password at all. It simply says "You are not authorized to perform this action", and the updater crashes and takes me back here again.

Running Trusty Tahr, last updated 17Mar2014.

Further on my previous comment...neither manual or automatic updates work now.

Running Trusty Tahr, last updated 17Mar2014 (unable to update since).

After the error, updates window does not show correctiy, but updates keep installing.

In my case, updates don't install, the update application either crashes (which I assume is happening since I am sent here) and/or closes. This happens daily, and no updates are installed.

Running Trusty Tahr, last updated 17Mar2014 (unable to update since).

I believe I have solved my problem! After some research, I made the following change:

--> Preferences --> Default Applications for LXSession --> Autostart

          CHECKED the box for PolicyKit Authentication Agent

Closed and rebooted.

Now the software updater runs perfectly! Something apparently changed in the way authentication is done/or unchecked PolicyKit during a prior update. I don't remember doing anything in that area at all myself.

Hope this will be a clue to some resolution for others!

Running Trusty Tahr, last updated 21Mar2014

All I can add to my comment #31 is that I'm usually running a Wine program when updating, but it updates normally while running one as well.

I found that it only happens to me if I don't put in my password within a certain amount of time. Now if I put my password in after the crash the packages still download and install. However I discovered today that eventually the Authenticate window will error out if I wait long enough. I'm running 14.04 amd64.

Only seems to happen if I expand something in the details panel first. Then if authentication is required the authentication input box does not appear and update crashes. If I then run it again and don't expand anything the authentication input appears, I authenticate and update proceeds as normal.

Just got this crash while updating 14.04 today, and the update-manager window became as shown in the snapshot.

Seems to be a problem with the PolicyKit, since this issue started for me today. I can no longer launch SoftwareUpdater or software-center (the latter just consumes all 4 GB of system memory in a few seconds.)
The only thing that works right now is running it as "gksu update-manager" ...

update-manager exits without asking for a sudo password.
"gksu update-manager" solve this problem.

I also have to start network manually, because net-indicator tell me I don't have enough privileges:

sudo ifconfig eth1 192.168.x.x up
sudo route add default gw 192.168.x.x

I don't know if every user out there knows how to raise network, so this post represents many upset users without possibility of report this problem.

Update manager never prompts for sudo password then says I don't have the privileges to run updates manager. Also I've lost the ability to shutdown without using a command prompt. When I select restart or shutdown it takes me to logoff only.

Same promlem here, in Ubuntu 14.04

Update manager not working " You don't have the required privileges to perform this action." And also I've lost the ability to shutdown & Restart without using a command prompt. When I select Restart or Shutdown it takes me to Log Out only.
The speed of ubuntu is too slow, Synaptic Pakage Manager- not working and I can not open my others driver (directory) it says that "Not authorized to perform operation".

I found this link https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1302412 and ran "sudo update-manager" in a terminal and was able to successfully run software updater without getting the "You don't have the required privileges to perform this action" error. Once I updated and restarted, software updater ran fine, my user was showed as logged in and when I tried to restart, I was able to, not just log out like knightscove noted. General performance improved significantly as well.

This command solve my problem run in terminal " sudo update-manager".
Now system works fine no - Update manager, PolicyKit Authentication Agent or restart errors/problems, and thanks to TheRacquetTech.
My OS is Ubuntu 14.04.

i got this error when the update manager requested the administrator password but i clicked the cancel button

Received this error after entering my password when prompted after runing Software Updater (update-manager).

Also affects Ubuntu Gnome 14.04

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

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

  * lp:~mvo/update-manager/lp1202754:
    - do nt crash if the user clicks "cancel" in the polkit dialog
      (LP: #1202754)
 -- Michael Vogt <email address hidden> Thu, 10 Apr 2014 14:29:00 +0200

This isn't fixed - I Apported it when it crashed randomly and this tab came up in my browser. Someone change it back to 'Triaged' for Ubuntu please?

I tried and I can't reproduce, so I think it is fixed in Trusty but not in Saucy - should be SRUed there

Affected on Ubuntu 14.04 when i'm try apply too many updates.