yast2 seg faults after fresh installation of opensuse 13.2

I’ve reinstalled opensuse 13.2 twice from scratch now on a DELL Latitude E6540 notebook and I keep running into the same problem. I get seg faults when using yast after updating all the installed packages to their newest versions.

If I try to launch yast from the GUI menu, then it just does not start and I get no feed back as to why.

If I try to launch yast2 as root from the shell I get:

/sbin/yast2: line 440:  4942 Segmentation fault      $y2ccbin $Y2UI_ARGS "$@"

I can launch yast (in its ncurses version) in the shell by just typing “yast”. Not having acces to the GUI version of yast is very frustrating. Does anyone have any advice?

On Thu, 01 Jan 2015 01:36:01 +0000, gonneman wrote:

> I’ve reinstalled opensuse 13.2 twice from scratch now on a DELL Latitude
> E6540 notebook and I keep running into the same problem. I get seg
> faults when using yast after updating all the installed packages to
> their newest versions.
>
> If I try to launch yast from the GUI menu, then it just does not start
> and I get no feed back as to why.
>
> If I try to launch yast2 as root from the shell I get:
>
> Code:
> --------------------
> /sbin/yast2: line 440: 4942 Segmentation fault $y2ccbin
> $Y2UI_ARGS “$@”
> --------------------
>
>
> I can launch yast (in its ncurses version) in the shell by just typing
> “yast”. Not having acces to the GUI version of yast is very frustrating.
> Does anyone have any advice?

After the installation and before running YaST, try doing an update.

You don’t have any NFS mounts defined on this system (not exports, but
remote filesystems mounted), do you? I seem to recall that that was the
cause of a similar problem when I first installed 13.2 - commenting them
out in fstab and dismounting them was necessary, but I believe the issue
is fixed in an update.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

No I don’t have any external mounts. Just one internal HD.

I’ll try installing once more an then updating directly. How do I do that? Use the KDE popup that informs me that there are updates?

OK I did yet another fresh install and then updated straight away without changing anything else. After that update yast still worked.

Then I installed the proprietary AIT fglrx drivers and after that I can’t start the yast GUI anymore. They seem to be at fault… How can that be? What do they have to do with yast2?

In this information is needed, my kernel version and ATI driver version are:

# uname -r
3.16.7-7-desktop
# zypper info fglrx64_xpic_suse132
Loading repository data...
Reading installed packages...


Information for package fglrx64_xpic_SUSE132:
---------------------------------------------
Repository: AMD/ATI Graphics Drivers
Name: fglrx64_xpic_SUSE132
Version: 14.501.1003-1
Arch: x86_64
Vendor: 
Installed: Yes
Status: up-to-date
Installed Size: 10.6 KiB
Summary: X Window display driver for the AMD graphics accelerators
Description: 
  This package is a meta package to installed fglrx-core,
  fglrx-graphics, fglrx-amdcccle and fglrx-opencl.

On Thu, 01 Jan 2015 03:06:02 +0000, gonneman wrote:

> No I don’t have any external mounts. Just one internal HD.
>
> I’ll try installing once more an then updating directly. How do I do
> that? Use the KDE popup that informs me that there are updates?

That should work, or you can drop to a terminal window and run:

sudo zypper up

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Thanks Jim.

It seems that the root of the problem is that the integrated intel graphics chip is being given priority over the ATI card.

Since this seems to be a driver/hardware problem now, I started a new thread in the hardware section of the forum.

me too had the same problem after installation of ATI/AMD drivers (but catalyst manager says me that no drivers was installed), uninstalled AMD/ATI drivers and yast worked fine,