Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Wrong working directory #3567

Open
TheSainEyereg opened this issue Nov 22, 2024 · 1 comment
Open

[Bug]: Wrong working directory #3567

TheSainEyereg opened this issue Nov 22, 2024 · 1 comment

Comments

@TheSainEyereg
Copy link

Describe the bug

When launching UE5 game located on /media/data/_Downloads/TestUE5Game/TestUE5Game.exe, it crashes with error:

---------------------------
Error
---------------------------
Couldn't start:
"Z:\run\user\1000\doc\b813cf8d\TestUE5Game\Binaries\Win64\TestUE5Game-Win64-Shipping.exe" TestUE5Game 
CreateProcess() returned 2.
---------------------------
OK   
---------------------------

It doesn't make any sense, because the game SHOULD run from /media/data/_Downloads/TestUE5Game and not from /run/user/1000...

At the same time, if you run an EXE through Steam or double-click to run through the system Wine (which I previously provided the necessary libraries), the game will run normally*

*if we do not take into account that Wine crashes, and keeping Steam for each similar game is not convenient

To Reproduce

  1. Add Shortcuts
  2. Locate exe withe latest UE5 game
  3. Run It from bottles

Package

Flatpak from Flathub

Distribution

Arch Linux

Debugging Information

Official Package: true
Version: '51.15'
DE/WM: plasma
Display:
    X.org: true
    X.org (port): :1
    Wayland: true
Graphics:
    vendors:
        nvidia:
            vendor: nvidia
            envs:
                __NV_PRIME_RENDER_OFFLOAD: '1'
                __GLX_VENDOR_LIBRARY_NAME: nvidia
                __VK_LAYER_NV_optimus: NVIDIA_only
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/nvidia_icd.json
            nvngx_path: /usr/lib/x86_64-linux-gnu/GL/nvidia-565-57-01/extra/nvidia/wine
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.11.8-arch1-2
Disk:
    Total: 16776331264
    Free: 16776146944
RAM:
    MemTotal: 31.2GiB
    MemAvailable: 24.7GiB
Bottles_envs: null

Troubleshooting Logs

02:48:42 (INFO) Launching with URI: None 
02:48:42 (INFO) [Activate] request received. 
02:48:42 (INFO) Bottles Started! 
02:48:43 (INFO) Performing Bottles checks… 
02:48:43 (INFO) Steam path doesn't exist, creating now. 
02:48:43 (INFO) Dxvks found:
         - dxvk-2.5.1
 
02:48:43 (INFO) Vkd3ds found:
         - vkd3d-proton-2.13
 
02:48:43 (INFO) Nvapis found:
         - dxvk-nvapi-v0.7.1
 
02:48:43 (INFO) Latencyflexs found:
         - latencyflex-v0.1.1
 
02:48:43 (INFO) Runners found:
         - soda-9.0-1
         - wine-ge-proton8-26
         - ge-proton9-20
         - sys-wine-9.0
 
02:48:43 (INFO) Bottles found:
         - SVALKER
 
02:48:43 (INFO) Catalog dependencies loaded 
02:48:43 (INFO) Catalog installers loaded 
02:48:43 (INFO) Catalog components loaded 
02:48:44 (INFO) Setting Key sync=fsync for bottle SVALKER… 
02:48:44 (INFO) There is no running wineserver. 
02:48:49 (INFO) Setting Key ce579d6d-6232-4bda-9f8e-ad6a3cba3f08={'executable': 'TestUE5Game.exe', 'name': 'TestUE5Game', 'path': '/run/user/1000/doc/b813cf8d/TestUE5Game.exe', 'id': 'ce579d6d-6232-4bda-9f8e-ad6a3cba3f08', 'folder': '/run/user/1000/doc/b813cf8d'} for bottle SVALKER… 
02:49:05 (INFO) Launching an executable… 
02:49:05 (INFO) Using EasyAntiCheat runtime 
02:49:05 (INFO) Using BattlEye runtime 
fsync: up and running.
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).

Additional context

As I said, this problem is not present when running through natively installed tools (including Steam), which makes me think that the stupid Flatpack package security policy is to blame.

Maybe there is some way to give Bottles direct access to the working directory?

@TheSainEyereg
Copy link
Author

TheSainEyereg commented Nov 22, 2024

Btw: here is another example: Old Chromium from 2013

This works in Bottles if originally installed via mini_installer.exe, however if you try to run chrome.exe from unzipped chrome-win32, the browser will crash immediately.

And again: everything works perfectly if you run it through Steam, also the browser starts through normal Wine (but the window is black).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant