https://bugzilla.novell.com/show_bug.cgi?id=732799 https://bugzilla.novell.com/show_bug.cgi?id=732799#c0 Summary: yast2 websearch(webpin) throw error 404 - could not connect so server Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: melchiaros@aol.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=464103) --> (http://bugzilla.novell.com/attachment.cgi?id=464103) logs - yast,messages,zypper, many more User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I´ve started the yast2 websearch(called webpin as far as I know), from the yast2 install dialog over the configuration menue.->search for packages in web(german: Suce nach Paketen im Web..). The search dialog comes up properly, but the search itself(boinc) gives a error message: error 404 could not connect to server. May be that the problem is a bit on my side Reproducible: Always Steps to Reproduce: 1.start yast2 installation/deinstallation module 2.use menu configuration -> search for packages in web ..(Suche nach Paketen im Web..) 3.see the websearch dialog coming up 4.search for boinc 5.see the error Actual Results: No working yast2 package search in web with error 404 could not connect to server. Expected Results: yast2 package search in web should be able to connect to server May be that the problem is a bit on my side: I´ve a disconnection with atk9k wireless driver(bug -> filed ) and brought on a god old cable connection with setting up eth0 with yast2->Networkadministration module. That all in the same session. So may be the websearch has only recognized the broken wlan and not recognized the working eth0. -> When it is like that yast2 should also be able to handle this with success. -- 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.