After refreshing the repos, but before I can install or update, Yast crashes with a segfault.
I can update with zypper so its not really a problem, but I’m also having trouble with plasma widgets crashing plasma.
I have Suse 11.0 with KDE4.2 using KDE4 factory repos running on an Acer laptop dual booting with Vista. I have these problems now and again and it doesnt’ bother me. I’ve just never had trouble with Yast updater segfaulting.
I did a search here and on google and couldn’t find much.
>
> After refreshing the repos, but before I can install or update, Yast
> crashes with a segfault.
>
> I can update with zypper so its not really a problem, but I’m also
> having trouble with plasma widgets crashing plasma.
>
> I have Suse 11.0 with KDE4.2 using KDE4 factory repos running on an
> Acer laptop dual booting with Vista. I have these problems now and
> again and it doesnt’ bother me. I’ve just never had trouble with Yast
> updater segfaulting.
>
> I did a search here and on google and couldn’t find much.
>
> Any ideas??
>
>
I had the same problem recently, and found it to be related to Qt. If
you have updated Qt to 4.4.90 from Qt repo, you should try to revert to
Qt 4.4.0 from Update repo.
>
> Rolf Lien;1946012 Wrote:
>> Psquared wrote:
>>
>> >
>> > After refreshing the repos, but before I can install or update,
>> > Yast crashes with a segfault.
>> >
>> > I can update with zypper so its not really a problem, but I’m also
>> > having trouble with plasma widgets crashing plasma.
>> >
>> > I have Suse 11.0 with KDE4.2 using KDE4 factory repos running on an
>> > Acer laptop dual booting with Vista. I have these problems now and
>> > again and it doesnt’ bother me. I’ve just never had trouble with
>> Yast
>> > updater segfaulting.
>> >
>> > I did a search here and on google and couldn’t find much.
>> >
>> > Any ideas??
>> >
>> >
>> I had the same problem recently, and found it to be related to Qt. If
>> you have updated Qt to 4.4.90 from Qt repo, you should try to revert
>> to
>> Qt 4.4.0 from Update repo.
>
> How did you downgrade to Qt 4.4.0 without yast? Did you use zypper and
> how did you go about it? Did it remove any other programs or
> dependencies.
>
> I like having 4.2. In fact, parts of it are almost to 4.3. Lots of
> bugs, but most are minor.
>
>
YaST2 has a problem, but not YaST.
Open a console, or start a cli session and start yast. I got no
dependency problems, but I should mention that I’m still on 3.5.10.
Still getting segfaults. Probably because I’m too bleeding edge. But out of curiosity, why doesn’t sudo rpmdb --rebuilddb work for me? I’ve run it several times and it seems to finish, but yast still segfaults.
Maybe it will be fixed in a later update. Or maybe I should update to 11.1 and drop “factory” for a more stable system?
>
> Still getting segfaults. Probably because I’m too bleeding edge. But
> out of curiosity, why doesn’t sudo rpmdb --rebuilddb work for me? I’ve
> run it several times and it seems to finish, but yast still segfaults.
>
> Maybe it will be fixed in a later update. Or maybe I should update to
> 11.1 and drop “factory” for a more stable system?
>
>
How do you know rpmdb --rebuilddb fails? Your segfault isn’t necessarily
caused by problems with rpmdb. If an incompatible version of Qt is the
problem, as it was in my case, you must restart your GUI to see any
change. (If you started YaST from a console.)
I am assuming it fails because it does not show any result. Maybe it is not supposed to - I don’t know.
BTW, I am doing all of this within the GUI. I start YaST using “Adminstrator Mode” from the menu. Should I exit the GUI and the Xserver and do it from the CLI?
I’ve had the same problem with YaST (from a console login) and from YaST2 trying it on both KDE and Gnome desktops.
It seems to go through the processes of “Reading Installed Packages” then “Reading the repository cache” fine then crashes. If I’m using a console login the software module next exits back to the YaST front end. Otherwise, if I’m using a GUI then I get a segmentation fault with an X-message to that effect. It looks exactly like Bug 461136 on the Novell Bugzilla which was posted on 20/12/'08.
It’s a bit frustrating but I guess we have to wait for a bug fix and use rpm from a console for the time being.
I fixed it by a fresh install of Suse 11.1. KDE4.1.3 is much more stable and I did not enable the factory repos. Now I get maybe 20-30 mb of updates a week. Completely tolerable. Only problem is KDE4 networking still isn’t quite where it needs to be so still using the KDE3 version.
>
> I’ve had the same problem with YaST (from a console login) and from
> YaST2 trying it on both KDE and Gnome desktops.
>
> It seems to go through the processes of “Reading Installed Packages”
> then “Reading the repository cache” fine then crashes. If I’m using a
> console login the software module next exits back to the YaST front end.
> Otherwise, if I’m using a GUI then I get a segmentation fault with an
> X-message to that effect. It looks exactly like Bug 461136 on the Novell
> Bugzilla which was posted on 20/12/'08.
>
> It’s a bit frustrating but I guess we have to wait for a bug fix and
> use rpm from a console for the time being.
>
>
I am having same problem on my older 32 bit openSUSE 11.0 system. I tried
total install of YaST but it did not help. This occurred after doing a KDE
update ( KDE3.5.9). My other system (64 bit) with openSUSE 11.1 KDE 4.2
release 104 has not had this problem.
I can enter YaST from the command line and everything works. If I try the
GUI or zypper on the 32 bit system I get the SegFault message after it reads
the packages and updates the repositories.
