Bug 134376 - sw_single hangs after source change.
Summary: sw_single hangs after source change.
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Michael Andres
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-18 11:33 UTC by Stanislav Brabec
Modified: 2007-01-26 22:37 UTC (History)
1 user (show)

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

Attachments
y2log (124.08 KB, text/plain)
2005-11-18 11:36 UTC, Stanislav Brabec 		Details
IS_CACHE_0x00000001.tar.bz2 (264.78 KB, application/x-bzip-compressed-tar)
2005-11-18 12:19 UTC, Stanislav Brabec 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Brabec 2005-11-18 11:33:44 UTC 
How to reproduce:

1. Add ftp://ftp.suse.com/pub/suse/i386/supplementary/GNOME/update_for_10.0/yast-source/ to YaST sources. Turn on source and refresh.

2. Go to package manager and exit.

3. Wait 4 days. Supplementary FTP will most probably have some updates after 4 days.

4. Run package manager.

You will see refreshing messages, and then YaST2 will stay forever in phase of reading information about packages.

Work-around: Kill YaST and run again. It will complete.
Comment 1 Stanislav Brabec 2005-11-18 11:36:46 UTC 
Created attachment 57715 [details]
y2log

Log of hung session.
Comment 2 Michael Andres 2005-11-18 11:42:31 UTC 
How long did you wait until killing YaST? Looks like it hangs in libcurl trying to get the packages.en file.
Comment 3 Stanislav Brabec 2005-11-18 11:48:54 UTC 
35 minutes. Next time it finished in 15 seconds. I was able to repeat this problem at least 4 times (2 machines, 2 supplementary repository changes). The behavior seems to be repeatable and does not depend on actually selected mirror.
Comment 4 Michael Andres 2005-11-18 12:01:11 UTC 
But no further problems, once the data are retrieved? I wonder if this might be related to bug #133708.

Could you please tar and attach /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000001
(the DATA and DESCRIPTION subdirs).
Comment 5 Stanislav Brabec 2005-11-18 12:19:46 UTC 
Created attachment 57717 [details]
IS_CACHE_0x00000001.tar.bz2

I see no problem after killing YaST and running it again. It is able to install all new packages.

Note that this bug was hidden up to last week, when I started updating of timestamp in media.1/media in supplementary snapshots (on your mail advice).
Comment 6 Michael Andres 2005-11-18 13:29:40 UTC 
Before this, YaST never attempted to reload the metadata. But the metadata are ok, and reloading in general works as well. Don't know yet what's special about the GNOME repository.
Comment 7 Michael Andres 2007-01-26 22:37:55 UTC 
Meanwhile download is abortable and we have a download timeout. So there is no more need to kill YaST if download hangs. Closing this.