Re: trixie: cdrecord can no longer write to CD
On 19/11/2025 01:31, Thomas Schmitt wrote:
The --devices bug is rather due to a failed attempt to rename /dev/sr
to /dev/scd about 25 years ago,
Do you know precise range of affected kernel versions? Is there a chance
to use some kind of feature detection (presence or contents of some file)?
With above strace run as normal user i only get an error message
together with each line:
openat(AT_FDCWD, 0x7fff596d83e0, O_RDWR|O_EXCL|O_NONBLOCK) = -1 ENOENT (No such file or directory)
strace: fopen: /proc/1188/maps: Permission denied
Below you mentioned that the binary does not have SUID bit. I would
expect that this error is caused by elevated privileges.
My Sid is assessed as Linux >= 2.6 because of the major kernel version
6 being larger than 1 and the minor version 16 being >= 6.
https://sources.debian.org/src/cdrkit/9%3A1.1.11-5/libusal/scsi-linux-sg.c#L251
return ( 0==uname( &buf ) && sscanf(buf.release, "%d.%d", &gen, &tmp)>1
&& tmp>=6);
The major kernel version is ignored here. Return value of sscanf is the
number of matched and assigned values.
You found it several years ago:
"Re: wodim --devices and -scanbus bugs 495184, 655878, 833346"
- <https://bugs.debian.org/495184#112>
- <https://bugs.debian.org/655878#10>
- <https://bugs.debian.org/833346#35>
- <mid:30196743283722340330@scdbackup.webframe.org>
Sat, 08 Apr 2017 12:11:02 +0200
There are more bugs that might be duplicates:
- <https://bugs.debian.org/434479>
"wodim: can't find /dev/sr0\n (as read from /proc/..../info"
- <https://bugs.debian.org/597500>
"wodim: Wodim fails to find device"
- <https://bugs.debian.org/851616>
"wodim --devices says try wodim --devices"
Any volunteers who still use optical drives to post comments suggesting
duplicates and rising priority?
My conclusion that there is severe problem with package development and
maintenance. That is why I earlier asked if xorriso may be a replacement.
I cannot test whether K3B would like my headless Sid's wodim without
setuid bit.
Can k3b be configured to use "ssh wodim.local wodim ..." instead of just
"wodim" (or a shell script wrapper)?
Reply to: