This is definitely related to LD_PRELOAD. What seems to be happening is that Steam adds ~/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so:~/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so to the existing LD_PRELOAD variable set by vglrun, so the resulting LD_PRELOAD variable is:
libdlfaker.so:libvglfaker.so:~/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so:~/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so Because I have no access to the gameoverlayrenderer.so source, I'm not sure exactly what that interposer is doing, but in my testing, it is clear that gameoverlayrenderer.so has to be preloaded ahead of VirtualGL for things to work properly. For instance, if I edit ~/.local/share/Steam/steamapps/common/dota 2 beta/game/dota.sh and add export LD_PRELOAD=~/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so:~/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so:libdlfaker.so:libvglfaker.so to the top, I can make Dota 2 launch and play correctly. This exposes a second issue whereby the game locks up when exiting it (still investigating that.) As far as I can tell, the LD_PRELOAD variable is modified within some non-hackable part of Steam. I think a good argument could be made that this is incorrect behavior on Steam's part. gameoverlayrenderer.so should be as close to the application in the preload order as possible, and other interposers should be placed after it. Still investigating how I might be able to work around this within VirtualGL, but I wanted to share my findings thus far. Note that I also tried disabling the in-game overlay, in hopes that that would make Steam stop trying to preload gameoverlayrenderer.so, but no such luck. :| I'll keep you posted. On 6/28/16 12:22 PM, Marco Marino wrote: > I'm able to play stream, but games nit working.. Please can you create > a steam account and try to play half life2 or dota?? They are free to > play games. > Thamk you > > Il 28 Giu 2016 19:19, "DRC" <dcomman...@users.sourceforge.net > <mailto:dcomman...@users.sourceforge.net>> ha scritto: > > Did installing both RPMs work? I am able to launch Steam with no errors > on F22 using the same packages you are using, and with both VirtualGL > RPMs installed: > > VirtualGL-2.5-20160215.x86_64 > VirtualGL-2.5-20160215.i386 > > But I have no ability to actually test games, as I do not have a Steam > account. > > > On 6/26/16 11:33 AM, DRC wrote: > > No, on RPM-based systems, you can simply co-install the i386 and x86_64 > > RPMs. > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > VirtualGL-Devel mailing list > VirtualGL-Devel@lists.sourceforge.net > <mailto:VirtualGL-Devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/virtualgl-devel > > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > > > > _______________________________________________ > VirtualGL-Devel mailing list > VirtualGL-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtualgl-devel > ------------------------------------------------------------------------------ _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
