You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System is Ubuntu 42.04 LTS
I am unable to sucessfully run the AppImage file which
is identified as UVtools_linux-x64_v4.3.2.AppImage
Printer and Slicer
Printer: N/A
Slicer: N/A
Description of the bug
I am attempting to run the latest AppImage 4.3.2 on an installation of Ubuntu 24.04 destop LTS with AppImageLauncher installed (I am able to sucessfully run other Appimage files on this system) and I am receiving a system notification-
Failed to launch "UVTools"
Failed to change to directory "~" (No such file of directory)
How to reproduce
click on Show Apps
click on icon UVtools
Files
No response
The text was updated successfully, but these errors were encountered:
This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌
I have notice that on recent systems. ~ definitely exists as it your home directory however somehow it fails.
I also note that the problem is with AppImage integration on your system, if you run it from desktop without integrate it always run fine.
I don't have a clue about the problem, but I will try to find anwsers.
System
Printer and Slicer
Description of the bug
I am attempting to run the latest AppImage 4.3.2 on an installation of Ubuntu 24.04 destop LTS with AppImageLauncher installed (I am able to sucessfully run other Appimage files on this system) and I am receiving a system notification-
Failed to launch "UVTools"
Failed to change to directory "~" (No such file of directory)
How to reproduce
click on Show Apps
click on icon UVtools
Files
No response
The text was updated successfully, but these errors were encountered: