search

pauleve / docker-mtgo

Docker image with ready-to-play MTGO (Magic Online) for Linux and macOS
https://hub.docker.com/r/panard/mtgo/
488 stars 34 forks source link

Error on import closing the app #155

Open EvertonZanotelli opened 2 years ago

EvertonZanotelli commented 2 years ago

Screenshot from 2022-05-16 15-35-04 The aplication is closing when i'm trying to import a deck at the exactly moment that I click the "Import" Fatal Error on Import.txt

EvertonZanotelli commented 2 years ago

output.log

pauleve commented 2 years ago

Do you get this error systematically? I'm not able to reproduce it here.. You may give a try to

./run-mtgo --test --reset   # start from a fresh install
# or
./run-mtgo --update  panard/mtgo:pr153 # wine 7.8
Wizzerinus commented 2 years ago

I am getting the same issue on the latest build (probably) Image digest: e4edd59b68c7184705740cf2dc4de9bf56f2fb209f9cba3afcdd4c0f042a872f Wine log & Windows internal log: https://hastebin.com/wimoxigaze.yaml

Wizzerinus commented 2 years ago

Notably, this does not trigger if the Z disk is disabled in winecfg. Think that should be the default.

FinleyVickers commented 2 years ago

Notably, this does not trigger if the Z disk is disabled in winecfg. Think that should be the default.

Hi, I have been running into the same issue, how do I disable the Z drive?

Wizzerinus commented 2 years ago

@FinleyVickers winecfg -> Drives -> Z: -> Remove

image

pauleve commented 2 years ago

Thanks, I'll check how to do that automatically. Quick question though: how do you give access to the decklist you want to import: are you using the -v option to mount your host filesystem in the Docker container? In that case, how do avoid requiring Z:?, or do you use docker cp to manully copy a file in the container?

Wizzerinus commented 2 years ago

I am manually copying files from drive_c. Well I was doing it until I changed to virtualbox, that is.

I bet you can add a drive to something like /home/user/documents/docker-mtgo and export there, although that sounds like something docker can't do without violating the sandboxing

Mycheze commented 1 year ago

I was having the same issue. Whenever I tried to "access the file system" it would throw the same error and crash. All my draft files have been exporting just fine.

Deleting the Z drive does seem to work as per Wizzerinus's above suggestion. I tried it once, it didn't seem to do anything, then I checked, and it was still there, so I deleted it again, and now it's working?

Anyway, just commenting to say that yes, has-workaround, but also still an issue for some systems it seems.

pauleve commented 11 months ago

I've added a command to remove the Z: device before starting MTGO. You can try with either

./run-mtgo --update  panard/mtgo:pr183

or

./run-mtgo --cmd "live-mtgo for-next"

Also note that you can also use the option --bind some/path to link a folder to the "Documents" windows folder.