I have first updated to k3b-23.08.4-2.fc39 (FEDORA-2024-9b6430cd6a) and then tested BZ#2212471.
Unfortunately, I now get the error mkisofs executable not found. when I click the burn button. However, the command/bin mkisofs is available on my Fedora.
Yet, is it possible that the new issue is that Fedora links the /bin/mkisofs file (symlink) to /etc/alternatives/mkisofs ? (I assume this is the Fedora default because I have not made any customizations to/in mkisofs)
I then tried to do alternatives --set cdrecord /usr/bin/wodim (I did it with root; my normal accounts don't have sudo) after I experienced the issue and tried again. But the outcome is the same.
I tried it also with unconfined_u user accounts (which is the Fedora default) to ensure that my confined user account is not the issue/problem.
I asked in the bugzilla topic BZ#2212471 if someone else can verify if the update to k3b-23.08.4-2.fc39 has the same outcome on their systems.
BZ#2212471 k3b is not able to burn data to disks in KDE
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
It will be selected by default on new fedora installations.
Perfect!
but given that it didn't work before i'd say this is good enough...?
I am not sure if I understand that comment. As far as it concerns me, the issue is solved! Thank you very much! I know for the future what/where to look for. My argument about making the selection to the default was referring to those who don't know (and maybe don't even know where/whom to ask). Also, I had to expect that both upgraded Fedoras and new installations might be affected. It's great that new installations are "prepared". I have just set the #k3b tag to my watch list in ask.fedora, just in case someone else who upgraded comes up with that issue so that I can refer to your solution.
This update has been submitted for testing by aleasto.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
I have first updated to k3b-23.08.4-2.fc39 (FEDORA-2024-9b6430cd6a) and then tested BZ#2212471.
Unfortunately, I now get the error
mkisofs executable not found.when I click theburnbutton. However, the command/binmkisofsis available on my Fedora.Yet, is it possible that the new issue is that Fedora links the
/bin/mkisofsfile (symlink) to/etc/alternatives/mkisofs? (I assume this is the Fedora default because I have not made any customizations to/in mkisofs)I then tried to do
alternatives --set cdrecord /usr/bin/wodim(I did it with root; my normal accounts don't have sudo) after I experienced the issue and tried again. But the outcome is the same.I tried it also with unconfined_u user accounts (which is the Fedora default) to ensure that my confined user account is not the issue/problem.
I asked in the bugzilla topic BZ#2212471 if someone else can verify if the update to
k3b-23.08.4-2.fc39has the same outcome on their systems.Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
/usr/bin/genisoimageis not selected by default in the k3b settings ("configure k3b" -> "Programs").It is necessary to manually select & apply
/usr/bin/genisoimagein the settings: After that, it works fine.However, the default should be changed so that
/usr/bin/genisoimageis selected/enabled by default on Fedora installations.Thanks for the update!
It will be selected by default on new fedora installations.
For people upgrading, they might end up in your same situation; but given that it didn't work before i'd say this is good enough...?
(new fedora installation may also just mean the first k3b installation as it's not preinstalled in fedora)
Perfect!
I am not sure if I understand that comment. As far as it concerns me, the issue is solved! Thank you very much! I know for the future what/where to look for. My argument about making the selection to the default was referring to those who don't know (and maybe don't even know where/whom to ask). Also, I had to expect that both upgraded Fedoras and new installations might be affected. It's great that new installations are "prepared". I have just set the #k3b tag to my watch list in ask.fedora, just in case someone else who upgraded comes up with that issue so that I can refer to your solution.
Again, thanks for handling this so quickly!
It means that i don't know if I'd be able to fix the missing checkbox on upgrade but that I would't want to hold this update for that :P
It means that i don't know if I'd be able to fix the missing checkbox on upgrade but that I would't want to hold this update for that :P
Ah, yeah, now I got it ;) Absolutey, that makes sense ! I already changed the karma above to +1 :)
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by aleasto.
This update has been pushed to stable.