yast fatal error - help?

hi when i tried to update software (opensuse 11.1 on an x64 bit Dell inspiron 530), i had a fatal error - the update software menu would not even open!

here is the error message (which i dont understand)

YaST got signal 11 at YCP file /usr/share/YaST2/clients/online_update_select.ycp:105
/sbin/yast2: line 437: 26036 Segmentation fault $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS

any ideas how 2 proceed?

c’mon guys help us out - my wife (whose PC this is about) is a linux newbie and is starting to complain & wants 2 return 2 windoze … dont let this happen! :wink:

the problem i reported on occurred after an attempted software upgrade which she interrupted by mistake - however this really should not lead to an inability 2 open the software installer at all!

help! thanks! will post any log file to any length and also dance it 4 you if I must :wink:


What repo’s do you have marked?

Is it more than OSS. NON-OSS, Packman and update? If so go back to them have you updated kde4 as far as I know and googling or searching here ti is due to qt4.5 which isn’t on any normal repo. And you would need to roll that or qt-yast back etc …

Segmentation error crash in YaST2 Software Management module - openSUSE Forums

zypper verify

Type this in a terminal as root. If there are some dependency problems, zypper should offer to install the needed packages.

If you need more help, post the output here.

thank you very much! apart from an x server problem (i have to figure out how to send a bug report which i am asked 2 do but not how!) this settled it! after zypper i was offered several solutions and i chose the downgrading one.

birkenkrahe wrote:
> (i have to figure out how to send a bug report which i am asked 2
> do but not how!)

look on the opening page for opensuse.org
<http://en.opensuse.org/Welcome_to_openSUSE.org> and find the section
named “Report a Bug” where you find links to:

a bug faq <http://en.opensuse.org/Bug_Reporting_FAQ>
and, HOW to submit <http://en.opensuse.org/Submitting_Bug_Reports>

no “figuring out” required, just a little reading.