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 am attempting to load 11.04 version from a USB drive. I have done this once already on my netbook with no problem. Now I am attempting to do the same on my HP Desktop. The system loads and works from the USB but when I try to install it permanently on my hard drive (the whole drive) I keep getting the error message "APT configuration problem. An attempt to configure apt to install additional packages from the CD failed" The installer crashes shortly afterwards. And again I am attempting this from a USB drive and not a CD? I also received this current error when I tried to update to the new version once I had loaded and ran the system from the USB. I have tried various combinations to get this installed on the desktop with the same loader crash results as I love the software on my netbook. Thanks
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Nov 11 10:18:59 2011
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
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.