k3b permissions?

smyle · 12-14-2004, 11:59 AM

I'm using SuSE 9.1 pro. I was able to use k3b just fine until recently. I switched from local login to NIS, and now k3b gets to "Creating GUI..." and locks. Works fine if I login as root. Sure sounds like a permissions problem, right?

I've googled and have yet to find the answer to this question: what permissions does k3b need to have to be happy?

sbassett · 12-14-2004, 12:12 PM

Definitely check out http://www.faqs.org/docs/linux_netwo...is.passwd.html and make sure all is mapped correctly, I believe k3b uses group burning, are the users still part of burning?

TMH · 12-14-2004, 12:13 PM

I believe you need to be in the cdrom and cdrw groups if they exist on your system. Failing that, chowning your group to /dev/cdrom0 or whatever your cdrom is should do the trick. However, k3b does some neat optimisation tricks when it's run as root, so maybe you shouldn't be going down that route anyway.

sbassett · 12-14-2004, 01:22 PM

I believe you might be correct in the 2.6 kernel scheme. Usually, your hdc will be owned by logged in user:disk. <- correct if I am wrong. But if you are using k3b from source, k3bsetup will set perms for cdrecord cdrdao and hdc as root:burning with all being modded 660. Again, correct me if I am wrong. It has been a few months since I have used suse.

smyle · 12-15-2004, 04:56 PM

Thanks sbassett!

I'd looked at perms on cdrecord and cdrdao, but not at the devices themselves. They were, indeed, owned by 'disk', and after changing that to 'users', k3b fires up flawlessly.

Sorry for the late reply. Naturally, as soon as I posted the question, things got busy at work.