wodim couldn't be set suid.

hello,

I've a problem, I can't burn my CD-RW because wodim :

The log of K3b :

System
-----------------------
K3b Version: 0.12.17

KDE Version: 3.5.6
QT Version: 3.3.7
Kernel: 2.6.20-8-generic
Devices
-----------------------
TSSTcorp CD/DVDW SN-W082B SB00 (/dev/hdb, ) at [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD-R DL; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-R Dual Layer Sequential; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R96R; Restricted Overwrite]

Used versions
-----------------------
cdrecord: 2.1.1a03

cdrecord command:
-----------------------
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hdb speed=24 -tao driveropts=burnfree -eject blank=fast -force

cdrecord
-----------------------
scsidev: '/dev/hdb'

devname: '/dev/hdb'
scsibus: -2 target: -2 lun: -2
Error trying to open /dev/hdb exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdb exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdb exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdb exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdb exclusively (Device or resource busy)... giving up.
TOC Type: 1 = CD-ROM
scsidev: 'ATA:/dev/hdb'
devname: 'ATA:/dev/hdb'
scsibus: -2 target: -2 lun: -2
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.

Why ?

There are two problems:

1) wodim is a fork from cdrecord and does not really work

2) you are running something like hald

Because of 1) you could not do anything

because od 2) you may even have problems with an original cdrecord
from:

http://cdrecord.berlios.de

Cdrecord (is installed suid root) will definitely be able to open the device
and write to it. If hald behaves non-cooperatively, you may see burning
aborts that look like buffer underruns. In this case, you need to disable hald
before burning.

This is largely unnecessary in newer Ubuntu releases.

Thank you for your bug report. Is this still an issue in Ubuntu Intrepid?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
BugSquad

I assume this applies as well to the Baltix distro.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
Ubuntu BugSquad

I'm experiencing the same problem on Kubuntu 9.10 Karmic Koala. I am unable to find the original cdrecord in the repositories. I get the same error whether or not hald is running. I did not check the log files for k3b failing, but I get the exact same output when I try to use wodim directly. I even get the same errors when I log in as root and run the commands (I enabled the account).

I don't see why this is unnecessary in newer releases. I don't see a replacement for k3b in ubuntu, and it would probably use wodim anyway. Anyway, here is my output from the command line

$ wodim -v dev=/dev/scd0 fs=1536M speed=32 -eject -dao myimage.iso
TOC Type: 1 = CD-ROM
scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
Error trying to open /dev/scd0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy)... giving up.
wodim: Device or resource busy.
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.
$ 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.
$ wodim -scanbus
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.

That should probably be /dev/sr0, but it's the same results either way. I used to get reprimanded by cdrecord for using the device names, so I switched to bus id's. Now I'm getting reprimanded for using bus id's, so I'm switching my scrips back.

It is wrong not to use the bus id's. This has been in the documentation
since 1996 and this did never change. The person who created the fork
wodim just does not understand the constraints in the Linux kernel and
gives wrong advise.

As mentioned above already, wodim is a defective fork from an extremely
old version of cdrecord and wodim is unmaintained. Wodim incorrectly
interfaces to hald and for this reason, it under some condifions is completely
unable to open the writer device. Note that all known issues with wodim go
away if you upgrade to recent original software from:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

http://cdrecord.berlios.de/

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 503186, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.