Bug#379323: mesa-utils: glxinfo does not report library open problems
On Sat, 2006-07-22 at 15:48 -0400, Marc MERLIN wrote:
>
> libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)
> libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so
> libGL error: dlopen /usr/X11R6/lib/modules/dri/fglrx_dri.so failed (/usr/X11R6/l
> ib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or dir
> ectory)
> libGL error: unable to find driver: fglrx_dri.so
>
> This was due to a packaging bug,
Which I hope has been reported as well?
> which I fixed with a simple symlink in about 30 seconds, but I would really
> really have liked for glxinfo to tell me that it couldn't open the driver
> and that's why I was still getting Mesa. Please consider making
> LIBGL_DEBUG=verbose or equivalent, a default to help out the countless
> people on the net like me who have spent too much time tracking this problem.
The reason why these errors are not printed by default is that this can
be perfectly normal and not cause any problems under some circumstances,
e.g. when connecting to a remote X server that supports GLX.
Maybe glxinfo could still provide a clue though, such as output that
goes something like 'Setting the environment variable
LIBGL_DEBUG=verbose may help find out why direct rendering is disabled'.
Do you think that would be useful?
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: