Star Conflict crashes due to missing "radeon_dri.so" library

Hey,

 

I am confused on where to report the issue. I created already ticket with ID 53837 on the gaijin tracker. I created a bug report at the official https://github.com/ValveSoftware/steam-for-linux/issues/3244 Valve bugtracker. And I will do it here again:

 

 

The game crashes because it is looking for a /usr/lib32/dri/radeon_dri.so which does NOT exist on my system. For a detailed info check the github-issue-link.

Setting breakpad minidump AppID = 212070
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198054163081 [API loaded no]
libGL error: MESA-LOADER: could not create udev device for fd 760
libGL error: dlopen /usr/lib32/dri/radeon_dri.so failed (/usr/lib32/dri/radeon_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: radeon_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeon
Game removed: AppID 212070 "Star Conflict", ProcID 29546 
Installing breakpad exception handler for appid(steam)/version(1397080338_client)

During my research on this particular issue I found the following bug report: http://osdir.com/ml/general/2014-04/msg09269.html

 

From what I understood this is an issue of using mesa 10.1 (or anything containing the patches from http://patchwork.freedesktop.org/patch/17793/) and libudev.so.0. My base system only contains libudev.so.1, but sadly the steam runtime (in ~/.local/share/Steam) currently ships libudev.so.0. I first attempted to work around the issue by deleting the file, but steam no longer started.

 

I did a nasty workaround to symlink my systems libudev.so.1 to overwrite the local libudev.so.0 in the steam runtime. If you are on x86_64 (64-bit OS) do:

ln -s /usr/lib32/libudev.so.1 ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0

If you are on i686 (32-bit OS) do:

ln -s /usr/lib/libudev.so.1 ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0

This issue will hit more users once mesa 10.1 is more widespread, which is likely to be soon as Ubuntu 14.04 was released shipping mesa 10.1.

During my research on this particular issue I found the following bug report: http://osdir.com/ml/general/2014-04/msg09269.html

 

From what I understood this is an issue of using mesa 10.1 (or anything containing the patches from http://patchwork.freedesktop.org/patch/17793/) and libudev.so.0. My base system only contains libudev.so.1, but sadly the steam runtime (in ~/.local/share/Steam) currently ships libudev.so.0. I first attempted to work around the issue by deleting the file, but steam no longer started.

 

I did a nasty workaround to symlink my systems libudev.so.1 to overwrite the local libudev.so.0 in the steam runtime. If you are on x86_64 (64-bit OS) do:

ln -s /usr/lib32/libudev.so.1 ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0

If you are on i686 (32-bit OS) do:

ln -s /usr/lib/libudev.so.1 ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0

This issue will hit more users once mesa 10.1 is more widespread, which is likely to be soon as Ubuntu 14.04 was released shipping mesa 10.1.

 

Sorry, but this is totally unrelated to my issue here. You should file a new bug. The same goes for your github issue comment.