|
Bugzilla – Full Text Bug Listing |
| Summary: | sw_single hangs after source change. | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Stanislav Brabec <sbrabec> |
| Component: | YaST2 | Assignee: | Michael Andres <ma> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.hanke |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2log
IS_CACHE_0x00000001.tar.bz2 |
||
|
Description
Stanislav Brabec
2005-11-18 11:33:44 UTC
Created attachment 57715 [details]
y2log
Log of hung session.
How long did you wait until killing YaST? Looks like it hangs in libcurl trying to get the packages.en file. 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. 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). 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).
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. Meanwhile download is abortable and we have a download timeout. So there is no more need to kill YaST if download hangs. Closing this. |