check-new-release-gtk crashed with TypeError in on_button_ask_me_later_clicked(): integer argument expected, got float
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have a fresh install of Xubuntu 11.04 i386 on a flash drive, and I was booting it on one of my desktop systems. When I booted up, the upgrade release dialog popped up, offering me to upgrade to Xubuntu 11.10. To dismiss it, I clicked "Ask me later", which caused the upgrade dialog to crash. I am submitting this report with the automatically included information. I will reboot and see if I can reproduce it.
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
ubuntu@ubuntu:~$ apt-cache policy update-manager
update-manager:
Installed: 1:0.150
Candidate: 1:0.150.2
Version table:
1:0.150.2 0
500 http://
*** 1:0.150 0
500 http://
100 /var/lib/
ubuntu@ubuntu:~$
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Thu Dec 22 10:38:29 2011
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
PackageArchitec
ProcCmdline: /usr/bin/python2.7 /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: update-manager
Title: check-new-
Traceback:
Traceback (most recent call last):
File "/usr/lib/
client.
TypeError: integer argument expected, got float
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #886564, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.