zwift: Zwift doesn't start with 1.55.0

Hello,

Since this morning, I’m facing an issue with the latest image (digest ac9eb7f0a269, v1.55.0).

Zwift doesn’t start and instead I get two error popups from Wine:

Wine The Wine configuration in /home/user/.wine is being updated, please wait…

rundll32.exe - This applicat… This application could not be started. Do you want to view information about this issue?

The last image working fine for me is digest ad3bca953cb1 v.1.54.0 from a few days ago. When pinning the image to this one, everything works fine.

I didn’t have time to troubleshoot more, here are the container logs:

+ ZWIFT_HOME='/home/user/.wine/drive_c/Program Files (x86)/Zwift'
+ mkdir -p '/home/user/.wine/drive_c/Program Files (x86)/Zwift'
+ cd '/home/user/.wine/drive_c/Program Files (x86)/Zwift'
+ '[' '' = update ']'
++ ls -A .
+ '[' '!' 'ANT_DLL.dll
APR2007_xinput_x64.cab
APR2007_xinput_x86.cab
BleWin10Lib.dll
BleWin10Lib_V2.dll
CloseLauncher.exe
DSETUP.dll
DXSETUP.exe
Feb2010_X3DAudio_x64.cab
Feb2010_X3DAudio_x86.cab
Jun2010_XAudio_x64.cab
Jun2010_XAudio_x86.cab
Launcher_ver_cur.xml
Patcher.dll
VC_redist.x64.exe
WebView2Loader.dll
Webview2Setup.exe
Windows ANT Dongle Driver
ZwiftApp.exe
ZwiftHelper.exe
ZwiftLauncher.exe
ZwiftLauncher.exe.config
ZwiftWindowsCrashHandler.exe
Zwift_1.0.123458_bd4431b2_manifest.xml
Zwift_ver_cur.xml
Zwift_ver_cur_filename.txt
assets
bink2w64.dll
data
dotnet-v4.7.2-installer.exe
dsetup32.dll
dxupdate.cab
starting zwift...
unins000.dat
unins000.exe' ']'
+ echo 'starting zwift...'
+ wine64 start ZwiftLauncher.exe SilentLaunch
013c:err:winebrowser:launch_app could not find a suitable app to open L"http://go.microsoft.com/fwlink/?prd=11324&pver=4.5&sbp=AppLaunch2&plcid=0x409&o1=SHIM_NOVERSION_FOUND&version=(null)&processName=rundll32.exe&platform=0009&osver=5&isServer=0&shimver=4.0.30319.0"

About this issue

Original URL
State: closed
Created 6 months ago
Reactions: 2
Comments: 31 (19 by maintainers)

Most upvoted comments

Sorry about that, my “squash” routine seems to have failed. Building latest image from scratch in order to fix it. Should be fixed afterwards.

netbrain on Jan 1, 2024

Thanks folks, just to say that the latest image (netbrain/zwift@sha256:e68c33ba7fcd7eeced68faf2a87d24ca1b6f0ddc4e51b37e680ee36267b8bd5e) is working fine back on my Fedora 39.

gaeljw on Jan 21, 2024

@fandan start by creating a pull request.

netbrain on Jan 17, 2024

For throse of you with a nvidia graphics card you basically need to get the gpu working in a container environment. https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/sample-workload.html

Also try running an actual gl application like glxgears.

for other graphics cards you need to try different settings i guess. Heres an example on how to get started:

# Create container containing glxgears
docker run --name glx-test debian:bookworm-slim bash -c "apt-get update && apt-get install -y  mesa-utils"
# Create image of container
docker commit glx-test glx-test
# Remove temporary container
docker rm -f glx-test 

#Then try some different experiments in order to get glxgears to work on your system. On my system this works.
docker run -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix --gpus=all -it --rm glx-test glxgears

However also try including flags like, but not limited to:

--device /dev/dri:/dev/dri
--user=$(id -u):$(id -g)
-e WAYLAND_DISPLAY=$WAYLAND_DISPLAY
-v $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY:/tmp/$WAYLAND_DISPLAY
-e XDG_RUNTIME_DIR=/tmp

This all depends on if you are running xorg, wayland or a hybrid etc. Try googling for other flags that would be necessary for your system. If you find a working configuration, then let me know and we’ll make the necessary adjustments to zwift.sh.

netbrain on Jan 4, 2024

Thanks a lot for your work @netbrain 😃

gaeljw on Jan 2, 2024