Re: trixie: cdrecord can no longer write to CD
Hi,
i wrote:
> > In libusal/scsi-linux-sg.c, usalo_open(), line 532:
> > - pattern="/dev/scd%d";
> > + pattern="/dev/sr%d";
Timothy M Butterworth wrote:
> I also ran into this problem. It was caused by permissions.
> Running:
> sudo chmod 4711 /usr/bin/wodim
> sudo chmod 4711 /usr/bin/cdrdao
> Fixed the problem for me.
We have two wodim problems in this thread:
The unexplored complaint by K3B towards the original poster,
D. R. Evans :
> > > k3b says: "Cdrecord [sic] has no permission to open the device".
for which he later reports that chmod 4711 solved it.
It is not clear, what K3B tried to do with wodim or cdrecord when it
encountered a reason to complain.
I was able to use wodim with dev=/dev/sr0 on a post-Trixie Sid VM
which has a virtual DVD-ROM drive. But this VM neither has a burner
device nor a graphical desktop where i could run K3B.
In the K3B source i believe to see that the K3B message is caused by
a wodim message which begins by
Permission denied
or by
Operation not permitted
The texts probably stem from the system error list (man errno).
In wodim's source i find only
https://sources.debian.org/src/cdrkit/9:1.1.11-5/doc/READMEs/README.ATAPI.setup?hl=31#L31
"Note: with certain kernel versions wodim can fail with this message:
"wodim: Operation not permitted. Cannot send SCSI cmd via ioctl"
In this case it still does need the suid bit - please send patches if
you have identified the reason of that problem."
So the problem waits for a K3B user who can reproduce it with wodim
without s-permission (the "4" in "4711") and then show K3B's command
log.
Of course, the messages of some failed wodim run outside K3B could give
insight, too.
The other problem is with wodim option --devices, for which the reason
is known and fix proposals have been discussed.
This problem is not related to permissions or user identies.
So it cannot be the reason why K3B refuses to use wodim with the
permissions as installed.
Have a nice day :)
Thomas
Reply to: