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

[Franz Apeltauer]

uname -a
Linux ubuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 athlon i386 GNU/Linux

lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

apt-cache policy update-manager
update-manager:
  Installed: 1:0.150
  Candidate: 1:0.150
  Version table:
 *** 1:0.150 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

CPU: Athlon XP (0.13)
Chipset: VIA KT400(A)/600

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: Mon Oct 24 19:04:38 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

[Franz Apeltauer (franz-apeltauer)]

This happened short after booting the Natty live CD.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #873424, so it 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. Feel free to continue to report any other bugs you may find.