Bugzilla – Bug 115911
OpenGL applications segfault with VIA driver
Last modified: 2006-02-13 11:47:31 UTC
Segfault with "via" driver since beta4. On beta3 GL applications work fine. RC1 is still affected. reproduce with glxgears, glxinfo, KDE OpenGL Screensaver ... as user. root is not affected. Machine: Maxdata M-book 1200X I'll submit hwinfo and X log. Are/which other log(s) needed?
Created attachment 49241 [details] hwinfo hwinfo output
Created attachment 49242 [details] X log
Sure, that your user is in group video?
Critical --> Major.
user is in group video: tux@g173:~> id tux uid=1000(tux) gid=100(users) groups=100(users),16(dialout),33(video) tux@g173:~> glxgears Segmentation fault tux@g173:~> do you need other logs?
Yes, I think so. Results of: 1) LIBGL_ALWAYS_INDIRECT=1 glxinfo 2) gdb /usr/X11R6/bin/glxinfo (install gdb package for this) run bt
Created attachment 49337 [details] LIBGL_ALWAYS_INDIRECT=1 glxinfo
Created attachment 49338 [details] gdb /usr/X11R6/bin/glxinfo ...
Ok. It would be an option to set LIBGL_ALWAYS_INDIRECT by default when via driver is in use by adding /etc/profile.d/via.{sh,csh}. via.sh: ------- if [ -f /var/log/Xorg.0.log ]; then grep -q \"via\" /var/log/Xorg.0.log if [ $? -eq 0 ]; then export LIBGL_ALWAYS_INDIRECT=1 fi fi via.csh: -------- if ( -f /var/log/Xorg.0.log ) then grep -q \"via\" /var/log/Xorg.0.log if ( $? == 0 ) then setenv LIBGL_ALWAYS_INDIRECT 1 endif endif
I'll do so. Fixed for RC2.
works fine.
This is no longer needed for 10.1 Beta3. Tested with same machine ( Maxdata M-book 1200X ) without workround.
Ok. Will change this for Beta4. Thanks for the feedback!
New problem with Maxdata M-book 1200X without LIBGL_ALWAYS_INDIRECT. glxinfo and glxgears and several GL screensaver works, but krandom.kss will freeze the X until krandom.kss will be killed. calling the single KDE GL screensaver works too - only krandom.kss is freezing and crashing. Setting LIBGL_ALWAYS_INDIRECT=1 works for krandom.kss Is this an krandom.kss problem or a via module problem? I try to get a backtrace of crashing krandom.kss Reenabling the old workaround? Reopen this bug? New bug assigend to?
Ok. I think I should better reenable the workaround. :-(
changed for Beta4.