Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: wine + fglrx ==> Please

  1. #11
    Join Date
    Aug 2008
    Posts
    32

    Default

    umm... ok so this is yet another env, good.
    now... what does it do exactly?


    cheers

  2. #12
    Join Date
    Jun 2008
    Location
    Melbourne
    Posts
    212

    Default

    It makes sure your using the fglrx openGL implementation, not mesa. Why it should change back, I'm not sure.

  3. #13
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,182

    Default

    Compiz sets that, IIRC.

  4. #14
    Join Date
    May 2007
    Posts
    352

    Default

    Quote Originally Posted by storma View Post
    It makes sure your using the fglrx openGL implementation, not mesa. Why it should change back, I'm not sure.
    Not quite. It makes sure that wine applications aren't using indirect rendering, which would still be the fglrx opengl implementation, just with the opengl commands passed through the X server via the glx module.

    And yes, compiz sets the LIBGL_ALWAYS_INDIRECT variable. However, even after starting X, that variable should only be set for applications spawned by compiz. if you start up a terminal through the normal gnome/kde menu, for example, that variable should be unset.

    Adam

  5. #15
    Join Date
    May 2009
    Location
    Canada
    Posts
    38

    Default

    Quote Originally Posted by adamk View Post
    Not quite. It makes sure that wine applications aren't using indirect rendering, which would still be the fglrx opengl implementation, just with the opengl commands passed through the X server via the glx module.

    And yes, compiz sets the LIBGL_ALWAYS_INDIRECT variable. However, even after starting X, that variable should only be set for applications spawned by compiz. if you start up a terminal through the normal gnome/kde menu, for example, that variable should be unset.

    Adam
    This is exactly it. wow. I almost always start my terminal windows with "SUPER+T" (a configured shortcut in compiz). When starting a terminal window this this shortcut (which uses compiz to start to the terminal I'm assuming), that ENV variable LIBGL_ALWAYS_INDIRECT is set to 1. However, if I start the terminal with ALT+F2 and gnome-terminal, this environment variable isn't set.

    Do we know why compiz sets this? ... trying to think if it's a bug ...

  6. #16
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,669

    Default

    Sounds like a bug in Compiz, yeah.

  7. #17
    Join Date
    Aug 2007
    Posts
    6,641

    Default

    Well most likely in the autostart script of compiz as you have to start it really soon in order to set a var system wide.

  8. #18
    Join Date
    May 2007
    Posts
    352

    Default

    Quote Originally Posted by fermulator View Post
    This is exactly it. wow. I almost always start my terminal windows with "SUPER+T" (a configured shortcut in compiz). When starting a terminal window this this shortcut (which uses compiz to start to the terminal I'm assuming), that ENV variable LIBGL_ALWAYS_INDIRECT is set to 1. However, if I start the terminal with ALT+F2 and gnome-terminal, this environment variable isn't set.

    Do we know why compiz sets this? ... trying to think if it's a bug ...
    Well because fglrx doesn't support GLX_EXT_texture_from_pixmap in direct rendering contexts, only via AIGLX.

    In other words, compiz needs to be started with indirect rendering in order to run.

    Newer versions of compiz will use indirect rendering if you specify --indirect-rendering, but I can't be 100% sure that it won't set the LIBGL_ALWAYS_INDIRECT variable for compiz and any other process compiz spawns.

  9. #19
    Join Date
    May 2007
    Posts
    352

    Default

    Quote Originally Posted by Kano View Post
    Well most likely in the autostart script of compiz as you have to start it really soon in order to set a var system wide.
    Again, it's not set system wide. It's set for compiz. If compiz spawns a process, though, it will also be set for that process.

    Don't launch terminals through compiz, and that variable won't be set.

    Adam

  10. #20
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,669

    Default

    Quote Originally Posted by adamk View Post
    Well because fglrx doesn't support GLX_EXT_texture_from_pixmap in direct rendering contexts, only via AIGLX.
    Hmm, I was under the impression it should have since maybe around 9.3... Ah, well. That explains it then.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •