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
Heroic never updates UMU-Launcher. It's installed once and then never updated. My version is 3 months old from October and there hasn't been a single UMU update even though 1.1.4 is out since November.
I discovered the bug while trying to figure out the save path bug here:
Binary files umu/umu-run and umu-outdated/umu-run differ
Binary files umu/umu_run.py and umu-outdated/umu_run.py differ
Well, I honestly don't know if they are newest, but at least they differ.
Edit: Yes, this forced an update to a newer UMU version:
Old:
umu-outdated $ ./umu-run --version
umu-launcher version 1.1.3 (3.13.1 (main, Dec 9 2024, 00:00:00) [GCC 14.2.1 20240912 (Red Hat 14.2.1-3)])
New:
umu $ ./umu-run --version
umu-launcher version 1.1.4 (3.13.1 (main, Dec 9 2024, 00:00:00) [GCC 14.2.1 20240912 (Red Hat 14.2.1-3)])
Edit 2: There's a second bug, probably in UMU itself. It will not upgrade its own installed components after updating UMU, so old bugs in wrappers/helpers remain.
Run both of these commands to fix both bugs. The first fixes the lack of UMU updates in Heroic, and the second fixes the lack of UMU wrapper/helper updates:
Describe the bug
Heroic never updates UMU-Launcher. It's installed once and then never updated. My version is 3 months old from October and there hasn't been a single UMU update even though 1.1.4 is out since November.
I discovered the bug while trying to figure out the save path bug here:
#4087 (comment)
I then checked the files on-disk and saw that UMU inside the Heroic Flatpak is outdated, which explains why the bug still happens.
Add logs
Steps to reproduce
Expected behavior
Update-checks for UMU. Auto-downloads of new versions.
Screenshots
No response
Heroic Version
Latest Stable (Flatpak)
System Information
Additional information
No response
The text was updated successfully, but these errors were encountered: