-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
AppImage 4.3.2 appears to be missing a directory #891
Comments
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. I don't have a clue about the problem, but I will try to find anwsers. |
Thank you, I hadn't thought of trying to run the AppImage without the AppImageLauncher integration. I very much appreciate your response |
- **File formats:** - (Add) File format: Klipper zip - (Add) Properties: - `Pause` and `ChangeResin` to layers - `BottomLiftAcceleration` - `BottomLiftAcceleration2` - `LiftAcceleration` - `LiftAcceleration2` - `BottomRetractAcceleration` - `BottomRetractAcceleration2` - `RetractAcceleration` - `RetractAcceleration2` - (Add) PrusaSlicer Keywords: - `FILECLASS_xxx` to define the file class directly instead of a file extension - `BottomLiftAcceleration` - `BottomLiftAcceleration2` - `BottomRetractAcceleration` - `BottomRetractAcceleration2` - `LiftAcceleration` - `LiftAcceleration2` - `RetractAcceleration` - `RetractAcceleration2` - (Add) Property `HaveTiltingVat` to know if the printer have a tilting vat - (Add) Compatibility with tilting vat Saturn 4 Ultra which also fixes print time estimate (#906) - (Add) Encrypted CTB: Tries to predict tilting vat printers from set parameters - (Change) CWS: Append `;<Slice>` as first line in the layer instead when required - (Change) VDT: Move FTL previews to top to be used as first in conversion - (Improvement) Anycubic: Write the image color table based on the AntiAliasing level (#899) - (Improvement) Encrypted CTB: Implement the `ModifiedTimestampMinutes` and `AntiAliasLevel` field - (Fix) nanoDLP `slicer.json` deserialize problem on some files - (Fix) SL1: The keyword `TransitionLayerCount_xxx` not being set on the file (#902) - (Fix) PHZ: Generated invalid thumbnail data (#903) - **Tools:** - (Improvement) Pixel arithmetic: Add extra checks to ignore empty size and layers - (Change) Edit print parameters: Allow set lift and retract speeds to 0 (#906) - **UI:** - (Add) Menu - File - Copy parameters to files: Allow to copy parameters from current file to another file(s) (#852) - (Improvement) Menu - File - Reset layer properties: Hold SHIFT key to also rebuild layers position with the file layer height (#870) - (Improvement) Save as and convert file save dialog: Force the correct file extension if been tampered (#909) - (Improvement) Exposure time finder: Disable incompatible panels instead of hide them - (Add) Layer preview shortcuts: A/W/S/D to pan the layer image and Q/E to go to previous/next layer (#871) - (Fix) Prevent CTRL + SHIFT + Up/Down (Issue navigation shortcut) from change layer - (Add) PrusaSlicer printer: Elegoo Saturn 4 Ultra - (Fix) Linux AppImage: Failed to change to directory "~" (No such file of directory) (#891) - (Upgrade) OpenCV from 4.8.0 to 4.9.0 - (Upgrade) AvaloniaUI from 11.0.10 to 11.1.1 (Fixes #872) - (Upgrade) .NET from 6.0.29 to 6.0.32
Fixed |
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: