Bug 113613 - Download fetchmsttfonts.sh and fetchnvidia.sh failed
Summary: Download fetchmsttfonts.sh and fetchnvidia.sh failed
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: HP All
: P5 - None : Normal
Target Milestone: ---
Assignee: Michael Radziej
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-28 09:27 UTC by Ulrich Lange
Modified: 2005-09-13 07:14 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
YaST2 logs (145.11 KB, application/x-gtar)
2005-08-28 21:01 UTC, Ulrich Lange
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Lange 2005-08-28 09:27:50 UTC
During Installation process hangs in window "Patch Download and Installation".
Last entry in Progress Log was: Installing fetchmsttfonst.sh "Download
Microsoft(r) TrueType Core Fonts".
Patch Progress shows 99%
Total Progress shows 50%
After a short time of network and disk aktivity process hangs.
After press Abort button messages "No patch have been installed" was shown.
I could continue the installation process without any following problems.
Comment 1 Christoph Thiel 2005-08-28 09:59:21 UTC
Please provide y2logs as described in
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST
Comment 2 Ulrich Lange 2005-08-28 21:01:57 UTC
Created attachment 47911 [details]
YaST2 logs

YaST tried to make a download from ftp.riken.jp/linux/suse/suse
and this information was shown before starting download:
./i386/update/10.0/patches
2 new updates
Comment 3 Klaus Kämpf 2005-08-29 12:55:16 UTC
Cornelius, Michael is on vacation. Can you have a look please ? 
Comment 4 Michael Radziej 2005-09-12 11:29:20 UTC
The patches are actually scripts that only fetch data from other servers.
Sometimes these are overloaded, then it can really take forever, but
unfortunately  this is beyond our control. Can you please try again now and tell
us whether this helped?
Comment 5 Ulrich Lange 2005-09-12 20:34:38 UTC
I had this problem only with beta 3. Since Beta 4 it´s working well. I thought
someone has fixed it. However, I think we can close this BUG.
Comment 6 Michael Radziej 2005-09-13 07:14:04 UTC
Thanks!