From a user perspective I've been able to try a few tests today that led to some more info. Don't know if it will help but it concerns the Repositories
https://bugzilla.novell.com/show_bug.cgi?id=464214 User david.casson@ntlworld.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464214#c22 --- Comment #22 from David Casson <david.casson@ntlworld.com> 2009-03-20 14:14:34 MST --- that are configured and enabled. After reading a few posts on the open SuSE forums it seemed some users had a degree of success with changing configured repositories. So I gave it a try and disabled all of mine except Packman.org and the problem is still there. - Segfault as soon as yast2 tries to build the repository cache. Next I tried disabling all repositories and apart from a whinge about no repositories I go no segfault crash! (The first time I've seen yast software management working on this machine since the beginning of the year.) So I next tried just enabling the Main (OSS) repository at download.opensuse.org with complete success. yast also now works from a root console login (TRL-ALT-F2). Further investigation revealed that the following repositories work in either the X11 GUI or on a console login: Main Repository (OSS) Main Repository (Non-OSS) Open Office for SuSE 10.3 STABLE Virtualisation: VirtualBox SuSE 11.1 The following would apparently work as far as setting up the repository details and enabling them but all caused the software management module to segfault in either the X11 GUI or on a console login. I included trying various different mirrors and protocols but to no avail. Open SuSE : Tools Mozilla Packman Repository VideoLan Repository Packman (Unixheads.org) Updates Repository (SuSE 10.3) When the cause is discovered it would be great if someone could give a brief guide for the inexperienced to implement the fix as many relaatively new users seem to have lost the yast functionality to apply any update through this bug so perhaps it is also (IMHO) worth considering an upgrade of the current importance of the bug to somewhat higher than 4 . -- 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.