[opensuse-factory] YaST2 crashes in 13.2 m0
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:~ # -- Graham Davis, Bracknell, Berks. openSUSE 13.1 (64-bit); KDE 4.12.3; AMD Phenom II X2 550 Processor; Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 21 Mar 2014 09:03:25 +0000 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:~ #
I've been informed of the bug report on this, https://bugzilla.novell.com/show_bug.cgi?id=866692, and have added another comment as, although the provided fix works, YaST insists on re-installing the dodgy module. -- Graham Davis, Bracknell, Berks. openSUSE 13.1 (64-bit); KDE 4.12.3; AMD Phenom II X2 550 Processor; Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Graham P Davis <hacker@scarlet-jade.com> writes:
I've installed debuginfo modules for YaST but these did nothing apparently.
What does "did nothing" mean? What did you expect to get? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 24 Mar 2014 08:14:52 +0100 Andreas Schwab <schwab@suse.de> wrote:
Graham P Davis <hacker@scarlet-jade.com> writes:
I've installed debuginfo modules for YaST but these did nothing apparently.
What does "did nothing" mean? What did you expect to get?
That's embarrassing. Have you ever written something that you thought made sense at the time but, on reflection, you realised was complete nonsense? I've no idea why I expected anything to happen from installing the debuginfo modules. I think I'll blame it on a "senior moment" - again. -- 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
El 21/03/14 06:03, Graham P Davis escribió:
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)
Hrmmm.. what is going on there.. if /usr/lib64/dri/updates/nouveau_dri.so fails to load but /usr/lib64/dri/nouveau_dri.so succeeds then no error should be printed...looks like a bug to me. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, the misleading error message is only printed when GL_DEBUG is set, so it is not as bad as it seems. I have created a small patch which should clarify the situation, see https://build.opensuse.org/package/show/home:StefanBruens:branches:X11:XOrg/... Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 24/03/14 12:06, Brüns, Stefan escribió:
Hi,
the misleading error message is only printed when GL_DEBUG is set, so it is not as bad as it seems.
I have created a small patch which should clarify the situation, see https://build.opensuse.org/package/show/home:StefanBruens:branches:X11:XOrg/...
0001-log-successful-dlopens-when-dlopen-errors-where-logg.patch --> that looks fine to me, thanks ! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 24.03.2014 16:06, schrieb Brüns, Stefan:
Hi,
the misleading error message is only printed when GL_DEBUG is set, so it is not as bad as it seems.
I don't have GL_DEBUG set, but still see the message: seife@susi:~> env |grep GL_ seife@susi:~> glxgears libGL error: dlopen /usr/lib64/dri/updates/i965_dri.so failed (/usr/lib64/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory) Running synchronized to the vertical refresh. The framerate should be (yes, not related to the original problem) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Stefan unfortunately the behaviour of LIBGL_DEBUG does not match the documentation: ./docs/libGL.txt:stderr if the LIBGL_DEBUG environment variable is defined. ./docs/envvars.html:<li>LIBGL_DEBUG - If defined debug information will be printed to stderr. whereas: < from src/loader/loader.h > #define _LOADER_FATAL 0 /* unrecoverable error */ #define _LOADER_WARNING 1 /* recoverable error/problem */ #define _LOADER_INFO 2 /* just useful info */ #define _LOADER_DEBUG 3 /* useful info for debugging */ ----- < from src/glx/dri_common.h > #define InfoMessageF(...) dri_message(_LOADER_INFO, __VA_ARGS__) #define ErrorMessageF(...) dri_message(_LOADER_WARNING, __VA_ARGS__) #define CriticalErrorMessageF(...) dri_message(_LOADER_FATAL, __VA_ARGS__) ----- < from src/glx/dri_common.c > _X_HIDDEN void dri_message(int level, const char *f, ...) { va_list args; int threshold = _LOADER_WARNING; const char *libgl_debug; libgl_debug = getenv("LIBGL_DEBUG"); if (libgl_debug) { if (strstr(libgl_debug, "quiet")) threshold = _LOADER_FATAL; else if (strstr(libgl_debug, "verbose")) threshold = _LOADER_DEBUG; } /* Note that the _LOADER_* levels are lower numbers for more severe. */ if (level <= threshold) { fprintf(stderr, "libGL%s: ", level <= _LOADER_WARNING ? " error" : ""); va_start(args, f); vfprintf(stderr, f, args); va_end(args); } } ----- So setting LIBGL_DEBUG=quiet will lower verbosity in the loader but increase it for the rest of the library. Also, by default the transient error for the nonexistent driver in .../updates/ will be printed on openSUSE. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Schwab -
Brüns, Stefan -
Cristian Rodríguez -
Graham P Davis -
Stefan Seyfried