/usr/bin/readcd: setting to root:root 0755 (wrong permissions 0711)
/usr/bin/cdrecord: setting to root:root 0755 "cap_ipc_lock,cap_sys_rawio,cap_sys_nice,cap_sys_resource=ep". (missing capabilities)
Hey I think this is prolly selinux permission errors but I am not sure, how to fix?
It’s not an SELinux issue. Those messages come from the cdrecord/readcd binaries themselves. Can you provide more information around when you read these messages? Was it during a package upgrade, or when running a disc-burning application like K3b?
Upstream sets these permissions, SUSE / openSUSE has always changed them to root:root 0755 as long as I’ve been around, k3B settings made you set the one for cdrecord 4755 IIRC.
While waiting for my coffee searched on OBS. Both cdrecord and cdread are part of cdrtools. In its spec file it sets this:
%verify(not mode)%attr(0755,root,root)/usr/bin/cdrecord
%verify(not mode)%attr(0755,root,root)/usr/bin/readcd
%verify(not mode)%attr(0755,root,root)/usr/sbin/rscsi
%else
%verify(not mode)%attr(0711,root,root)/usr/bin/cdrecord
%verify(not mode)%attr(0711,root,root)/usr/bin/readcd
%verify(not mode)%attr(0711,root,root)/usr/sbin/rscsi
%config /etc/permissions.d/cdrecord.*
AFAICS this is where it happens and why one sees the messages during install and during an update.
It was during update/upgrade.
And is the application working as expected? Or were you just asking a general question?
idk I didnt even test the application I was just wondering if it was a problem.
I hope it’s clear to you now, that it is not a problem.
It was just correcting as per the package update (and as Gertjan described).
Ok thanks!
My tuppence worth:
- In the Zypp history of this Tumbleweed system:
# grep -E 'readcd|cdrecord' /var/log/zypp/history -B 1 -A 1
.
# 2026-02-22 14:55:47 readcd-3.02~a10-53.1.x86_64.rpm installed ok
# Additional rpm output:
# /usr/bin/readcd: setting to root:root 0755 (wrong permissions 0711)
#
2026-02-22 14:55:47|install|readcd|3.02~a10-53.1|x86_64||openSUSE:repo-oss|a897948203de6adee986c0a1ed37c893b9735422f411e4036521f7f40767b2860035e37bc10088e4808b98e7ae13e0286187bc22c8c2594f483be2dc35d329ec|
.
# 2026-02-22 14:55:47 cdrecord-3.02~a10-53.1.x86_64.rpm installed ok
# Additional rpm output:
# /usr/bin/cdrecord: setting to root:root 0755 "cap_ipc_lock,cap_sys_rawio,cap_sys_nice,cap_sys_resource=ep". (missing capabilities)
#
2026-02-22 14:55:47|install|cdrecord|3.02~a10-53.1|x86_64||openSUSE:repo-oss|691c57b1ac65c02132c4f6a5b8e9daa4ef9e879ada6ed95cc09f32154890fb0198bb0d1e2e28338e2a25bfe92d04636b9624c289d86bd389a3b276f78d1cd392|
.
So, yes, nothing is broken – and, the missing capabilities are a Linux Kernel issue:
<Playing with Linux kernel capabilities>
> ls -alZ /usr/bin/readcd /usr/bin/cdrecord
-rwxr-xr-x. 1 root root system_u:object_r:cdrecord_exec_t:s0 407936 17. Feb 04:59 /usr/bin/cdrecord
-rwxr-xr-x. 1 root root system_u:object_r:bin_t:s0 129600 17. Feb 04:59 /usr/bin/readcd
>