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

[KurtKrueckeberg]

While trying to downgrade from 11.10 to 11.04, the installation crashed. Thereupon, after 11.04 was booted from the CD, this second error ocurrred, which prompted me to file a bug report.

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: Fri Oct 14 10:25:30 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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Steffen Röcker (sroecker)]

Line 125 should be:
next_check = int(time.time()) + 7*24*60*60

[betweenbrain (matt-betweenbrain)]

Steffen - would you like this to be tested? If so, can you provide some basic test instruction. I am new to Ubuntu bug reporting, but would be happy to help.

[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.

[Daniel Kelly (dkellyhome)]

Great! However I don't know how to or what to provide you.

I can however tell you how this problem occurred.

I have natty (11.04) and I received a notice that I can upgrade. So I tried.

After about 12 hours of downloading, it ended with a screen (terminal
screen) that had some
code written on it which ended with a storage battery check (of which
doesn't apply to my
desktop machine) and it stopped there. It wouldn't even recognize a sudo
command saying
something like there was no such command. It just kept saying it was
running, then overnight
I stopped it.

On 10/17/2011 03:39 AM, betweenbrain wrote:
> Steffen - would you like this to be tested? If so, can you provide some
> basic test instruction. I am new to Ubuntu bug reporting, but would be
> happy to help.
>

--
*Dan Kelly*

[Daniel Kelly (dkellyhome)]

How do I get there?

On 10/17/2011 01:30 AM, Steffen Röcker wrote:
> Line 125 should be:
> next_check = int(time.time()) + 7*24*60*60
>

--
*Dan Kelly*

[Daniel Kelly (dkellyhome)]

Are you talking about the startup of the upgrade?

On 10/16/2011 11:19 PM, Jean-Baptiste Lallement wrote:
> ** Visibility changed to: Public
>

--
*Dan Kelly*