I realize Yast has always been buggy, but it has gotten much, much worse
the last 2 days. This is will v11.0
It keeps bouncing between different versions of firefox, xine(between
the worthless one that it ships with and the one on packman), and other
applications. But it always does this BS, but is now unusable.
The automatic update feature won’t update because the resolver is
broken, and I can’t even open software management in Yast because of a
seg fault: YaST got signal 11 at YCP file
/usr/share/YaST2/clients/inst_packages.ycp:36
/sbin/yast2: line 421: 21134 Segmentation fault $ybindir/y2base
$module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARG
Using zypper just breaks more apps. This is not the way to encourage
upgrading to 11.1
vilanye;1910045 Wrote:
> It keeps bouncing between different versions of firefox, xine(between
> the worthless one that it ships with and the one on packman), and other
> applications. But it always does this BS, but is now unusable
> …
> Using zypper just breaks more apps. This is not the way to encourage
> upgrading to 11.1IMHO this is a problem specific to your setup.
Possibly you have an inappropriate selection of repos, or your zypper
or rpm database is corrupted.
I would agree if it weren’t for the fact I have seen this behavior on
several systems, and it is well known this is a problem all around.
Putting the blame on me, because Yast wasn’t built correctly, doesn’t
help.
Yast should be smart enough not to offer up any incompatible repos.
None of this has anything to do with a seg fault, so the problem can’t
be fixed, if it is my fault. You did know that if the opensuse updater
runs into a resolver problem it just gives up quietly, don’t you?
vilanye;1910062 Wrote:
> I would agree if it weren’t for the fact I have seen this behavior on
> several systems, and it is well known this is a problem all around.
> Putting the blame on me, because Yast wasn’t built correctly, doesn’t
> help.The intention is to help you.
I do think you should take a look again at what I suggested.
I run several systems. I do not have this problem. This is NOT a
problem all around.
What is the output of:::zypper lr::on each of your
systems that have this problem? What have you done to check if you have
a corrupted database? Following the same systemic practise on each
system can lead to the same systemic problem on each system.
"
I run several systems. I do not have this problem. This is NOT a
problem all around."
So if you don’t have a problem it isn’t common? Look outside of
opensuse websites and learn the truth about zypper and Yast in general.
caf4926,
Thanks for your legitimate help. Too bad it didn’t work. A seg fault
shouldn’t have anything to do with a misbehaving repo. I guess the only
thing to do is to go back to 10.2, when YAST was reliable or find
something that hasn’t been bloated up. Thanks again.
vilanye;1926856 Wrote:
> So if you don’t have a problem it isn’t common? Look outside of opensuse
> websites and learn the truth about zypper and Yast in general.If it was as common as you note, I (or one of my colleagues) would have
encountered it. I have installed 11.1 on 4 completely different
systems, and I have exchanged emails/PMs with over a dozen users who
have also installed 11.1 on many systems. I would have seen a lot of
mention of it … and YES, I have surfed and this is not common.
IMHO you have encountered a systemic problem associated with the
specifics in terms of how you have set things up. I’m not saying you
have done something incorrect, but I am saying you have systemically
done something different to bring your problem about. I think you
should focus on what you are doing to come up with a cause and effect.