Closed skyvenom-msx closed 10 months ago
Found a workaround! I added "--no-bwrap" to the protontricks command in step/configure_steam_wineprefix.sh.
Fix: protontricks --no-bwrap "$game_appid" -q "${game_protontricks[@]}"
On Pop_OS! using Flatpak protontricks and had a similar issue and solution.
Needed to add --no-bwrap
on line 10 if configure_steam_wineprefix.sh
edit* should add this was for Skyrim: Special Edition on an external harddrive :shrug:
from:
flatpak run 'com.github.Matoking.protontricks' \
"$game_appid" -q "${game_protontricks[@]}" \
to:
flatpak run 'com.github.Matoking.protontricks' --no-bwrap \
"$game_appid" -q "${game_protontricks[@]}" \
I don't know enough about about wine
to cast judgement if this is a valid solution that should be applied to all source.
Perhaps a re-try to add --no-bwrap
if it fails at this step?
Problem here is the Steam client itself (pressure-vessel most likely) and seems to be described in the following line from the logs:
steam-runtime-launcher-service[30290]: E: Can't find session bus: Error spawning command line `dbus-launch --autolaunch=f5e2011d7c6638b29c9027ae5f4195e6 --binary-syntax --close-stderr': Failed to execute child process "dbus-launch" (No such file or directory)
From the looks of it, Steam can't find the program dbus-launch
and can't proceed because of that.
@skyve2222 you can check whether or not dbus-launch
is installed on your system with the command command -V dbus-launch
.
@fanuch your problem is unlikely to be the same, since you're on Pop_OS!. Getting Protontricks to continue by using --no-bwrap
was probably just a coincidence. Please provide the failure logs so we can take a look at what happened.
Closing due to inactivity. The use of --no-bwrap
may be related to bugs in older versions of Protontricks, see conversations in #555
I've tried installing this multiple times with clean prefixes and fresh installs and it keeps getting stuck on "Configuring game prefix This may take a while" for an hour. It may be a protontricks problem but I couldn't find any issues on it. Maybe I'm just being impatient but I couldn't find anything running from this script in htop. I'm on Artix (non-systemd Arch) using runit.
Here what I see before it gets stuck for at least an hour: