update-manager crashed with TypeError in _on_synaptic_exit()

Workaround is to use the command-line instead. e.g. "# apt-get update".

Installing python-aptdaemon-gtk (and perhaps aptdaemon) works around this issue. It will use an aptdaemon backend, instead of the buggy Synaptics backend.

Barry, the second argument of the signal indicates whether the action is authorized or not. For the synaptic backend it must be True because synaptic must be run as root to perform the update and is always authorized. I can't think of a way to know if synaptic has been authorized or not to do the check.

I think your fix is incorrect because you set the second argument to 0 which is "False", and the package list won't be refreshed. Unless my boolean math is wrong, the patch should be :

--- /usr/lib/python2.7/dist-packages/UpdateManager/backend/InstallBackendSynaptic.py 2010-09-07 17:30:58.000000000 +0200
+++ UpdateManager/backend/InstallBackendSynaptic.py 2010-11-11 19:24:34.000000000 +0100
@@ -34,7 +34,7 @@
         action, tempf = data
         if tempf:
             tempf.close()
- self.emit("action-done", action)
+ self.emit("action-done", action,True)

     def update(self):
         opt = ["--update-at-startup"]

Please also consider bug 674175, which prevent the aptdaemon backend to be loaded in Natty.
Thanks.

Jean-Baptiste,

Thanks! I found it surprisingly difficult to find any documentation about the semantics of that second argument. Do you have a reference for that?

I just pushed an update with your suggested change. I'll start another PPA build and then test it in my Natty VM. If that works, I'll ask Michael for a merge proposal.

ppa:pythoneers/py27stack4

Well, the only piece of "reference documentation" I'm aware of is ... the source code, thanks to the explicit naming of the arguments of the callback _on_backend_done in UpdateManager/UpdateManager.py

Thanks for your help on this fix.

/me sees the light bulb go on!

Now I get it. Thanks. :)

I confirm that the patch fixes the problem.

Accepted update-manager into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

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

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

  [ Barry Warsaw ]
  * Add required details to .emit() call. (LP: #631328)

  [ Michael Vogt ]
  * debian/control:
    - add or-dependency for python-aptdaemon-gtk and drop gksu
      dependency (its either brought in via synaptic or not needed)
  * UpdateManager/Core/utils.py:
    - add get_arch() call
  * DistUpgrade/DistUpgradeController.py, DistUpgrade/DistUpgradeQuirks.py:
    - use new utils.get_arch() call
  * merged fixes from lp:~ubuntu-core-dev/update-manager/maverick
  * debian/rules:
    - push EOLReleaseAnnouncement to the server too
 -- Michael Vogt <email address hidden> Fri, 12 Nov 2010 15:56:32 +0100

Verified that update-manager no longer hangs. I installed Ubuntu 10.10 in VirtualBox, and ran updates. I then reproduced the original issue following the TestCase given. I then installed -proposed, installed the fixed update-manager, and ran test case again. The error no longer prints in terminal, and update manager completes the check for new updates.

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

---------------
update-manager (1:0.142.22) maverick-proposed; urgency=low

  [ Barry Warsaw ]
  * Add required details to .emit() call when running with
    synaptic as the backend (LP: #631328)

  [ Michael Vogt ]
  * DistUpgrade/DistUpgradeQuirks.py:
    - fixes in the cmov quirks handler (LP: #587186)
      (thanks to Jean-Baptiste Lallement)
 -- Michael Vogt <email address hidden> Fri, 12 Nov 2010 09:30:28 +0100