DiRT Rally fails to Launch [Arch][Tumbleweed] #3
Comments
|
Ok it seems its the SDL2 issue.. i wonder why it cannot open that file, its bundled with the Dirt Rally and i see it in the folder there. |
|
Update. Seems all feral games have this issue. i mean every game reports different missing .so file but i tested: Hitman, Mad Max, F1 2015, Alien Isolation... all have similar crash and just different .so file is reported to be missing, though i see those files bundled with the game.. Other non-feral games seem to be not having this issue.. is there something wrong with the paths on my system? |
|
Ok, fixed it with a workaround. added this to the steam launch options
now it works. But why doesnt it work like that by default is beyond me |
|
Hi @xpander69, cheers for the report and workaround. So our games find those libraries by using the ELF $ objdump -x bin/DirtRally | grep RPATH
RPATH $ORIGIN/../libThis means even a raw $ ldd bin/DirtRally | grep SDL2-2
libSDL2-2.0.5.so => /opt/steam/steamapps/common/DiRT Rally/bin/../lib/x86_64/libSDL2-2.0.5.so (0x00007f8d2e52b000)Unfortunately, I'm testing this on Arch updated this morning and our steam games are running fine, so I'm unsure what the issue is on your end, could you share the output of the above commands? |
|
yeah seems to be my system then. i have no idea why though. have to investigate. i do use testing repos of arch though, maybe something is screwed up there. full ldd -r log |
|
Thanks for looking into it further. Let me know if you find anything out - issues like these can be early warning signs of future breakages on more stable repos. |
|
Hi @xpander69, did you find the cause here? |
|
Hi, no i did not :( someone in GOL forum said that he have had this issue also in the past. |
|
Worth noting this also appears to be happening in raw Tumbleweed installations |
|
@xpander69 to get you gaming now, it looks like a workaround is to move the contents of |
|
Thanks. Confirming it works that way. |
|
Cheers, could you also run this command and paste the output? |
|
now it works :) |
|
Much appreciated, I'll clean up the back and forth from the thread. Looks like some change in the fundamentals of How strange, will investigate more. For now as you've confirmed this will fix it: cd '/path/to/DiRT Rally/'
ln -s lib/x86_64/* lib/ |
mdiluz
changed the title
|
I've reported the issue we see here on the openSUSE bugzilla while we investigate. Perhaps someone knows what was changed. If you're feeling particularly inclined to do the same for Arch then go ahead. Unfortunately I can't make the report as I still can't reproduce the issue on my Arch installations. |
|
Not sure how helpful I can be, but I recently encountered this problem on Arch w/ [testing] and Life Is Strange. Making links in Did a pastebin of |
|
Cheers, @theRealPadster that certainly looks like the same issue, you're getting the Not sure about |
|
Looks like this might be a glib ABI breakage from this commit. I've added that to the SUSE bug report as glibc's conduct states to report to distribution maintainers before going directly to GNU. Hopefully, this will get looked into soon. |
|
I'm now seeing this with Arch. Downgrading glibc rectifies the problem. So it's pretty much confirmed. |
|
I had the same issue on Slackware64 -current. Fixed it by moving lib dir (per game) as noted above. |
|
This was also reported on the Arch Linux bugtracker: https://bugs.archlinux.org/task/55563 We've now backported the patch from https://sourceware.org/bugzilla/show_bug.cgi?id=22093 so Arch users should do a full system update to get glibc 2.26-4 |
|
Still does the same thing (just not launch) with glibc 2.26-4 if I remove the launch options. |
|
Hi all,
I can confirm that 2.26-4 works fine without the launch options. Just
tested it.
…On Thu, Sep 14, 2017 at 11:21 PM, Isaac ***@***.***> wrote:
Still does the same thing (just not launch) with glibc 2.26-4 if I remove
the launch options.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXv4KsbwdEUqTaMjC7QgmoJiXB4xB-59ks5siUR5gaJpZM4O-82I>
.
|
|
Then why isn't it working for me? o.0 Steam output here |
|
Hi,
Life is Strange works fine too. I just tested all of the games.
On 14 Sep 2017 23:45, "Isaac" <[email protected]> wrote:
Then why isn't it working for me? o.0
[padster@noctus ~]$ pacman -Ss glibc | grep installed
core/glibc 2.26-4 (base) [installed]
multilib/lib32-glibc 2.26-2 [installed]
Steam output here <https://pastebin.com/M1JU6YJe>
Could be this?
/data/padster/Games/Steam/steamapps/common/Life Is
Strange/bin/LifeIsStrange: /usr/lib/libldap_r-2.4.so.2: no version
information available (required by
/data/padster/Games/Steam/steamapps/common/Life Is
Strange/bin/../lib/x86_64/libcurl.so.4)
/data/padster/Games/Steam/steamapps/common/Life Is
Strange/bin/LifeIsStrange: /usr/lib/liblber-2.4.so.2: no version
information available (required by
/data/padster/Games/Steam/steamapps/common/Life Is
Strange/bin/../lib/x86_64/libcurl.so.4)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXv4KjMkcU94_QA5V4G_O78qhjU6IFA2ks5siUoRgaJpZM4O-82I>
.
|
|
@mdiluz Thanks! I will go and notify Slackware team then. Edit: Now fixed in Slackware. |
|
Adding that Fedora 27 didn't have this fix on launch (it was in updates-testing) but now does: |
|
I'm having this issue still on Manjaro 20.1 XFCE. Moving the contents of the x86_64 folder to its parent didn't fix it, the env variable workaround didn't fix it, the ldd command din't fix it. I'm with GLIBC 2.32.... why is this still a thing? |
Same issue even now on the latest version of Manjaro KDE with Alien Isolation. The steam launch options don't work either. The game just doesn't launch. |
|
Having similar issues. None of the above fixes worked. Launcing the game gives a SIGSEV(11) Segmentation fault. Logs: was able to get over these errors by symlinking libcurl.so.4 to the local one: Now, the game just crashes with a segmentation fault and no wiser on what actually causes the crash Computer Information: Processor Information: Operating System Version: Video Card: Sound card: Memory: VR Hardware: Miscellaneous: lspci -k |
Currently the game is failing to launch as libgconf is missing and not available from the Arch repos. I'll try compiling the available AUR package but it seems many are having issues with it succeeding. Edit: gconf didn't do the trick. libldap is installed for what it's worth, though it's likely the version is too new? |
|
Gave up on running the game via steam-runtime, got the game running on proton experimental. |
|
There's a beta branch that works. I have no idea why it isn't public or default. The password is "feraldirtsupport" and it's called "feral_support_branch" under steam. Do you have force feedback working under proton? I do not have it with any of my controllers using this beta build. |
|
I just had the same error running this game. None of the suggested solutions here worked, so I ran the game via Proton 4.11-13 and it worked perfectly out of the box. But only 4.11-13 works, the rest of the new protons (5.0 and above) are no go with this game. |
|
On Arch you need to install |
|
I tried all the solutions above, like setting env variables, symlinking to files, or getting What did work is getting the feral_support_branch using the "feraldirtsupport" password (Game configuration -> Betas -> Input password). Why isn't this branch default? |
|
I meant you need to install |
|
If affects Deus Ex Mankind divided and XCOM2 (vanilla, without War Of The Chosen) on Ubuntu 23.04 I think it will affect more and more distributions because of a change in glibc version 2.37: AT_PLATFORM is what was defined as x86_64 until now |
|
Can confirm the Steam feral_support_branch is working flawlessly on OpenSUSE Tumbleweed. Go to game Properties -> Betas and enter access code feraldirtsupport. This branch should be the default. |
On my ArchLinux, I did the following procedure:
After the procedure, the game worked normally |
|
Could anyone help? Operating System: Manjaro Linux Log from Steam: |
|
@Neural-network-N your kernel version seems to be a bit old , even for manjaro , are you sure it is updated correctly , arch and tumbleweed are already on 6.7.x with matching mesa drivers etc. |
Better to configure it so as not to use LD_PRELOAD, in the game, this even interferes with checking the log. |
Cross-referencing: this is the same issue that's described in #15 and ValveSoftware/steam-runtime#613. |
In my comment, I mentioned that on Arch Linux you just need to install gconf (AUR) and openssl-1.0 (AUR) and copy the files from the "$GAMEROOT/lib/x86_64" directory to "$GAMEROOT/lib", except the "libcurl.so.4" file , otherwise it will make the game ask for more dependencies. Maybe it's a good idea to do a test too, as I don't think it's necessary to create well-designed scripts just to make a game work. That's the job of the game's devs. Well, that's my suggestion for an easy solution. You don't need to accept what I actually say.
|
|
On Manjaro, the game starts with Steam running in runtime mode, but failed to start in native mode.
|
In fact, I don't have the "$GAMEROOT/lib/x86_64" and "$GAMEROOT/lib" folders. I had seen them before my game updated (common game autoupdate via Steam). How can I install those gconf and openssl-1.0 packages?.. |
https://aur.archlinux.org/packages/gconf Be warned the AUR is not officially supported on Manjaro so if your system breaks don't ask Arch for help. |
|
@Neural-network-N: You seem to have the Windows version of Dirt Rally installed, not the native Linux version. Check the settings in its Properties -> Compatibility in Steam. If you are intentionally using the Windows version, check that it's configured to run under some version of Proton. If you were intending to be using the native Linux version, check that it's configured to run under either "Steam Linux Runtime 1.0 (scout)" or no compatibility tool at all. |
@smcv, thank you, Simon! And thank you all! There was no compatibility tool chosen. BTW, I reinstalled DirtRally, chose manually "Steam Linux Runtime 1.0 (scout)" , joined the beta-branch "feral_support_branch" and then the game started! Without any additional libraries! I've got only one error (sigsegv 11 segmentation fault or smth like that) for 3 hours of gameplay. |
Having an issue with Dirt Rally, It worked fine few days ago. Now im getting this:
System info:
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 1700X Eight-Core Processor
CPU Family: 0x17
CPU Model: 0x1
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 3900 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 4.12.1-2-hz
X Server Vendor: The X.Org Foundation
X Server Release: 11903000
X Window Manager: Metacity (Marco)
Steam Runtime Version: steam-runtime-beta-release_2017-07-24
Video Card:
Driver: NVIDIA Corporation GeForce GTX 1070/PCIe/SSE2
Driver Version: 4.5.0 NVIDIA 384.59
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 119 Hz
VendorID: 0x10de
DeviceID: 0x1b81
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 4480 x 1440
Primary Display Size: 23.50" x 13.23" (26.97" diag)
59.7cm x 33.6cm (68.5cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 8192 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Nvidia GPU 83 HDMI/DP
Memory:
RAM: 32175 Mb
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 2815659 Mb
Largest Free Hard Disk Block: 352451 Mb
VR Headset: None detected
Recent Failure Reports:
What i have tried to fix this problem so far?
Still same problems
The text was updated successfully, but these errors were encountered: