update-manager crashed with TypeError in function(): Must be number, not tuple

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

Still having this problem Robert?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

I just had this problem. Marking it as confirmed.

Any chance you can describe what you were doing with U-M when this happened? Did you expand the details dialog, resize a window, etc.?

Not really, just did an update.

I have the same error. I have finished to click on the update.

Same here, however I have apt-listchanges running, so my crash occurred after hitting 'q' in the details after reviewing the changelog (though it was squished to a 1 line output, and I was in a rush, knew it was the recent libSSL CVE update, so I didn't/couldn't read anything).

In my case, it did re-launch in a completed state, i.e. No new updates.

I saw the bugpattern-needed tag, so I submitted my apport trace in #921586

It maybe helpful to know the following things from people experiencing this bug:

1) Do you have apt-listchanges installed?
2) What version of aptdaemon do you have installed? (if you are currently encountering this bug)

1) I don't have it
2) 0.43+bzr697-0ubuntu1.1

aptdaemon - 0.43+bzr697-0ubuntu1.1. This hasn't re-occured for me yet.

This is really a problem in aptdaemon.

I'm going to mark this bug as incomplete since I cannot reproduce it. However, if you are running at least aptdaemon 0.43+bzr769-0ubuntu1 and encounter the problem again, please apply the attached diff to /usr/lib/python2.7/dist-packages/aptdaemon/gtk3widgets.py and paste the output so we know what is causing the problem. I can't see anything wrong in the code.

It happened to me again, so I applied the patch. Would I have to run the update-manager with stdout visible all the time, or will the information be included in the bug report?

Right.

Right, you have to run update-manager in a terminal to get the stdout. It won't be automatically attached to an error report.

Happened to me again, but I didn't have it in a terminal. So the issue is still there, will try to get the msg.

Just a comment about my Issue

I had 4 open terminals 3 in ssh mode 1 of them had a couple tabs
Aptana
Libre Office
ThunderBird
FireFox
Empathy
idk what else

And while it was running its post installation triggers i tried to add more to the process list when it died

aka I think I killed it, this error was most likely my fault

I have to take back my last comment.

This time everything was closed down and only the normal desktop was running

The attachment "Diagnostic help" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

just made the changes inside of /usr/share/pyshared/aptdaemon/gtk3widgets.py

subtracted 1 line and added the rest let ya know when I get back

Aptana loaded and I could navigate throught it, which I wasn't able to do before.
Firefox didnt have an Adobe crash immediatley after opening it.
Gedit open on the first try
Thunder Bird opened I I can now navigate it
So far I have to say thank you for the patch, but will be back to complain if i find more errors..... :D

(i am still referring to this bug as a general SIGSEGV error) because all of my combined issues seemed to be the same

As I clicked post comment below this is what enetered my terminal for aptana

james@dev:~$ aptana

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x01073f01, pid=2290, tid=121592688
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode, sharing linux-x86 )
# Problematic frame:
# V [libjvm.so+0x241f01] InterpreterRuntime::newarray(JavaThread*, BasicType, int)+0x101
#
# An error report file with more information is saved as:
# /home/james/hs_err_pid2290.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)
james@dev:~$

Although initially it seemed to fix "all of my problems" making the changes to /usr/share/pyshared/aptdaemon/gtk3widgets.py seem to have made it worse. and revrting back to the original version hasnt fixed anything either (i only barely know my way around in this area) my cli exp is limited to standard web dev stuff like error_log, mysql, nano, find, etc

NEW ISSUES:
I get a system error to report now when the pc first logs onto my user. If i try to report the bug it sets off a slew of other errors and ultimately fails.

I am getting ready to re install ununtu after I have backed up a few more files, if there is any help I can supply, errologs dumps etc please let me know I will check back here before I install the new image.

The issue appeared to originate from end, I was unable to identify the exact cause do to time constraints. Its a good think ubuntu only takes a couple hours for a complete re install vs windows all day affair
A clean install seemed to fix everything

bug-898851.diff is not actually a patch fixing this bug.

Looking at the attachments in this bug report, I noticed that "Diagnostic help" was flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug, since this was not one I've unchecked the patch flag for it. In the future keep in mind the definition of a patch. You can learn more about what qualifies as a patch at https://wiki.ubuntu.com/Bugs/Patches. Thanks!

Since we cannot get to the root of the problem - which seems to be located in GTK+ or Python GI - I would vote to just work arround the crash.

Sebastian - do you think we should just add this patch to Raring?

Indeed. I just forgot this patch :) Should make sense. The error reports of the users seem to indicate that there is really something more worse broken on their system and we only see a side effect here.

This bug was fixed in the package aptdaemon - 1.0-0ubuntu8

---------------
aptdaemon (1.0-0ubuntu8) raring; urgency=low

  *debian/patches/fix-lp898851.patch: Workaround a random crash during
   progress dialog. Thanks to Sebastian Heinlein for the patch. (LP: #898851)
 -- Brian Murray <email address hidden> Fri, 22 Mar 2013 15:09:13 -0700