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

[ALFIN SYAMSUDDIN]

when upgrade dialog pop up and i clicked the button "ask me later" it hangs up

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150.3
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Fri Oct 14 08:54:18 2011
ExecutablePath: /usr/lib/update-manager/check-new-release-gtk
GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/first_run=false
 /apps/update-manager/show_details=true
 /apps/update-manager/window_size=(511,600)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
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: Upgraded to natty on 2011-05-09 (157 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev root sambashare tape vboxusers video www-data

[Apport retracing service (apport)]

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 #873728, 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.