Aquesta és una versió anterior. La versió actual és la 2126.2. Azahar 2126.2 · Data de publicació:
Fitxers d’instal·lació 2123.4
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) · en-US | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
Azahar 2123.4 is an unscheduled minor release which primarily targets several critical issues which were discovered since the last release, some of which were caused by upstream changes.
All users are advised to update to this release at their earliest convenience.
Please read the change log for further details.
Work continues on the 2124 major release, and you can track its progress here.
New download options:
Android
- The Android build has been split into two new download options, those being the vanilla and googleplay builds.
- The vanilla version uses a new method of filesystem access which is significantly faster and more simple, but isn't permitted by the Google Play store due to its use of the MANAGE_EXTERNAL_STORAGE permission.
- This new system is in its infancy, and is mostly the same as the googleplay variant, so the performance improvements won't yet be apparent. Filesystem performance should noticeably improve in the next few major releases as more functionality is migrated to the new system.
- The googleplay version is compliant with Google Play Store regulations, and uses the old SAF-based method. This build will not see the performance improvements present in the vanilla build.
- Unless you have a particular reason to use the googleplay build or you are downloading the app from the Google Play Store, the vanilla version is recommended.
Linux
- The AppImage build has been split into two new download options, those being azahar.AppImage and azahar-wayland.AppImage
- The default azahar.AppImage now has native Wayland support disabled, instead opting to use XWayland when run in a Wayland session. This is due to some severe upstream issues that have been discovered when using native Wayland with Azahar (e.g. #1191)
- Users are advised to use the default AppImage unless they have a specific reason to have native Wayland support enabled, for example if they are running a system with no xwayland support.
Azahar 2123.4 Changelog
Desktop
- Fixed an issue where the emulator could instantly crash when starting an application due to a race condition. | @OpenSauce04 #1448
Android
- Fixed an issue where, if an application attempted to rename a file to a different location, the file wouldn't be moved, and the file would just be renamed in the same directory it was previously in. | @OpenSauce04 #1545
- This notably fixes an issue where Nimbus 2.x wouldn't install its files correctly.
- Implement new build variant which uses raw filesystem access for file I/O. | @OpenSauce04 #1511 #1542
Linux
- Fixed an issue where attempting to use the Vulkan renderer on a system with an AMD graphics card and Mesa 25.3.2 or later would result in an instant crash. | Anonymous contributor #1563
- Disabled native Wayland support in default AppImage, Create new AppImage download option with native Wayland support enabled. | @OpenSauce04 #1499
MacOS
- Fixed an issue where attempting to use a real camera for camera emulation would result in solid green video output from the camera. | @OpenSauce04 #1515
Technical
- Fixed a build failure in the AppImage build caused by an upstream change to linuxdeploy. | @OpenSauce04 #1486
- Added relWithDebInfoLite build profile. | @OpenSauce04 #1498
- Upgraded AGP to 8.13.1. | @OpenSauce04 #1500
- Updated Boost to v1.89.0 | @PabloMK7 #1502
