Update-manager crashes on fresh natty installs-- NotAuthorizedError: org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name': ':1.107'}): org.debian.apt.upgrade-packages

Bug #704667 reported by pschonmann
706
This bug affects 77 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt
Natty
Fix Released
High
Michael Vogt

Bug Description

Binary package hint: update-manager

-----------------
Summary: Update-manager crashes after clicking cancel during the "authentication" window.
-----------------

I ran um
There appears window with partial update announce, i canceled that to see latest packages.
Then i click on check to check new packages.
After that i clicked on install and u-m crashed.

ProblemType: CrashDistroRelease: Ubuntu 11.04
Package: update-manager 1:0.145.10
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
Architecture: amd64
Date: Tue Jan 18 23:17:12 2011
ExecutablePath: /usr/bin/update-managerInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager
ProcEnviron:
 LANGUAGE=en
 LANG=cs_CZ.utf8
 LC_MESSAGES=en_AG.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']SourcePackage: update-manager
Title: update-manager crashed with NotAuthorizedError in _run(): org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name': ':1.107'}): org.debian.apt.upgrade-packages
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
pschonmann (pschonmann) wrote :
pschonmann (pschonmann)
visibility: private → public
tags: removed: need-duplicate-check
Revision history for this message
RedSingularity (redsingularity) wrote :

Thanks for taking the time to report this.

Please attach the dpkg.log located in /var/log/dpkg.log

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
pschonmann (pschonmann) wrote :
Revision history for this message
RedSingularity (redsingularity) wrote :

Thanks. Now run the following:

sudo apt-get update | tee ~/Desktop/Update1

Attach the file that will be located on the desktop to your next post.

Revision history for this message
pschonmann (pschonmann) wrote :
Revision history for this message
RedSingularity (redsingularity) wrote :

Update looks good as well. Obviously there are some custom sources which may be triggering the "partial update announce" but thats not an issue.

Can you reproduce the bug again? Crashing the update-manager?

Revision history for this message
pschonmann (pschonmann) wrote :

No, i cant reproduce it now. I updgraded with aptitude in console.

Revision history for this message
RedSingularity (redsingularity) wrote :

Ok, I will leave this report open. Wait until you can test it again and report the results. It may have been a one time error and you will not see it again. In the meantime, I will try reproducing this bug on my test machine and report back as well.

Thanks.

Revision history for this message
old_toby (simon-hornweb) wrote :

I don't think it's an apt-related bug. The crash always comes together with a crash of policykit. So update-manager just doesn't know how to handle that.

Revision history for this message
RedSingularity (redsingularity) wrote :

Yes, it seems that the policykit package is causing the crash. I will mark the bug accordingly.

@ old_toby

You are running Natty as well correct?

Revision history for this message
old_toby (simon-hornweb) wrote :

Yes, I'm also running natty.

Revision history for this message
RedSingularity (redsingularity) wrote :

Hold on......it may not be policykits fault.

Does anyone else notice a problem with other packages that use the policykit? Such as synaptic or using gksudo to open a program?

Revision history for this message
RedSingularity (redsingularity) wrote :

Sorry, gksudo does not use polkit. Disregard.

Revision history for this message
old_toby (simon-hornweb) wrote :

You mean that

1. There's a bug in update-manager which ...
2. ... causes a crash of policykit which ...
3. ... causes this bug

Anyway, policykit should know how to handle a wrong call (or whatever it is), and should rather produce an error message than a crash.

Revision history for this message
RedSingularity (redsingularity) wrote :

@old_toby

Are you still able to get update-manager to crash?

Revision history for this message
old_toby (simon-hornweb) wrote :

I think yes. It crashes most of the time. (but not today, all updates are done)

Revision history for this message
RedSingularity (redsingularity) wrote :

@old_toby

Did you update from the command line to get past the crash?

Revision history for this message
old_toby (simon-hornweb) wrote :

Yes, I usually do this.

Revision history for this message
RedSingularity (redsingularity) wrote :

Marking as confirmed. Seems that the bug is present on a fresh install of 11.04 1/31/11 daily build. Running update-manager as sudo seems to solve the issue and allow an upgrade. (Probably because it goes around policykit) After performing a current update and rebooting the problem appears solved. You can then launch update-manager from the application menu as normal.

To initially get past the bug and perform an update use the command:

gksudo update-manager & exit

Changed in update-manager (Ubuntu):
status: Incomplete → Confirmed
tags: added: bugpattern-needed
Revision history for this message
RedSingularity (redsingularity) wrote :

UPDATE:

I have also noted that this error primarily takes place if you allow the "Enter password" window to remain open for a few seconds with no user input.

description: updated
summary: - update-manager crashed with NotAuthorizedError in _run():
- org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name',
- {'name': ':1.107'}): org.debian.apt.upgrade-packages
+ Update-manager crashes on fresh natty installs
Revision history for this message
old_toby (simon-hornweb) wrote : Re: Update-manager crashes on fresh natty installs

@RedSingularity

No, I don't think so. Here it crashed most of the time before the "Enter password" window even appeared (or when I click cancel or enter a wrong password).

Revision history for this message
RedSingularity (redsingularity) wrote :

@old_toby

What natty build are you using? Date wise?

Revision history for this message
RedSingularity (redsingularity) wrote :

@old_toby

Yes I see it now. Thanks for that info.

UPDATE:

When password prompt comes up, clicking cancel OR entering wrong password will indeed crash it as well.

description: updated
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
old_toby (simon-hornweb) wrote :

@RedSingularity

Well, it's not only on fresh natty installs.

I once installed Ubuntu Edgy and upgraded from there ever since.

Revision history for this message
Paul White (paulw2u) wrote :

This morning (16/02/2011 0615GMT) cannot upgrade the mount package. Trying to do so causes the policy kit error and update manager crash. All other updates offered are processed correctly.

Revision history for this message
Paul White (paulw2u) wrote :

This is the error copied from terminal when using aptitude when trying to install mount:

Preparing to replace mount 2.17.2-3.3ubuntu4 (using .../mount_2.17.2-9.1ubuntu1_i386.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 49: dpkg-vendor: not found
dpkg: error processing /var/cache/apt/archives/mount_2.17.2-9.1ubuntu1_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 127
No apport report written because MaxReports has already been reached
                                                                    Errors were encountered while processing:
 /var/cache/apt/archives/mount_2.17.2-9.1ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

mount also will not update using update manager due to policy kit error as I reported above.

tags: added: bugpattern-written
removed: bugpattern-needed
Revision history for this message
Rohit R (rr0hit) wrote :

I face the same problem, but only when i click cancel in the authentication box. Here is the error i get when i run update-manager from the terminal and press the cancel button in the authentication prompt :

update-manager
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/defer/__init__.py", line 472, in _inline_callbacks
    result = gen.throw(result.type, result.value, result.traceback)
  File "/usr/lib/python2.7/dist-packages/aptdaemon/gtkwidgets.py", line 633, in _run
    yield self._transaction.run()
aptdaemon.errors.NotAuthorizedError: org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name': ':1.61'}): org.debian.apt.install-or-remove-packages

Revision history for this message
Remco Brenninkmeijer (requist1) wrote :

I can still reproduce the bug (haven't used aptitude yet), also get an error message when using synaptic package manager (see duplicate bug 73809). I am using 11.04 alpha 3 for a couple of weeks, updated daily. Problem appeared today.

please say if I can help with any data..

summary: - Update-manager crashes on fresh natty installs
+ Update-manager crashes on fresh natty installs NotAuthorizedError:
+ org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name',
+ {'name': ':1.107'}): org.debian.apt.upgrade-packages
summary: - Update-manager crashes on fresh natty installs NotAuthorizedError:
+ Update-manager crashes on fresh natty installs-- NotAuthorizedError:
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name',
{'name': ':1.107'}): org.debian.apt.upgrade-packages
description: updated
description: updated
Revision history for this message
Alessandro Losavio (alo21) wrote :

I have the same problem in Ubuntu Beta 1 amd64

Revision history for this message
Kate Stewart (kate.stewart) wrote :

Based on the number of duplicates, marking this bug as high, and making sure its on the canonical foundations team radar.

Changed in update-manager (Ubuntu Natty):
importance: Medium → High
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed with the following upload:

update-manager (1:0.147.2) natty; urgency=low

  * UpdateManager/backend/InstallBackendAptdaemon.py:
    - no not trigger a apport exception on user auth issues and if
      the user does not type the password in time (LP: #626798)

 -- Michael Vogt <email address hidden> Tue, 05 Apr 2011 15:49:58 +0200

Changed in update-manager (Ubuntu Natty):
assignee: Canonical Foundations Team (canonical-foundations) → Michael Vogt (mvo)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.