YaST2 Segmentation Fault - unresolved

Suddenly, whenever I attempt to use yast2 --install, or even yast2 --update,
I get the following error:

“YaST got signal 11 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187
/sbin/yast2: line 386: 4728 Segmentation fault $ybindir/y2base $module “$@”
“$SELECTED_GUI” $Y2_GEOMETRY $Y2QT_ARGS”.

zypper is broken as well, infact whenever I issue a zypper --command, I receive
a “segmentation fault”

I tried several recovery methods to correct the issue, as deleting
/var/cache/zypp/zypp.db and rebuilding my rpm db with rpmbuild --rebuilddb,
without any success.

These are the pkg versions currently in use:
yast2-2.15.58-12
yast2-core-2.15.13-0.1
zypper-0.8.26-0.1
libzypp-3.27.2-0.1
rpm-4.4.2-140
deltarpm-3.4-36
rpm-python-4.4.2-164

Which version of OpenSuSE do you use?

I’m using OpenSuSE 11.0 with the following versions of your mentioned packages:

yast2-2.16.71-6.1
yast2-core-2.16.51-6.1
zypper-0.11.10-0.2
libzypp-4.27.1-0.1
rpm-4.4.2-199.1
deltarpm-3.4-78.1
rpm-python-4.4.2-247.1

A segmentation violation upon base software means that something is really bad with your configuration. Such an error message is an example of meaningless unfriendly error messages. I think that EVERY operating system can confront the user with it. I hate segmentation fault that bad as an invalid page fault from Windows 9X. :wink:

The s…t thing is that updating seems impossible due to that nasty s…tty segmentation violation.

I’ve met such an error upon base software as well, because I’ve used 3 memory bars of different sizes on an old Pentium III. Replacing to 3 equal sized memories resolved the problem.

Overclocking might also cause a Linux PC to flip.

Maybe this can help you.

Hi Tom2k,
I am using openSUSE 10.3.

I red something related to HW malfunctions as memory, could cause segmentation faults.

One time I used memtest by using installation DVD, but I stopped that test just before the full completation.

My machine is a 64bits AMD Turion MK36 laptop, with 2GBRAM; it is only 6 months old and I never opended it to change memory or other internals parts, so I don’t believe that my problem is caused by faulty HW.
In any case I thank you very much for your comments.