Bug 64852 - Non fatal Gtk errors when up2date hits a package already in its cache
Non fatal Gtk errors when up2date hits a package already in its cache
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.3
i386 Linux
low Severity low
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-05-13 12:20 EDT by Alan Cox
Modified: 2015-01-07 18:56 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-15 01:27:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alan Cox 2002-05-13 12:20:58 EDT
If up2date hits a package during the download phase that is already cached, 
eg because /var/spool/up2date is shared, or from a prior up2date being killed
before finishing installing it prints

Gtk-CRITICAL **: file gtkprogress.c: line 518 (gtk_progress_set_percentage):
assertion `percentage >= 0 && percentage <= 1.0' failed.

for each such package.

This seems to have done no actual harm
Comment 1 Adrian Likins 2002-05-15 15:27:53 EDT
heh, lovely warning
Comment 2 Adrian Likins 2003-01-15 01:27:54 EST
This is fixed in the 7.3 errata.

Note You need to log in before you can comment on or make changes to this bug.