I have no idea where this comes from, or what's causing this, but all my SDL apps (Skale Tracker, ScummVM, whatever) display black as transparent (I mean, instead of black, I can see my wallpaper - and it's orange because of that!). This is true for the 64bit compiled version, as well as the 32bit binary version in emul-libs-x86. I'm currently using xorg-6.8.0-r1, libsdl 1.2.7-r3 and emul-linux-x86-sdl 1.0 on kernel 2.6.9-grntoo-r6, with Nvidia 6629 (the same problem also occured with prior Nvidia, libsdl and xorg releases)... Reproducible: Always Steps to Reproduce: 1. 2. 3.
post your xorg.conf please
Here you go: Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" # FontPath "/usr/share/fonts/100dpi:unscaled" # FontPath "/usr/share/fonts/75dpi:unscaled" # FontPath "/usr/share/fonts/.75dpi" # FontPath "/usr/X11R6/lib/X11/fonts/100dpi" FontPath "/usr/share/fonts/misc" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/Speedo" FontPath "/usr/share/fonts/CID" FontPath "/usr/share/fonts/TTF" FontPath "/usr/local/share/fonts" FontPath "/usr/share/fonts" FontPath "/usr/local/share/fonts/Type1" FontPath "/usr/share/fonts/cyrillic" FontPath "/usr/share/fonts/ttf-bitstream-vera" FontPath "/usr/share/fonts/ukr" FontPath "/usr/share/fonts/100dpi" FontPath "/usr/share/fonts/75dpi" EndSection Section "Extensions" Option "XEVIE" "Enable" # Option "Composite" "Enable" Option "RENDER" "Enable" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "true" Option "Pixmap" "32" EndSection Section "Module" Load "type1" Load "dbe" Load "freetype" Load "glx" Load "v4l" Load "extmod" EndSection Section "InputDevice" Driver "kbd" Identifier "Type6" Option "MapName" "Standard Keyboard [ pc105 ]" # Option "Protocol" "Standard" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbRules" "xorg" Option "XkbVariant" "nodeadkeys" Option "XkbOptions" "ctrl:swapcaps" EndSection Section "InputDevice" Driver "wacom" Identifier "Stylus" Option "Device" "/dev/input/event1" Option "Name" "Intuos2Stylus" Option "Vendor" "Wacom" Option "Mode" "Absolute" Option "Type" "Stylus" # Option "InputFashion" "Tablet" Option "Suppress" "0" Option "Threshold" "16" # Option "Tilt" "on" Option "USB" "on" Option "HistorySize" "32" Option "KeepShape" "on" EndSection Section "InputDevice" Driver "wacom" Identifier "Eraser" Option "Device" "/dev/input/event1" Option "Name" "Intuos2Eraser" Option "Vendor" "Wacom" Option "Mode" "Absolute" Option "Type" "Eraser" # Option "InputFashion" "Tablet" Option "Threshold" "16" # Option "Tilt" "on" Option "USB" "on" Option "HistorySize" "32" Option "KeepShape" "on" EndSection Section "InputDevice" Driver "wacom" Identifier "Cursor" Option "Device" "/dev/input/event1" Option "Name" "Intuos2Cursor" Option "Vendor" "Wacom" Option "Mode" "Relative" Option "Type" "Cursor" # Option "InputFashion" "Tablet" Option "Emulate3Buttons" "no" # Option "ZAxisMapping" "5 4" Option "Button4" "6" Option "Button5" "19" # Option "USB" "on" # Option "Tilt" "on" # Option "HistorySize" "32" Option "Speed" "2.5" # Option "DebugLevel" "10" EndSection Section "Monitor" # DisplaySize 380 230 HorizSync 28-70 VertRefresh 58-63 Identifier "Monitor[0]" ModelName "1600SW" Option "DPMS" VendorName "SGI" Option "OverridePolarity" "1" UseModes "Modes[0]" EndSection Section "Modes" Identifier "Modes[0]" Modeline "1600x1024" 106.9 1600 1632 1656 1672 1024 1027 1030 1067 ModeLine "800x512" 38.94 800 840 1040 1120 512 514 526 552 EndSection Section "Screen" DefaultDepth 24 SubSection "Display" Depth 15 Modes "1600x1024" "1280x1024" "1024x768" "800x600" "800x512" EndSubSection SubSection "Display" Depth 16 Modes "1600x1024" "1280x1024" "1024x768" "800x600" "800x512" EndSubSection SubSection "Display" Depth 24 Modes "1600x1024" "1280x1024" "1024x768" "800x600" "800x512" EndSubSection SubSection "Display" Depth 32 Modes "1600x1024" "1280x1024" "1024x768" "800x600" "800x512" EndSubSection SubSection "Display" Depth 8 Modes "1600x1024" "1280x1024" "1024x768" "800x600" "800x512" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection Section "Device" Identifier "Device[0]" VendorName "NVidia" BoardName "QuadroFX3000G" BusID "2:0:0" Driver "nvidia" Option "NvAGP" "2" Option "HWCursor" "true" Option "CursorShadow" "true" Option "CursorShadowAlpha" "32" Option "DigitalVibrance" "128" Option "RenderAccel" "true" Option "AllowGLXWithComposite" "1" Option "BackingStore" "true" Option "Overlay" "true" Option "UseClipIDs" "true" Option "UBB" "true" Option "PageFlip" "true" Option "WindowFlip" "true" Option "NoDDC" "true" # Option "AllowGLXWithComposite" "1" # Option "MultisampleCompatibility" "1" # Option "XaaNoOffscreenPixmaps" EndSection Section "ServerLayout" Identifier "Layout[all]" InputDevice "Type6" "CoreKeyboard" InputDevice "Cursor" "CorePointer" InputDevice "Stylus" "SendCoreEvents" InputDevice "Eraser" "SendCoreEvents" Option "Clone" "off" Option "Xinerama" "off" Screen "Screen[0]" EndSection
i really have no idea what could cause this.. do you still encounter that bug with newer versions of the packages you mentioned?
Just tested again, and yes, it also happens with the latest versions. But I think I found the problem: seems to be a SDL bug with workstation-level graphic cards. If you enable hardware OpenGL overlays (Nvidia Quadro4 XGL/ Nvidia Quadro FX), black becomes transparent - I guess nobody noticed this yet, 'cause those cards are quite rare, overlays are disabled by default, and most people won't use SDL apps on 3D workstations... :-)
Vapier: Is upstream aware of this bug? If yes, please resolve it as thus.
ive never talked to upstream about it
nor have i ever had this issue on my amd64 with nvidia ...
SpanKY, do you use a Quadro 4 XGL or QuadroFX with hardware OpenGL overlays supported _and_ enabled? Like I said, the problem is only apparent with overlays enabled. I don't think it's amd64-specific, the bug was there on my AthlonXP 2000+ (same graphic card, PNY QuadroFX 3000G), too, IIRC.
no, i dont have a Quadra or overlays ... maybe it that case it's an issue with the nvidia drivers rather than libsdl ?
Has this been fixed by libSDL 1.2.8 or 1.2.9? This one might be resolved and we just don't know it... Well, we can dream, can't we?
Could be... reopen if it's still a problem with the latest versions.
