Please use this thread to report issues and ask support questions

Release annoucement and download links: https://arosworld.org/infusions/forum/viewthread.php?thread_id=2096&pid=14487#post_14487

@deadwood

Good news: with my AROS One 1.3—which “hasn't been updated with the Dx”—the ISO CUE files mount perfectly, and the audio CD immediately displays the two icons in Wanderer.

PlayCDDA also works well; there are just a few issues with the Eject button (on native AROS it doesn't work, and on VMware it freezes the system).

Hmm, what is the base for 1.3? 20250418-U2?

Are you using the CUE plugin I compiled today with 1.3 or did it have another it's own "older" version?

There wasn't a 64-bit version available, so I used the CUE you compiled!
I need to test it with your new Build 2026.09

Can you tell me what is the base system version in AROS One 1.3?

I don't remember exactly, but it should be 20250418-1-U3!

https://www.arosw...post_11170

@deadwood
CUE works well even with the new Build 2026.09!
PlayCDDA also works well.

Deadwood, just like with the DX builds, what should I do about GRUB and the boot file (upper and lowercase)?

Keep in mind that if you try to update AROS One with the new AROS One build, it won't boot!

Does the new AROS One have to be built using the new build?

@AMIGASYSTEM

grub/boot files

The grub in 2026.04 is not compatible with the grub used in 20250418-1. If you are building update package for AROS One 1.3 it can't contain grub - it's the same thing as with at least U3 update - it also couldn't update grub.

Note that there is also 20250418-1-U4 release which is an upgrade package that turns 20250418-1 into 2026.09. This package doesn't have grub update.

What I'd like to know is whether the new AROS One “will have to have the new GRUB” and therefore need to be rebuilt!

That's your choice. I don't think anything in 2026.09 depends on having updated grub.

I assume you are taking AROS One 1.3 and the copying 2026.09 on top of it. In such you case you will often have issues, because some files might have moved or were removed (like in case of grub) and you end up with some duplicated system files. I personally would do the integration slightly different. Take AROS One 1.3. Delete all the files that came from 20250418-1 + U3 (so all old system files) and then apply 2026.09 on top of that. This way you won't have duplicated system files.

This is getting complicated now. Just today I deleted all the old builds, but now I'm finding 20250418-1 and the updates, it's no longer on the forum, and it's not on build.axrt.or either!

FYI: build.axrt.org is not hosting release, only nightly builds.

You can find all binaries for 20250418-1 here: https://github.com/deadwood2/AROS/releases/tag/ABIv11_20250418-1

Okay, I've decided to take the easiest route: I'll start from scratch by building AROS One based on Build 2026.09.
There probably won't be any updates this time; otherwise, AROS One users will run into problems.

Hi All,

A serious performace regression was discovered 2026.09 in BoingIconBar. If you are using it in your distribution/installation, be sure to update it with attached binary.

Deadwood: I noticed a problem when you accidentally drag an app icon onto another app icon; if you try to close it, instead of closing, the notifications multiply, see the attached video.

Thanks for reporting, I will into this in comming days.

In the Shell, if you type or paste text up to the limit supported by the Shell, the Shell can no longer be closed.

With AROS One on VMware, I always have that annoying problem (even after updating to ABIv11 64-bit 2026.09) where if I copy and paste in the Shell, the system freezes; with the ABIv11 64-bit 2026.09 build, this doesn’t happen.
Strangely enough, if it doesn’t happen on the first copy-and-paste, the freeze won’t happen again!

On a native PC, AROS One itself doesn’t have this problem!