[k3b] [Bug 501656] New: Can't burn CD's on Fedora Silverblue
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Mon Mar 17 18:41:43 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=501656
Bug ID: 501656
Summary: Can't burn CD's on Fedora Silverblue
Classification: Applications
Product: k3b
Version: 25.03.80
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: k3b at kde.org
Reporter: migtorr at proton.me
CC: michalm at jabster.pl, trueg at kde.org
Target Milestone: ---
SUMMARY
Can't burn any CD, tried installing k3b with rpm-ostree and with toolbox dnf
STEPS TO REPRODUCE
1. Burn CD on Fedora Silverblue
2. I get "cdrecord has no permission to open the device"
OBSERVED RESULT
"cdrecord has no permission to open the device"
EXPECTED RESULT
Able to bun CD
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Silverblue 41
ADDITIONAL INFORMATION
When you see ">" it means command > result. This is all I tried to make it run
Over here you can see it more tidy and with photos
https://red.ngn.tf/r/silverblue/comments/1jdgn72/cant_burn_cds_with_k3b_neither_brasero/
Devices
-----------------------
PIONEER BD-RW BDR-XD08U 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R
Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW
Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer,
CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE]
[SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted
Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential
Recording + POW] [%7]
System
-----------------------
K3b Version: 24.12.3
KDE Version: 6.11.0
Qt Version: 6.8.2
Kernel: 6.13.5-200.fc41.x86_64
Used versions
-----------------------
cdrecord: 1.1.11
cdrecord
-----------------------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK
limits.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
/usr/bin/wodim: Cannot allocate memory.
Cannot open SCSI driver!
For possible targets try wodim --devices or wodim -scanbus.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
Text len: 576
TOC Type: 0 = CD-DA
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=24 -sao driveropts=burnfree
textfile=/tmp/k3b.YFGXxC -useinfo -audio
/var/home/migtorr/Videos/k3b_audio_0_01.inf
/var/home/migtorr/Videos/k3b_audio_0_02.inf
/var/home/migtorr/Videos/k3b_audio_0_03.inf
/var/home/migtorr/Videos/k3b_audio_0_04.inf
/var/home/migtorr/Videos/k3b_audio_0_05.inf
/var/home/migtorr/Videos/k3b_audio_0_06.inf
/var/home/migtorr/Videos/k3b_audio_0_07.inf
/var/home/migtorr/Videos/k3b_audio_0_08.inf
/var/home/migtorr/Videos/k3b_audio_0_09.inf
/var/home/migtorr/Videos/k3b_audio_0_10.inf
/var/home/migtorr/Videos/k3b_audio_0_11.inf
/var/home/migtorr/Videos/k3b_audio_0_12.inf
/var/home/migtorr/Videos/k3b_audio_0_13.inf
wodim --devices
wodim: Overview of accessible drives (1 found) :
0 dev='/dev/sr0' rwrw-- : 'PIONEER' 'BD-RW BDR-XD08U'
wodim --scanbus
scsibus1:
`1,0,0` `100) 'PIONEER ' 'BD-RW BDR-XD08U' '1.02' Removable CD-ROM`
`1,1,0` `101) *`
`1,2,0` `102) *`
`1,3,0` `103) *`
`1,4,0` `104) *`
`1,5,0` `105) *`
`1,6,0` `106) *`
`1,7,0` `107) *`
With sudo gpasswd --add migtorr cdrom > gpasswd: group 'cdrom' does not exist
in /etc/group
sudo groupadd cdrom > groupadd: group 'cdrom' already exists
sudo usermod -aG cdrom migtorr does nothing
sudo chown root:cdrom /dev/cdrom
sudo chmod 660 /dev/cdrom
sudo udevadm control --reload-rules
sudo udevadm trigger
does nothing
Had to edit the /etc/group file and add cdrom:x:24:migtorr
group migtorr > migtorr : migtorr wheel cdrom
And now that part seems to be sorted
sudo chmod 4711 /usr/bin/wodim\ > chmod: changing permissions of
/usr/bin/wodim: Read-only file system
sudo chmod 4711 /usr/bin/cdrdao\ > chmod: changing permissions of
/usr/bin/cdrdao: Read-only file system
I cannot find a workaround for above
ls -l /dev/cdrom > lrwxrwxrwx. 1 root root 3 Mar 17 13:33 /dev/cdrom -> sr0
I try sudo k3b but it crashes:
QGuiApplication::setDesktopFileName: the specified desktop file name ends with
.desktop. For compatibility reasons, the .desktop suffix will be removed.
Please specify a desktop file name without .desktop suffix
kf.coreaddons.kaboutdata: QGuiApplication::desktopFileName "org.kde.k3b" is
out-of-sync with KAboutData::applicationData().desktopFileName
"org.kde.k3b.desktop"
kf.coreaddons.kaboutdata: QGuiApplication::desktopFileName "org.kde.k3b" is
out-of-sync with KAboutData::applicationData().desktopFileName
"org.kde.k3b.desktop"
QGuiApplication::setDesktopFileName: the specified desktop file name ends with
.desktop. For compatibility reasons, the .desktop suffix will be removed.
Please specify a desktop file name without .desktop suffix
kf.coreaddons.kaboutdata: QGuiApplication::desktopFileName "org.kde.k3b" is
out-of-sync with KAboutData::applicationData().desktopFileName
"org.kde.k3b.desktop"
[5123:5123:0317/143940.833679:ERROR:zygote_host_impl_linux.cc(100)] Running as
root without --no-sandbox is not supported. See https://crbug.com/638180.
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 13 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 12 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 11 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 9 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 7 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 5 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 4 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 3 destroyed
QThreadStorage: Thread 0x558892fc5430 exited after QThreadStorage 2 destroyed
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the k3b
mailing list