[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: trixie: cdrecord can no longer write to CD



Thomas Schmitt wrote on 11/14/25 3:07 PM:
Hi,

D.R.Evans wrote:
I just discovered that, following the upgrade from bookworm to trixie on my
main desktop machine, when I try to write a hierarchy of data files to the
CD drive, k3b says: "Cdrecord [sic] has no permission to open the device".

Unhelpfully, k3b doesn't tell me what is the name of the device it is trying
to open, nor what permission it (or cdrecord) lacks :-(

The mentioned "cdrecord" is probably wodim from package cdrkit.

The device is possibly /dev/sr0 if it is the only optical drive that
is attached to the computer.

Yep, I worked out that it is /dev/sr0.

But suspiciously

   sudo wodim --devices


I get:

[ZB:tmp] sudo wodim --devices
wodim: No such file or directory.
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.
[ZB:tmp]

talks of /dev/sg1, which on my Debian 12 is the generic SCSI device
associated to /dev/sr0. The number after "sg" may be different on your
system. Ask wodim.

The needed permissions are rw. Normally these permissions are given
to owner "root", group "cdrom", and by ACL to the desktop user.
Inquire by

   sudo getfacl /dev/sr0

which on my Debian 12 with fvwm user "thomas" says:

   # file: dev/sr0
   # owner: root
   # group: cdrom
   user::rw-
   user:thomas:rw-
   group::rw-
   mask::rw-
   other::---


Here, I get:

[ZB:tmp] sudo getfacl /dev/sr0
getfacl: Removing leading '/' from absolute path names
# file: dev/sr0
# owner: root
# group: cdrom
user::rw-
user:n7dr:rw-
group::rw-
mask::rw-
other::---

[ZB:tmp]

which looks to my eyes to be equivalent to what you get, and it appears to say that I shouldn't have had this problem. Although perhaps the fact that I already applied the setuid "fix" in my message of a couple of hours ago changed the output from what I would have got had I run the command before applying the fix.

  Doc

--
Web:  http://enginehousebooks.com/drevans


Reply to: