http://bugzilla.novell.com/show_bug.cgi?id=487559
User alpha096@virginbroadband.com.au added comment
http://bugzilla.novell.com/show_bug.cgi?id=487559#c16
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |CLOSED
Info Provider|alpha096@virginbroadband.co |
|m.au |
Resolution| |INVALID
--- Comment #16 from Scott Couston 2009-04-10 14:24:32 MDT ---
Unknown reason for output in #10-12 - however RPM database was rebuild and all
is in order now.....
The Online update - error message was only indicated when Patch
'libpurple - libpurple: Fix connecting to ICQ of pidgin and finch
Fixes connecting of pidgin and finch to ICQ.
References:
483744 (bugzilla) : bug number 483744'
tried to be installed via Updater Applet OR using Yast>Online Update
Unknown reason why this patch failed to download correctly.....Error response
was always
"Download Failed with xxxxx Bytes Remaining ?
Abourt/Retry/Cancell ?"
Continual retry only reinstates this error.....The presumption for the reason
it failed was that a Time Out factor was applied and the download failed, due
to this value being reached....
It is very common for patch updates to time out either via Yast OR Update
Applet in KDE since V10.2....Many patch updates require user intervention of
'Retry' when installing patches.
The Exact reason why many many Online Patches, since V 10.2, required Retry of
download is presumed to be a "Time Out Value" being reached. - No clear answer
to this.
Yast.de always respond with "There is NO time out Value Set" and this is not
the reason for the 'Retry'
Most all 'Retry' that I have to interveneD with will eventually download and
install correctly. However the libpurple patch could never ever be downloaded
and installed due to ? and has been marked by user as Taboo.
Other Patch updates installed correctly and a few "Retry" interventions were
required but successful.
The 'Retry' since V10.2 seems only to affect me in .AU, however *Every* Gnome
Installations do not ever produce a "Retry" event.
CONCLUSION:-
As this Retry only appears to effect me here in .AU and Only KDE since 10.2, No
reasonable reason why this occurs has ever been previously acknowledged by
Suse.DE and I cannot provide ANY definitive and reproducible environment which
can ever be re-created at Suse.De or via Logs.
Errors #10-12 were fixed by successful re-build of rpm database and have been
eliminated as cause.
Close as INVALID DUE TO CONCLUSION ABOVE
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.