Since wrapper 3.0.1, can't access games on external drive in Steam

The-Wineskin-Project / WineskinServer

Wineskin

GNU Lesser General Public License v2.1

2.47k stars 170 forks source link

Since wrapper 3.0.1, can't access games on external drive in Steam #576

Closed asmaloney closed 7 months ago

asmaloney commented 7 months ago

Environment

OS: macOS 12.7.4
Winery version: 2.0 (from homebrew)
Master Wrapper version: 3.0.1/3.0.2
Engine version: CX 23.7.1-1
Hardware: iMac
Application/Game Name: Steam

Describe the bug

I had Steam set up to access games on an external drive and it was working great using Wrapper 3.0.0.

I have it configured using the winecfg utility to map the drive to to G:.

Once I updated the wrapper to 3.0.1, my games disappeared in Steam and I could no longer add G: as a drive in Steam.

Went to Settings -> Storage -> Add Drive

Selected G:
nothing happens

I tried creating a new install from scratch with 3.0.2, but still have the same problem.

LastRunWine.log

Steam.app/Contents/SharedSupport/Logs is empty. Not sure where LastRunWine.log file is.

Gcenx commented 7 months ago

You need Winery 2.0.1 and Xcode Command Line Tools installed.

To fix an existing wrapper run

/usr/bin/codesign --deep --force --sign - MyCoolWrapper.app

asmaloney commented 7 months ago

You need Winery 2.0.1 and Xcode Command Line Tools installed.

Ah - I actually do have 2.0.1 (from homebrew), but the about box says 2.0.

To fix an existing wrapper run

It didn't work on my old wrapper ("unsealed contents present in the bundle root"), but I created a new one, ran this and it can find the files again. Time to set everything up again...

So we'll have to do this every time we change wrappers? What about if we switch engines?

Thanks Dean!

Gcenx commented 7 months ago

Ah - I actually do have 2.0.1 (from homebrew), but the about box says 2.0.

Weird.

It didn't work on my old wrapper ("unsealed contents present in the bundle root"), but I created a new one, ran this and it can find the files again. Time to set everything up again...

All you’d have needed todo is remove the files before /Contents including a hidden one.

So we'll have to do this every time we change wrappers? What about if we switch engines?

With the latest versions you might need to adhoc codesign after updating an existing wrapper. Wrappers generated using the current latest Winery/Wrapper there should be no issue with “unsealed contents”

I might might this step automatic after updating an existing Wrapper/Engine, this step will be extremely important for a future CX24.x based Engine and all future Engines.

asmaloney commented 7 months ago

Great - thanks again Dean.

Have a good day/evening/night!