What you specified is a pseudo SCSI spec which wodim tries to map back to a real Linux device with it's obscure ways. Obviosly, it prefers the /dev/sg* devices and you seem not to have permissions on that device.
Indeed, because sg0 is my hard disk.
Send your output of "wodim -scanbus" please.
See #370603.
Don't rely on its guessing code. Specify a real device file (dev=/dev/hdX or dev=/dev/srX) and it should be happy. Can you test it and report?
Yes. This fails: $ wodim dev=0,6,0 -atip And this succeeds: $ wodim dev=/dev/scd1 -atip I have no problem with specifying a device name when manually invoking wodim from the command line. However, I would suggest that if the pseudo-scsi-id syntax is broken, then it should be either fixed or removed. Also, if the pseudo-scsi-id syntax doesn't work, then k3b shouldn't use it. If you look at my original email that opened this bug report, you can see that k3b has detected the devices correctly, and that it knows the device names. As such, it should be easy to modify k3b to pass that to wodim, instead of the pseudo-scsi-id. -- graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
