F42 KDE remix using Kiwi-ng: Anaconda fails with rsync error

[Massimiliano Bugni]

Hello,
I'm facing an issue with my F42 KDE Remix [1]. Maybe this is not the best place to post it, but you could help me to address the issue.
When I try to install the live image in a KVM virtual machine, I get the following error message (see also attachment):

Failed to install image: process '['rsync', '-pogAXtlHrDx', '--stats',
'--info=flist2,name,progress2', '--no-inc-recursive', '--exclude',
'/dev/', '--exclude', '/proc/', '--exclude', '/tmp/*', '--exclude',
'/sys/', '--exclude', '/run/', '--exclude', '/boot/*rescue*',
'--exclude', '/boot/loader/', '--exclude', '/boot/efi/', '--exclude',
'/etc/machine-id', '--exclude', '/etc/machine-info',
'/run/install/sources/mount-0000-live_os_image/', '/mnt/sysroot']'
exited with status 23

Is anyone facing a similar problem?
The image is very similar to F41, and this is the first time I see this error.

Thanks
Massi

[1] https://github.com/mbugni/fedora-remix

[Steve Cossette]

For this, you'd need to submit an issue on the KDE Remix github. We do not
support third party modifications of Fedora.

But do let us know if you experience the same thing with the official F42
KDE Edition image!

On Mon, May 12, 2025 at 7:04 AM Massimiliano Bugni via kde <
[e-mail]> wrote:
> Hello,
> I'm facing an issue with my F42 KDE Remix [1]. Maybe this is not the best
> place to post it, but you could help me to address the issue.
> When I try to install the live image in a KVM virtual machine, I get the
> following error message (see also attachment):
>
> Failed to install image: process '['rsync', '-pogAXtlHrDx', '--stats',
> '--info=flist2,name,progress2', '--no-inc-recursive', '--exclude',
> '/dev/', '--exclude', '/proc/', '--exclude', '/tmp/*', '--exclude',
> '/sys/', '--exclude', '/run/', '--exclude', '/boot/*rescue*',
> '--exclude', '/boot/loader/', '--exclude', '/boot/efi/', '--exclude',
> '/etc/machine-id', '--exclude', '/etc/machine-info',
> '/run/install/sources/mount-0000-live_os_image/', '/mnt/sysroot']'
> exited with status 23
>
> Is anyone facing a similar problem?
> The image is very similar to F41, and this is the first time I see this
> error.
>
> Thanks
> Massi
> [1] https://github.com/mbugni/fedora-remix
>
> kde mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Massi aka Ergosum]

Il giorno lun 12 mag 2025 alle ore 14:41 Steve Cossette
 ha scritto:
> For this, you'd need to submit an issue on the KDE Remix github. We do not support third party modifications of Fedora.

I'm the author of that remix. Do you know someone else that is
building live or remix using kiwi-ng?
> But do let us know if you experience the same thing with the official F42 KDE Edition image!

I didn't try it, but AFAIK official images are built using kickstart
technology, isn't it?

[Steve Cossette]

I believe they use kiwi, if that makes sense. I don'T have much knowledge
on how the fedora isos are generated.

On Mon, May 12, 2025 at 10:02 AM Massi aka Ergosum 
wrote:
> Il giorno lun 12 mag 2025 alle ore 14:41 Steve Cossette
>  ha scritto:
> > For this, you'd need to submit an issue on the KDE Remix github. We do
>
> not support third party modifications of Fedora.
> >
>
> I'm the author of that remix. Do you know someone else that is
> building live or remix using kiwi-ng?
> > But do let us know if you experience the same thing with the official
>
> F42 KDE Edition image!
> >
>
> I didn't try it, but AFAIK official images are built using kickstart
> technology, isn't it?

[Troy Dawson]

On Mon, May 12, 2025 at 7:17 AM Steve Cossette via kde <
[e-mail]> wrote:
> I believe they use kiwi, if that makes sense. I don'T have much knowledge
> on how the fedora isos are generated.
>
> On Mon, May 12, 2025 at 10:02 AM Massi aka Ergosum <
> [e-mail]> wrote:
> > Il giorno lun 12 mag 2025 alle ore 14:41 Steve Cossette
> >  ha scritto:
> > > For this, you'd need to submit an issue on the KDE Remix github. We do
> >
> > not support third party modifications of Fedora.
> > >
> >
> > I'm the author of that remix. Do you know someone else that is
> > building live or remix using kiwi-ng?
> > > But do let us know if you experience the same thing with the official
> >
> > F42 KDE Edition image!
> > >
> >
> > I didn't try it, but AFAIK official images are built using kickstart
> > technology, isn't it?
>
> Starting with Fedora 42, they are now using Kiwi.

You can find the official kiwi configurations here
 https://pagure.io/fedora-kiwi-descriptions/tree/f42

At what point are you getting that error?
Right when you double click the icon?  (So anaconda isn't even started)
Or while anaconda is starting up?

Troy

[Massi aka Ergosum]

> Starting with Fedora 42, they are now using Kiwi.
> You can find the official kiwi configurations here
>  https://pagure.io/fedora-kiwi-descriptions/tree/f42

I see that in F42 the iso filesystem has changed from squashfs to erofs.
> At what point are you getting that error?
> Right when you double click the icon?  (So anaconda isn't even started)
> Or while anaconda is starting up?

I sent you an attachment, but I realized that probably this ML doesn't
support it.
The error is during filesystem copy from live image to disk.
More or less, in the middle of the install process.

Massi

[Massi aka Ergosum]

I'm discovering other similar issues:

https://github.com/rhinstaller/anaconda/pull/6029
https://bugzilla.redhat.com/show_bug.cgi?id=2329379

[Neal Gompa]

On Mon, May 12, 2025 at 4:49 PM Massi aka Ergosum via kde
 wrote:
> I'm discovering other similar issues:
>
> https://github.com/rhinstaller/anaconda/pull/6029
> https://bugzilla.redhat.com/show_bug.cgi?id=2329379

Looks like those issues were fixed with F42.

--
真実はいつも一つ！/ Always, there's only one truth!

[Massi aka Ergosum]

> > https://github.com/rhinstaller/anaconda/pull/6029
> > https://bugzilla.redhat.com/show_bug.cgi?id=2329379
>
> Looks like those issues were fixed with F42.

I hope this issue is related to erofs (I'm still using squashfs).
I'll try to switch in the next few days.
Very similar descriptions work perfectly with F41.
Honestly, I'd like to get rid of Anaconda and use Calamares, but I
cannot get it working.

Regards
Massi

[Massi aka Ergosum]

> > Looks like those issues were fixed with F42.
>
> I hope this issue is related to erofs (I'm still using squashfs).
> I'll try to switch in the next few days.

My issue is due to [1] [2] [3].
After applying the [3] patch, my F42 installation was successful.
I suppose this is an evil F42 combination kiwi+anaconda.

During my investigation, I also discovered the weird
`/etc/fstab.script` patch [4] [5].
Honestly, I don't understand why. But I also applied this one, just in case.

No erofs, still using squashfs.

Hope this helps those who want to build custom images.

Regards
Massi

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2358785
[2] https://github.com/OSInside/kiwi/pull/2778
[3] https://pagure.io/fedora-kiwi-descriptions/pull-request/177
[4] https://github.com/OSInside/kiwi/issues/2201
[5] https://osinside.github.io/kiwi/working_with_images/custom_fstab_extension.h...

[Massi aka Ergosum]

This weird bug is back again. I really don't know why.

For some digital miracle, Calamares stopped crashing. I decided to try
harder with it.
After some patches, I got my first Fedora live install using Calamares.

First, I removed /boot/loader/entries using config.sh (I suppose it's
garbage from kiwi build)
The installation is successful, but booting from disk provides only
the UEFI settings entry (the kernel has not been recognized).

I restarted the live system and manually mounted the ESP partition.
Then I re-created manually the grub.cfg file using grub2-mkconfig.
Now the system boots as intended.

It's a crappy procedure, but at least it works.

BTW
The F42 calamares version tries to remove itself using the dnf3(!!!)
command, and of course it fails.

[Massi aka Ergosum]

After struggling a little with grub entries, I finally got it working
with Calamares.
Thanks to the Nobara project that heavily inspired me.

I published a video to show it [1].

[1] https://www.youtube.com/watch?v=NHn7zolSDqc

Il giorno sab 28 giu 2025 alle ore 17:39 Massi aka Ergosum
 ha scritto:
> This weird bug is back again. I really don't know why.
>
> For some digital miracle, Calamares stopped crashing. I decided to try
> harder with it.
> After some patches, I got my first Fedora live install using Calamares.
>
> First, I removed /boot/loader/entries using config.sh (I suppose it's
> garbage from kiwi build)
> The installation is successful, but booting from disk provides only
> the UEFI settings entry (the kernel has not been recognized).
>
> I restarted the live system and manually mounted the ESP partition.
> Then I re-created manually the grub.cfg file using grub2-mkconfig.
> Now the system boots as intended.
>
> It's a crappy procedure, but at least it works.
>
> BTW
> The F42 calamares version tries to remove itself using the dnf3(!!!)
> command, and of course it fails.