Error on import closing the app

Question

Error on import closing the app

EvertonZanotelli opened this issue 2 years ago · 10 comments

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

Answer 1 · 2022-05-16T19:09:40.000Z

output.log

Answer 2 · 2022-05-17T20:05:42.000Z

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

Answer 3 · 2022-08-05T10:09:21.000Z

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

Answer 4 · 2022-08-09T10:01:46.000Z

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

Answer 5 · 2022-10-11T00:31:43.000Z

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?

Answer 6 · 2022-10-13T10:24:51.000Z

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

Answer 7 · 2022-10-13T13:35:23.000Z

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?

Answer 8 · 2022-10-13T14:55:17.000Z

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

Answer 9 · 2023-08-09T01:41:27.000Z

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.

Answer 10 · 2023-12-21T13:49:51.000Z

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.