I had the same problem, k3bsetup2 and chmod 4750 didn't solve the problem because there was another /dev/sg entry with bad permissions. k3bsetup didn't detect this entry:
crw-rw---- 1 root root 21, 0 2006-06-09 20:10 /dev/sg0 crw-rw-rw- 1 root cdrom 21, 1 2006-06-09 20:10 /dev/sg1 Then, doing cdrecord -scanbus, the output was: Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second. cdrecord: Device or resource busy. Cannot open '/dev/sg0'. Cannot open SCSI driver. For me the solution was simple: I deleted /dev/sg0 :) -- k3b and cdrecord priviliges problems https://launchpad.net/bugs/32039 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
