<div><div>Thanks Derek! That worked like a charm! I know that I am not the only one out there with this problem, so that fix needs to be applied to Ubuntu's wiki somewhere! Thanks again for your help!, Lee McLain </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Message: 6 Date: Mon, 19 Jun 2006 09:06:42 -0300 From: Derek Broughton < <a href="mailto:news@pointerstop.ca">news@pointerstop.ca</a>> Subject: Re: K3b permissions are driving me nuts! To: <a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a> Message-ID: < <a href="mailto:ijgim3-9vu.ln1@news.pointerstop.ca">ijgim3-9vu.ln1@news.pointerstop.ca</a>> Content-Type: text/plain; charset=us-ascii Lee McLain wrote: > Hi everyone, > This is an issue that is really bugging me and I can't seem to find a > proper fix for it. > I am running Dapper on an Inspiron 6000. K3b keeps telling me that > cdrecord doesn't have permission for the device. Upon further checking, > it seems that cdrecord is trying to use /dev/sg0 even though K3b says it's > using /dev/sg1. Really? I wouldn't expect the CD device to be on sg1, _but_ for scsi CD/DVDs k3b requires access to /dev/sg0 which is a scsi control device, and k3b doesn't report that. > I try to add that device(sg0) and K3bsetup tells me that > it isn't a valid device. Not for reading and writing on, anyway. > I change the permissions of /dev/sg0 to 666 and K3b then works. There's the clue - you should never need it to be 666. As Norton said, you should be in the cdrom group, but iirc some versions of udev don't actually make sg0 owned by cdrom, either, in which case you need to add the following to /etc/udev/rules.d/15local.rules (creating the file if necessary): BUS=="scsi", KERNEL=="sg[0-9]", NAME="%k", GROUP="cdrom" > Unfortunately, after rebooting, the permissions go back to what they were > before. This sucks. It's normal, since the device doesn't exist between boots. -- derek </blockquote></div>