https://bugzilla.novell.com/show_bug.cgi?id=853016 https://bugzilla.novell.com/show_bug.cgi?id=853016#c0 Summary: Online update hangs with IPv6 when WAN is IPv4 only Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.5 Safari/534.34 Running yast online update results in a random server to be selected. Some of these servers are IPv6 capable. My ISP and WAN are not. The default openSUSE configuration is to always enable IPv6, and there are use cases for doing this even with an IPv4-only WAN (the LAN for example has no such limitation). And it is the default setting. So the situation is: * Yast times out every 30s with a network error, until clicking "skip" on this repo, for every single repo worst case. * There is no "cancel" button. * Clicking the window's "close" button brings up a "terminate this application"; clicking yes does nothing. So the user has an obnoxious application that does only offline "updates", keeps on wasting time, AND does not take "bugger off" for an answer! Updating the system is impossible with this. Reproducible: Always Steps to Reproduce: 1. Use WAN that is IPv4 only. Use LAN that is IPv6 capable (e.g. from default openSUSE installs). 2. Run online update. 3. Repeat until a IPv6 updates server is selected. Actual Results: Yast times out with a network error every 30s, until clicking "skip". Yast times out with a network error with the next repository, every 30s, until clicking skip. Yast keeps on doing nothing useful until the last repo has been dealt with. Expected Results: Update server being addresses in IPv4 when IPv6 doesn't work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.