After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 98615 - under/overflow in download window
under/overflow in download window
Status: RESOLVED FIXED
Product: galeon
Classification: Deprecated
Component: User interface
1.3.0
Other other
: Normal normal
: 2.0
Assigned To: galeon-maint
galeon-maint
: 109786 127612 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-11-15 15:50 UTC by Mark Howard
Modified: 2005-12-29 16:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
shot of download dialog with bug visible (26.35 KB, image/png)
2004-02-03 20:29 UTC, Robert Holmberg 		Details

Description Mark Howard 2002-11-15 15:50:15 UTC 
The following was reported in the Debian bts, #169202

Package: galeon-snapshot
Version: 1.3.0.20021110-1
Severity: minor

At http://treebeard.tolkien.dk/~boll/snapshot3.png I have put a
screenshot, illustrating what appears to be an under or overflow of the
integer(s) holding the values used in Time Elapsed.
I am fairly certain that I havent been downloading for 4.2 billion
hours. I have done nothing out of the ordinary to provoke the error.
Comment 1 Crispin Flowerday (not receiving bugmail) 2003-08-22 21:01:06 UTC 
*** Bug 109786 has been marked as a duplicate of this bug. ***
Comment 2 Crispin Flowerday (not receiving bugmail) 2003-11-21 18:05:38 UTC 
*** Bug 127612 has been marked as a duplicate of this bug. ***
Comment 3 Robert Holmberg 2004-02-03 20:29:51 UTC 
Created attachment 24035 [details]
shot of download dialog with bug visible
Comment 4 Robert Holmberg 2004-02-03 20:31:53 UTC 
Selecting another file and then selecting the file with the funny
"Time elapsed" -value corrects the error. I use galeon cvs as of today
with mozilla 1.4.1.
Comment 5 Crispin Flowerday (not receiving bugmail) 2005-12-29 16:47:09 UTC 
I believe this is now fixed. If it re-occurs in versions > 2.0 please re-open.