Hi there,

ive installed Sarge with 2.6.8 Kernel and K3b on my PC.

When I start K3b with as an user, k3b will start the wizard and recognize one DVD burner and one DVD-rom. Thats correct.
After this if I am trying to burn an CD I am not able to choose a burner within the appearing dialog, even if everything seems set up fine (added a burning group and so on.
groups on /dev/hdb /dev/hdc are set to root:burning

so i am not able to burn because i cannot choose the burner.

if i login as root (within X!!!) everything is working. I am able to choose a burner.

what am i doing wrong? when i got debian/sarge some months ago I did exactly the same things and everything was working well. after reinstall i ran into these problems.

as well k3b wont recognize dvd+rw-tools anymore, even they are installed. root or user doesnt matter in this case.


any ideas? thx for help.

After creating the "burning" group, did you add yourself to the new group?

What are the permissions on the dvd-burner device set to? Are they set to
brw-rw----, if not they should be... The burning group has to have permission
to write to the device.

/Les

hi. thx for reply.

well i set the attribs to rw-rw-rw to be sure and i added myself to the group (and restarted to be sure i was added).

on another forum for fedora ive read about changing some parameters in udev and it should work. but i have no idea what this udev is about.

i gathered some information from k3b. it seems the 2.6.8 and 2.6.9 kernels are buggy in this case. so downgrading should be the best solution till the problem is fixed. :-(
the sad thing is, that it already worked with an 2.6.8 kernel, till they patched something to death. sigh.

http://www.k3b.org/
http://k3b.plainblack.com/index.pl/news2

yeah. i have the same problem with sarge. very annoying, but hey - you can always buy windows!

There also appears to be a setuid issue for cdrecord on the 2.6.9 kernel.
See the second link you posted. Make sure that cdrecord is not setuid.

# ls -al /usr/bin/cdrecord
-rwxr-xr-x 1 root root 344908 Sep 29 05:33 /usr/bin/cdrecord
#

I decided to check k3b as well:

# ls -al /usr/bin/k3b
-rwxr-xr-x 1 root root 1692328 Oct 13 07:57 /usr/bin/k3b
#

Same permissions (this is from FC2: 2.6.9-1.6_FC2).

HTH,
/Les

Not sure about "udev", I'm not using it yet so I can't comment. It is something new in FC3 and
possibly sarge. There is a good writeup on how to create custom udev rules in the Dec 2004
Redhat Magazine: http://www.redhat.com/magazine/002dec04/features/udev/

I really don't think this will solve your problem, as you've already set the permissions to what
they should be. Although, you may want to check that the permissions have survived the reboot.
If they haven't then depending on what is controlling the device permissions, you may have to
either adjust the settings in pam or udev (or possibly both)...

/Les