A failed Run() call doesn't let the transaction fail (e.g. authorization errors)

Bug #891255 reported by stefan
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When hitting 'Install Updates' on the Update Manager, it briefly greys out the manager but does not actually proceed to update anything. syslog says something has been queued:

Nov 16 09:03:45 myserver AptDaemon: INFO: CommitPackages() was called: dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'icedtea-6-jre-cacao'), dbus.String(u'icedtea-6-jre-jamvm'), dbus.String(u'liblightdm-gobject-1-0'), dbus.String(u'openjdk-6-jre-headless'), dbus.String(u'openjdk-6-jre-lib')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s'))
Nov 16 09:03:45 myserver AptDaemon.Trans: INFO: Queuing transaction /org/debian/apt/transaction/7d380769c12e48aa99632f955582f2f3

after a while a window pops up informing me that
"Task cannot be monitored or controlled"
The connection to the daemon was lost. Most likely, the background daemon crashed.
Details:
   It seems that the daemon died.

Which is true since syslog tells us:

Nov 16 09:06:04 myserver AptDaemon: INFO: Quitting due to inactivity
Nov 16 09:06:04 myserver AptDaemon: INFO: Quitting was requested

apt-get per commandline works fine as a workaround.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.152.25.4
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Nov 16 09:22:43 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: Upgraded to oneiric on 2011-10-21 (25 days ago)

Revision history for this message
stefan (stefan-phas) wrote :
description: updated
stefan (stefan-phas)
summary: - update-manager loses connection to daemon - can't update
+ Update impossible with update-manager -- loses connection to daemon
Revision history for this message
RedSingularity (redsingularity) wrote : Re: Update impossible with update-manager -- loses connection to daemon

Any output if Update-manager is run in a terminal?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
stefan (stefan-phas) wrote :

Yes, numerous Gdk_CRITICAL ones that are probably not relevant to this bug and one that might elucidate the situation I hope:

(update-manager:2033): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

ERROR:dbus.proxies:Introspect error on :1.3:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.220" (uid=1000 pid=2033 comm="/usr/bin/python /usr/bin/update-manager ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=1083 comm="NetworkManager ")

(update-manager:2033): Gtk-WARNING **: Attempting to add a widget with type aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin subclass a GtkWindow can only contain one widget at a time; it already contains a widget of type GtkVBox

(update-manager:2033): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

Revision history for this message
stefan (stefan-phas) wrote :

One further comment:

If I start update-manager with su privileges (sudo update-manager) from the command line, the whole process works as expected.

So it is obviously a result of update manager unsuccessfully attempting to acquire those access rights. In past releases, it would ask me for my password (I'm member of group admin) and be on its merry way. Now, as I understand, it will not ask for this but as a result it fails to perform said updates for lack of authority.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport. This is on ubuntu 11.10, correct?

Could you please check if you have the "policykit-1-gnome" package installed? When its missing update-manager can't put up the permission dialog.

is there anything else unusual about your system. There is one output releated to network-manager. Do you have this package installed ? And if so, is it generally working? Anything else that might be unusual about the system and give us a clue what causes the error?

Revision history for this message
Michael Vogt (mvo) wrote :

Could you also please run aptdaemon in a terminal with:
$ sudo aptd --debug --replace --disable-timeout
and then start update-manager again and attach the output of the aptd terminal?

Revision history for this message
stefan (stefan-phas) wrote :

Yes, ubuntu 11.10 release-upgraded from 11.04

$ dpkg -s policykit-1-gnome
Package: policykit-1-gnome
Status: install ok installed
...
Architecture: amd64
Version: 0.102-1ubuntu1
...
$ dpkg -s network-manager
Status: install ok installed
...
Architecture: amd64
Version: 0.9.1.90-0ubuntu5
...

Not sure whether I can attest to network-manager working. I have eth0 with a constant IP assigned based on my MAC in a university dept. All very boring but otherwise functional.

I have attached the aptd output while running update manager in user space and also with sudo privileges. I hope you can divine some meaning from it. It doesn't look all that informative.

Thanks, Stefan

Revision history for this message
Ian Nicholson (imnichol) wrote :

I have been experiencing this issue on 12.04 for several weeks now. I run apt-get from the command line in order to update my system.

Revision history for this message
Joe Van Demark (jjvandemark) wrote :

I have the same issue, I can run update-manager as root but see the following:

warning: could not initiate dbus

(update-manager:2165): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

** (update-manager:2165): WARNING **: Timeout was reached

(update-manager:2165): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

I am running Kubuntu, not Unity, possibly part of the problem.
warning: could not initiate dbus

(update-manager:2165): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

(update-manager:2165): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed

** (update-manager:2165): WARNING **: Timeout was reached

(update-manager:2165): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Timeout was reached

** (update-manager:2165): WARNING **: Timeout was reached

Micheal, are you still looking for the output from running aptd as you suggested?

     aptd --debug --replace --disable-timeout

If so let me know.

How is aptd started? I didn't find anything in /etc/init.d/ that looked applicable, nor did /etc/apt/conf.d/* suggest a way to add the requested argument, though I didn't look very hard.

Joe

Revision history for this message
Joe Van Demark (jjvandemark) wrote :

Opps, sorry looks like some of the output I posted is actually duplicated :(

After the initial output is should have read as follows:

I am running Kubuntu, not Unity, possibly part of the problem.

Micheal, are you still looking for the output from running aptd as you suggested?

     aptd --debug --replace --disable-timeout

If so let me know.

How is aptd started? I didn't find anything in /etc/init.d/ that looked applicable, nor did /etc/apt/conf.d/* suggest a way to add the requested argument, though I didn't look very hard.

One other comment, I need to run "xhost +" prior to "su root" & "update-manager"

Joe

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

I can add only

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/UpdateManager/MetaReleaseGObject.py", line 42, in check
    def check(self):
from 12.04

Changed in update-manager (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Complete strace
22:55:45 clicked install
22:56:13 inserted passsword
22:56:26 clicked again install then UM start
23:01:... advcice of daemon lost

tags: added: precise
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Probably unrelated
[pid 6966] 23:02:17.177394 read(120, "i indici o bibliografie e visual"..., 4096) = 4096
[pid 6966] 23:02:17.177721 read(120, " pacchetto permette ad un progra"..., 32768) = 32768
[pid 6966] 23:02:17.178069 read(120, "di sistema e programmatori devon"..., 4096) = 4096
[pid 6966] 23:02:17.179736 lseek(129, 94208, SEEK_SET) = 94208
[pid 6966] 23:02:17.180180 read(129, " | debconf-2.0, emacs23 | emacs2"..., 4096) = 4096
[pid 6966] 23:02:17.180496 read(129, "e: pool/main/a/auth-client-confi"..., 32768) = 32768
[pid 6966] 23:02:17.180825 read(129, "22ea51518642640\nBugs: https://bu"..., 4096) = 4096

tags: added: strace
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Seems today's aptd upgrade fix this issue on precise
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
RedSingularity (redsingularity) wrote :

Thanks Fabio. Can anyone else confirm?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Ian Nicholson (imnichol) wrote : Re: [Bug 891255] Re: Update impossible with update-manager -- loses connection to daemon

Worksforme. Muchos thanks.

Sent from my Palm PreOn Jan 3, 2012 16:50, Tim &lt;<email address hidden>&gt; wrote:

Thanks Fabio. Can anyone else confirm?

---

Ubuntu Bug Squad volunteer triager

http://wiki.ubuntu.com/BugSquad

--

You received this bug notification because you are subscribed to the bug

report.

https://bugs.launchpad.net/bugs/891255

Title:

  Update impossible with update-manager -- loses connection to daemon

Status in “update-manager” package in Ubuntu:

  Confirmed

Bug description:

  When hitting 'Install Updates' on the Update Manager, it briefly greys

  out the manager but does not actually proceed to update anything.

  syslog says something has been queued:

  Nov 16 09:03:45 myserver AptDaemon: INFO: CommitPackages() was called: dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'icedtea-6-jre-cacao'), dbus.String(u'icedtea-6-jre-jamvm'), dbus.String(u'liblightdm-gobject-1-0'), dbus.String(u'openjdk-6-jre-headless'), dbus.String(u'openjdk-6-jre-lib')], signature=dbus.Signature('s')), dbus.Array([dbus.String(u'')], signature=dbus.Signature('s'))

  Nov 16 09:03:45 myserver AptDaemon.Trans: INFO: Queuing transaction /org/debian/apt/transaction/7d380769c12e48aa99632f955582f2f3

  after a while a window pops up informing me that

  "Task cannot be monitored or controlled"

  The connection to the daemon was lost. Most likely, the background daemon crashed.

  Details:

  &nbsp;&nbsp;&nbsp;It seems that the daemon died.

  Which is true since syslog tells us:

  Nov 16 09:06:04 myserver AptDaemon: INFO: Quitting due to inactivity

  Nov 16 09:06:04 myserver AptDaemon: INFO: Quitting was requested

  apt-get per commandline works fine as a workaround.

  ProblemType: Bug

  DistroRelease: Ubuntu 11.10

  Package: update-manager 1:0.152.25.4

  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4

  Uname: Linux 3.0.0-12-generic x86_64

  NonfreeKernelModules: nvidia

  ApportVersion: 1.23-0ubuntu4

  Architecture: amd64

  Date: Wed Nov 16 09:22:43 2011

  EcryptfsInUse: Yes

  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)

  PackageArchitecture: all

  ProcEnviron:

  &nbsp;LANGUAGE=en_CA:en

  &nbsp;PATH=(custom, user)

  &nbsp;LANG=en_CA.UTF-8

  &nbsp;SHELL=/bin/bash

  SourcePackage: update-manager

  UpgradeStatus: Upgraded to oneiric on 2011-10-21 (25 days ago)

To manage notifications about this bug go to:

https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/891255/+subscriptions

Revision history for this message
stefan (stefan-phas) wrote : Re: Update impossible with update-manager -- loses connection to daemon

to test on 11.10, I'd need to wait until I'm not up-to-date (or do I?)

Revision history for this message
Brian Murray (brian-murray) wrote :

The precise issue seems to have been a different one than the original reporter's bug and is fixed.

tags: removed: precise
Revision history for this message
stefan (stefan-phas) wrote :

The most recent upgrade don't seem to concern update-manager. So no luck.

To make matters worse, I believe a related problem exists for software-center. I can not install anything as user (I will never be asked for user privileges). But I can install stuff when starting "sudo software-center". Isn't this fairly serious for a user that doesn't use commandline apt-get? How come there are so few reports of this?!

Revision history for this message
RedSingularity (redsingularity) wrote :

Well this may a local bug, as in, it only effects the configuration set on your machine. I am going to install a fresh 11.10 and try to reproduce this issue. Will report back with results.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
RedSingularity (redsingularity) wrote :

Seems to be working fine on my testbed machine. What version of update-manager do you have installed?

'apt-cache policy update-manager' will tell you.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
stefan (stefan-phas) wrote :

Remains to be a problem for me. Did you try 64bit?

$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.152.25.5
  Candidate: 1:0.152.25.5
  Version table:
 *** 1:0.152.25.5 0
        500 http://ca.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.152.25 0
        500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

Revision history for this message
RedSingularity (redsingularity) wrote :

Changing package due to aptdaemon errors in logs.

affects: update-manager (Ubuntu) → aptdaemon (Ubuntu)
Changed in aptdaemon (Ubuntu):
status: Confirmed → New
summary: Update impossible with update-manager -- loses connection to daemon
+ AptDaemon: INFO: CommitPackages() was called:
+ dbus.Array([dbus.String(u'')],
Changed in aptdaemon (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
summary: - Update impossible with update-manager -- loses connection to daemon
- AptDaemon: INFO: CommitPackages() was called:
- dbus.Array([dbus.String(u'')],
+ A failed Run() call doesn't let the transaction fail (in the case of
+ e.g. authorization errors)
summary: - A failed Run() call doesn't let the transaction fail (in the case of
- e.g. authorization errors)
+ A failed Run() call doesn't let the transaction fail (e.g. authorization
+ errors)
Changed in aptdaemon (Ubuntu):
status: In Progress → Fix Committed
Changed in aptdaemon (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jon Kirton (jon-fourjs) wrote :

I have this problem on 12:04 started yesterday.

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.