Describe the bug
Having Unicode characters in any of the environment variables makes the pharo launcher break while Clicking "Show" in the VMs and probably hangs while trying to launch an image.
To Reproduce
Steps to reproduce the behavior:
Go to the location where you installed the Pharo Launcher
Click on the launcher file (pharo-launcher)
Update the virtual machines
See error
WideString does not understand #tfPointerAddress
with a Debug button and an Ignore one.
Expected behavior
The Image should open.
Screenshots
Error Window:
Clicking debug I got a hint of the problem:
Version information:
OS: Antix Linux (Debian oldstable)
Version: 3.0.1
Expected development cost
I don't really have a good idea. I know about Smalltalk from a long time ago, but I'm at maximum a hobbyist. I have no idea exactly how to fix things. My skills extend to small debugging.
Additional context
So as I mentioned and is showed in the screenshots the problem is having
XDG_DOWNLOAD_DIR=/home/fkbm/Descărcări
in the environment. Launching the pharo-launcher with:
Describe the bug Having Unicode characters in any of the environment variables makes the pharo launcher break while Clicking "Show" in the VMs and probably hangs while trying to launch an image.
To Reproduce Steps to reproduce the behavior:
Expected behavior The Image should open.
Screenshots Error Window:![screenshot](https://github.com/pharo-project/pharo-launcher/assets/1178686/3dfdc533-e56e-4ec9-be43-d623852c8460)
Clicking debug I got a hint of the problem:![screenshot2](https://github.com/pharo-project/pharo-launcher/assets/1178686/3afff417-b8ae-40b8-a863-3cad2223b60d)
Version information:
Expected development cost I don't really have a good idea. I know about Smalltalk from a long time ago, but I'm at maximum a hobbyist. I have no idea exactly how to fix things. My skills extend to small debugging.
Additional context So as I mentioned and is showed in the screenshots the problem is having
in the environment. Launching the pharo-launcher with:
A similar error occurs because I also have:
Now relaunching with:
fixes everything, but it's not a normal/nice way of fixing it.
Anyway, for the error showed in the screenshots the debug log is: