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

Error on import closing the app #155

Open
EvertonZanotelli opened this issue May 16, 2022 · 10 comments
Open

Error on import closing the app #155

EvertonZanotelli opened this issue May 16, 2022 · 10 comments

Comments

@EvertonZanotelli
Copy link

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
Copy link
Author

output.log

@pauleve
Copy link
Owner

pauleve commented May 17, 2022

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
Copy link

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
Copy link

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

@FinleyVickers
Copy link

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
Copy link

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

image

@pauleve
Copy link
Owner

pauleve commented Oct 13, 2022

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
Copy link

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
Copy link

Mycheze commented Aug 9, 2023

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 added a commit that referenced this issue Dec 11, 2023
pauleve added a commit that referenced this issue Dec 11, 2023
pauleve added a commit that referenced this issue Dec 14, 2023
@pauleve
Copy link
Owner

pauleve commented Dec 21, 2023

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.

pauleve added a commit that referenced this issue Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants