On Mon, 24 Mar 2014 10:22:46 +0100 Richard Brown <RBrownCCB@opensuse.org> wrote:

On 21 Mar 2014 10:03, "Graham P Davis" <hacker@scarlet-jade.com> wrote:

...

Installed 13.2 m0 yesterday and found YaST2 failed in "Software Management" module after selecting packages to install and continuing. Ran from console when logged on as "root" and got the following messages:

linux:~ # yast2 "Qt Warning - invalid keysym: dead_actute" libGL error: dlopen /usr/lib64/dri/updates/nouveau_dri.so failed

(/usr/lib64/dri/updates/nouveau_dri.so: cannot open shared object file: No such file or directory)

...

Run command: /sbin/yast2 sw_single & libGL error: dlopen /usr/lib64/dri/updates/nouveau_dri.so failed (/usr/lib64/dri/updates/nouveau_dri.so: cannot open shared object file: No such file or directory) YaST got signal 11 at YCP file /usr/share/YaST2/modules/SlideShow.rb:385 /sbin/yast2: line 429: 4522 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS linux:~ #

When I tried this as a normal user, I could not get any messages.

I've installed debuginfo modules for YaST but these did nothing apparently.

Just tried again and the problem has worsened in that the crash occurs as soon as "Software Management" is selected.

linux:~ # yast2 "Qt Warning - invalid keysym: dead_actute" libGL error: dlopen /usr/lib64/dri/updates/nouveau_dri.so failed (/usr/lib64/dri/updates/nouveau_dri.so: cannot open shared object file: No such file or directory) Run command: /sbin/yast2 sw_single & libGL error: dlopen /usr/lib64/dri/updates/nouveau_dri.so failed (/usr/lib64/dri/updates/nouveau_dri.so: cannot open shared object file: No such file or directory) YaST got signal 11 at YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:2159 /sbin/yast2: line 429: 5103 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS linux:~ #

Hi there,

I cant reproduce this on my M0 installation, but I'm using GNOME - so I suspect you might be able to run yast2 --gtk to workaround the issue for now.

Hope this helps,

Thanks, Richard, but the problem has been fixed by removing libproxy1-config-kde4 and then tabooing it. If it is not tabooed, YaST insists on re-installing it (as, by the way, it also does for Apper and Packagekit). See https://bugzilla.novell.com/show_bug.cgi?id=866692 -- Graham Davis, Bracknell, Berks. openSUSE 13.2-m0 (64-bit); KDE 4.12.2; AMD Phenom II X2 550 Processor; Kernel: 3.14.0-rc5; Video: nVidia GeForce 210 (using nouveau driver); Sound: ATI SBx00 Azalia (Intel HDA) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org