Hello, I've been attempting to burn a CD as user for the past 4 hours and I just cant get it to work at all. I've used both k3b and xcdroast, but both spit out the same cdrecord error:

TOC Type: 1 = CD-ROM
/usr/bin/cdrecord: Warning: not running as root user, fs= option ignored.
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
/usr/bin/cdrecord: No such file or directory. Cannot open SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.


CD burning DOES work if I am root, and I've used k3bsetup to change my cdrecord permissions (I also temporarily chmoded cdrecord as 7777, although I still got the same error.)

I've burned as user before, although not in this current install of SuSE 9.
I have a burning group (which my login is linked to), and it is associated with cdrecord, cdrdao, and readcd.



What am I still missing?

Jeff

Check the permissions on the device(s),
presumably
ls -l /dev/scd0
and
ls -l /dev/sg0


Cheers,
Tink

The permissions are listed below:

scd0
brw-rw-rw- 1 root disk 11, 0 2003-09-23 17:59 /dev/scd0

sg0
crw-rw-rw- 1 root disk 21, 0 2003-09-23 17:59 /dev/sg0

do a
chmod a+x /dev/sg0
and try again ...


Cheers,
Tink

arrr.

I did it, and I still get the same error:

/usr/bin/cdrecord: Warning: not running as root user, fs= option ignored.
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
/usr/bin/cdrecord: No such file or directory. Cannot open SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

try this like root:

chmod +s /usr/bin/cdrecord

after this try to burn you cd as normal user

^Tried it, still getting the same very annoying error.

/usr/bin/cdrecord: Warning: not running as root user, fs= option ignored.
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
/usr/bin/cdrecord: No such file or directory. Cannot open SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.


Are there any other files that are used that could have the wrong privileges specified one way or another?

Well, I figured it out, and so that no one else ever has to endure this, here is the solution.

1. This ONLY happens in SuSE 9, and hopefully this will be the only distro it ever happens in.

Ok, here goes.

SuSE's goofy version of cdrecord requires something called 'resmgr' to be running for regular users in order to burn cd's as a non-root user. However, resmgr is not setup this way by default! On top of this, there is no documentation that explains this!

So... heres how to fix it.

One:

Open a terminal window su to root
Type:

resmgr login <username> :0

Use the login you wish to burn cds on, as your already root.

CD's should burn!

Of course, now you want this to run all the time.
This information is stored in the pam damon.

Navigate to
/etc/pam.d and open 'login'
Add the line
'session optional pam_resmgr.so grant=desktop '

This will load the resmgr correctly.

If you have a 'kde' file in the pam directory, add the line to it as well.


But, there is a better way.

Go to www.rpmseek.com and find a different rpm version of cdrecord. I simply installed a redhat 9 version of cdrecord.

This removes all of suses goofy proprietary code from cdrecord and allows it to work the way it should!

If you want to compile cdrecord yourself, you can do this as well, although compiling cdrecord is not exactly fun.


Goodluck!

I was just thinking about this when I saw this thread. I'm also using SuSE 9 and couldn't understand why I needed to be root to burn...but I solved it by doing "sudo gcombust"

I had similar problem using Libranet 2.8.1; k3b 0.10.3

knew it had to be a permissions problem, as root could run k3b without problem.

i set up a group burning that includes me, and set cdrecord group to burning. that is pretty standard. also made cdrecord executable by group, also pretty standard.

but, it still wasn't working for me.

here is the catch, I think .... cdrecord is a shell script. i made it readable by group as well (in addition to executable). don't know if my reasoning was correct, but all is now working perfectly as regular user.

Regards,

RDC

have run k3bsetup ? That should change the needed settings so you can run as regular user.