ZimaOS v1.7.1 Is Here, Please Update Now！🚀

Announcements
1

Dear IceWhale members，

Following the release of ZimaOS 1.7, ZimaOS v1.7.1 mainly focuses on security, stability, and fixes for issues recently reported by the community. This release addresses a high-risk security issue in the file service, along with several issues related to memory usage, backups, USB devices, RAID, and app data.

We’ve also further improved the Docker experience, including container startup, network configuration, Web UI port settings, YAML compatibility, and app migration. Thank you to everyone who reported issues and helped with testing. Your feedback continues to make ZimaOS better. :blue_heart:

Here is the full changelog:

Security

  • Fixed a high-risk security issue in file services to improve the security of file access and operations

Added

  • Added be2net network driver support for Emulex NICs. Special thanks to @Tigre34.

  • Added support for Azerbaijani. Special thanks to @ElonStark.

Fixes

  • Fixed abnormal memory usage in certain file operation scenarios. thanks to @balaise0558.

  • Fixed an issue where empty folders could remain after cutting folders in certain scenarios. thanks to @Isanto1306 .

  • Fixed issues where backup tasks could fail or be interrupted in certain scenarios. thanks to @SEBASCHELL.

  • Fixed an issue where some USB-related tasks could be lost after system restart. thanks to @bbalak.

  • Fixed inaccurate RAID status display in certain scenarios

  • Fixed an issue where uninstalling an app could delete the app configuration folder

Improvements

  • Improved Docker container startup speed and startup efficiency

  • Improved the network configuration experience during Docker installation. thanks to @AmIBeingObtuse

  • Improved Docker Web URL port configuration with more flexible port setting, thanks to @adrien.

  • Improved YAML configuration saving compatibility to reduce failures caused by specrial content. thanks to @landouraubriot-coder.

  • Improved the display experience of App Store and app installation windows. thanks to @alexvaltchev.

  • Imprved app migration compatibility. thanks to @editon.

  • Improved Docker URL handling to better adapt to dynamic network environments

Download Now：

image
image1688×2806 353 KB

If you run into any issues or have any feedback, feel free to @Zima-777Spider anytime. We’ll continue listening to the community and improving ZimaOS together.

Thank you as always for your support! :blue_heart:

IceWhale Team

2 Likes
3

Dashboard configuration issues when upgrading from ZimaOS 1.6.2 to 1.7.1

Before upgrading from ZimaOS 1.6.2 to 1.7.1, I made screenshots of my complete dashboard so that I could compare the state before and after the update.

My dashboard contains a large number of installed applications and web shortcuts, many of which have been manually arranged and customized with different icons.

Problems after upgrading to 1.7.1

The update to ZimaOS 1.7.1 itself completed, but after the upgrade I noticed major problems with the dashboard configuration.

After upgrading from 1.6.2 to 1.7.1:

Many web shortcuts were missing.
Some shortcuts were still present, but their icons had changed.
Some custom icons were replaced by older icons that I had previously changed.
Some shortcuts had no proper icon anymore.
The order of apps and shortcuts was changed.
Several dashboard entries appeared in different positions than before.

The dashboard therefore looked significantly different compared to my screenshots from ZimaOS 1.6.2.

Attempt to restore the old configuration

Fortunately, I have automatic daily backups of my dashboard configuration created with Cron.

The relevant files were:

app_order.json
link.json

I tried to restore the previous configuration by copying the contents of the old backup files from ZimaOS 1.6.2 into the corresponding files on ZimaOS 1.7.1 and then rebooting the NAS.

However, after the first restoration attempt, the situation actually became worse.

After rebooting:

More entries appeared to be incorrect or missing.
The order became even more inconsistent.
Several icons were wrong or missing.
The dashboard looked worse than it did immediately after the upgrade.

After further attempts, another reboot, and restoring the configuration again, most of the missing web shortcuts eventually returned.

However, the dashboard was still not identical to the original ZimaOS 1.6.2 configuration.

Some entries were still in the wrong order, some icons were incorrect, older icons that I had previously replaced reappeared, and some icons were missing completely.

Returning to ZimaOS 1.6.2

Because of these problems and the unreliable behavior of the dashboard configuration, I eventually decided to downgrade from ZimaOS 1.7.1 back to ZimaOS 1.6.2.

The rollback itself was also not completely straightforward. During the RAUC installation, the process appeared to remain at:

42% Copying image to boot.0

for a considerable amount of time.

The RAUC processes were still running in the background, so I did not interrupt the installation. Eventually, the installation completed successfully.

After rebooting into ZimaOS 1.6.2, most of my original dashboard configuration returned.

The web shortcuts and applications were present again, although the order of some entries was still mixed up. This can be manually corrected.

Conclusion

Based on my experience, there appears to be a problem with how the dashboard configuration is handled when upgrading from ZimaOS 1.6.2 to 1.7.x.

Simply restoring the previous:

app_order.json
link.json

does not reliably reproduce the original dashboard state under ZimaOS 1.7.1.

It seems possible that ZimaOS 1.7.x processes, migrates, regenerates, or overwrites parts of the dashboard configuration after reboot.

I cannot confirm exactly what happens internally, but the behavior affects:

App order
Web shortcut order
Icon assignments
Custom or previously changed icons
Overall dashboard layout

After returning to ZimaOS 1.6.2, the situation was significantly better and most of my previous dashboard configuration was restored.

For now, I will stay on ZimaOS 1.6.2 until the dashboard migration and upgrade behavior are more reliable.

I strongly recommend that users with heavily customized dashboards make a backup of their configuration before upgrading from ZimaOS 1.6.x to 1.7.x.

Additional UI feedback

There is also another change introduced with ZimaOS 1.7.x that I personally do not like: the new typography and text appearance.

In the previous version, the text and labels in the interface appeared clearer and visually lighter. The typography had a cleaner and more subtle appearance.

Since ZimaOS 1.7.0, the text styling appears different. Some text looks heavier and darker, while other elements appear too faint or washed out. Overall, I find the previous text and font appearance easier to read and visually more balanced.

This is of course a matter of personal preference, but I would prefer an option to choose between the previous and the new text appearance, or at least adjust the font weight and contrast.

4

I personally haven’t encountered any problems but I went through v1.7.0 (with its minor bugs).
Maybe by first taking a step to v1.7.0 then, secondly, moving to v1.7.1, you would encounter fewer problems (?).
Although having been critical, like you, of the (minor) bugs caused by v1.7.0. I am satisfied with this new version.
I particularly like the new console with the possibility of acting directly on the YAML live.
I also appreciate that applications developed outside the console are no longer required for reconstruction (impossible).
Also this update to v1.7.1 fixed a problem due to the Bios of my Z Motherboard. When I restarted my machine, I had to restart my apps. This problem was also present in Debian. Now and I don’t know why, everything works perfectly - no need to restart my apps.
Regarding the new font, I too preferred v1.6. But hey it’s not very important and it’s everyone’s tastes.