K3b permissions are driving me nuts!

[Norton Roman]

Well, well, I don't have this problem here, but I do recall I had it on
debian. The solution was that debian did not add me to the "cdrom" group by
default, which was necessary to use the device. In my ubuntu install I'm
part of that group... maybe that's the problem

and, of course, one can always put a script on rc.*, but tha's awful 8-).

Cheers

norton

2006/6/16, Lee McLain <lee.mclain at gmail.com>:
>
> 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.  I try to add that device(sg0) and K3bsetup tells me that it
> isn't a valid device.
>    I change the permissions of /dev/sg0 to 666 and K3b then works.
> Unfortunately, after rebooting, the permissions go back to what they were
> before.  This sucks.
>    What do I have to do to remedy this situation?  I believe that this was
> the same problem I had under Breezy and I had hoped that it would be fixed
> with Dapper.
>
> Thanks,
> Lee
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060616/2feba609/attachment.html>