Your message dated Sat, 17 Feb 2007 19:38:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#241922: mesag3-glide2: MESA_GLX_FX environment variable
should go
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mesag3-glide2
Version: 3.4.2.1-4
Severity: normal
Hi!
Every time I run xlock(1x), I get the following message:
| WARNING: This Mesa Library includes the Glide driver but
| you have not defined the MESA_GLX_FX env. var.
| (check the README.3DFX file for more information).
|
| you can disable this message with a 'export MESA_GLX_FX=disable'.
I'm not using any of the cards mentioned in README.3DFX. In fact, I
didn't know about some of them before I've read that file. Nor I intend
to use them. But still I have to bother with setting the MESA_GLX_FX
variable or I will be annoyed with that `warning'.
(1) Leaving the variable(s) unset should be OK, cf. e.g. POSIXLY_CORRECT
environmental variable. It's not a systematic way to _require_ setting
of an environment variable. Consider what would happen if every 3D
videocard driver used such a variable... But even if I used it, maybe I
would be not interested in using this driver. Leaving this variable
unset should result just in some default behaviour. What the defaults
should be is out of the scope of this bugreport.
(2) All in all, the `warning' should go: It's not a good idea to emit an
all-caps `WARNING'. Consider multi-luser setups with many of the lusers
not so English-proficient. The operating system should treat them
kindly, shouldn't it?
(3) And against the environment variables themselves: It is not possible
to alter environment variables of a running program (afaik), or at least
there is no legal way. But you can add videocards on-the-fly (hotplug
or suspend-coldplug-resume). So you will end up with your favourite X
window manager having variable set to some value, while your hardware
setup would require a different one. You would have to start new
session (terminal, restart the window manager, ...). Configuration
files are far more flexible.
(4) My bugreports should be less formal ;-)
Conclusion:
The use of MESA_GLX_FX environment variable as a mean of configuration
is not flexible enough, and should be replaced by e.g. configuration
file option. Leaving this variable unset should be OK, just as it is
for example for POSIXLY_CORRECT. No `WARNING' should be emitted, or at
least in mixed-caps, as it confuses oblivious users.
Cheers,
Jan.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux kontryhel 2.4.20-int-rt-uml-jan #3 SMP Thu Jul 3 03:30:43 CEST
2003 i686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8
Versions of packages mesag3-glide2 depends on:
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libglide2 2001.01.26-1.1 Graphics library for 3Dfx Voodoo b
ii xlibs 4.1.0-16 X Window System client libraries
pgpbmHtPOW4lE.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Closing since the code that handles this warning is between #ifdef FX,
but FX does not seem to be ever defined when building current mesa.
Brice
--- End Message ---
