check-new-release-gtk crashed with TypeError in on_button_ask_me_later_clicked(): integer argument expected, got float

Bug #875429 reported by Dreyer
This bug report is a duplicate of:  Bug #873424: ask me later fails. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu (any version 10.4 11.10 or 11 4 wont install, i can only run them from a stick.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat Oct 15 21:11:27 2011
ExecutablePath: /usr/lib/update-manager/check-new-release-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/lib/update-manager/check-new-release-gtk
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/update-manager/check-new-release-gtk']
SourcePackage: update-manager
Title: check-new-release-gtk crashed with TypeError in on_button_ask_me_later_clicked(): integer argument expected, got float
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/update-manager/check-new-release-gtk", line 126, in on_button_ask_me_later_clicked
     client.set_int("/apps/update-notifier/release_check_time", next_check)
 TypeError: integer argument expected, got float
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #874346, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
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.