K3b problems...

[Lee McLain]

Ok,  I did make sure that I am a member of the cdrom group.  I am and
it still does not work without either running K3b as root or changing
the permission on /dev/sg0.
Does anyone know why that device exists?  This is running on my Dell
Inspiron 6000 laptop.  On my desktop machine(also running Hoary), I
don't have that device at all.

Thanks,
Lee


> ------------------------------
> 
> Message: 2
> Date: Tue, 14 Jun 2005 21:12:27 -0400
> From: "Sean D. Quinn" <seandq at gmail.com>
> Subject: Re: K3b problems...
> To: Ubuntu Help and User Discussions <ubuntu-users at lists.ubuntu.com>,
>         Michael Beattie <mtbeedee at gmail.com>
> Cc: Lee McLain <lee.mclain at gmail.com>
> Message-ID: <1118797947.5472.1.camel at localhost.localdomain>
> Content-Type: text/plain
> 
> On Tue, 2005-06-14 at 21:01 -0400, Michael Beattie wrote:
> 
> > As long as your user is a member of the cdrom group it should work I
> > think.  Someone correct me if I am mistaken.
> 
> I think you are right. It works fine for me as normal non-root
> non-sudo'd user here.
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 14 Jun 2005 22:17:28 -0300
> From: Joel Goguen <jtgoguen at gmail.com>
> Subject: Re: K3b problems...
> To: Ubuntu Help and User Discussions <ubuntu-users at lists.ubuntu.com>,
>         Lee McLain <lee.mclain at gmail.com>
> Message-ID: <1118798248.18350.0.camel at localhost.localdomain>
> Content-Type: text/plain
> 
> Make sure you're a member of the cdrom group.  Or you could run k3b as
> root, but that's not really a fix IMO, just a prop to hide the need for
> a fix.
> 
> On Tue, 2005-14-06 at 20:42 -0400, Lee McLain wrote:
> > Hi all,
> >    I am having a bit of a problem with K3b.
> >    After starting it up, I can burn anything.  It says that cdrecord
> > does not have permission to use the device.
> >    I tried to change the permissions on /dev/sg0 so that all users can
> > read and write.  That solved the problem...temporarily.  When I
> > reboot, the permissions are changed back and the problem returns.
> >    Does anyone know how I would go about solving this problem?  Should
> > I be figuring out how to set the permissions of /dev/sg0 on boot or is
> > there some other "correct" way to fix the problem?
> >
> > Thanks,
> > Lee
> >
> 
> --
> Joel Goguen
> ITS Student Consultant
> Bachelor of Computer Science III
> University of New Brunswick
>