Hi all

When I try to format a DVD with K3B (Version 0.12.015)as a normal user it fails with the message below that I am not a root user. When I log in as administrator it formats the DVD no worries. Where or what permissions do I change to use this function as normal user when using K3B.

I am using Fedora Core 5 64 Bit on my Athlon with latest k3B update.

I use K3B under Ubuntu on my laptop and dont remember setting or having this problem.

Look forward to any help you can give me on this one.

Cheers

Gimmee





System
-----------------------
K3b Version: 0.12.15

KDE Version: 3.5.1-2.3 Red Hat
QT Version: 3.3.6
Kernel: 2.6.17-1.2174_FC5
Devices
-----------------------
PIONEER DVD-RW DVR-109 1.57 (/dev/hda, ) at [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD-R DL; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-R Dual Layer Sequential; DVD-R Dual Layer Jump; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R; Restricted Overwrite; Layer Jump]

dvd+rw-format
-----------------------
* DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 4.10.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Trying to open without locking.
* 4.7GB DVD-RW media in Sequential mode detected.
umount: /media/disk is not in the fstab (and you are not root)
:-( unable to proceed with format: Device or resource busy

dvd+rw-format command:
-----------------------
/usr/bin/dvd+rw-format -gui -blank /dev/hda

this is just a wild guess, but seeing the line about not in fstab, makes me thing putting it there may help. Does the directory /media/disc exist?
If so you could try making an entry in fstab with "user, rw" options.

This is my entry from FC4, trouble is FC5 manages moumting media a bit differently, so I'm not sure how much it will help.

/dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0

This problem of burning CD, DVD as user or have to use SU to burn
has been a problem all the way back from the start of the Fedora Core. What's even more weird is I have been able to burn DVD as user but not CD's
I have installed all five of the cores and have had this problem
with one box, but not another.
What blows my mind is why it can't be fixed.
I always open file manager SU and right click on a file > actions
and start k3b from there.

Jim

Hi all thanks heaps for those helpful replies.

Looks like I will be doing switch user a bit more or as I am doing now just using my laptop with Ubuntu to Format and burn DVD's.

Right whats my next little niggle in getting this Fedora Desktop up and running.

Cheers
New Zealand

and see what mode /dev/hda (your burner, right?) is.

I'm assuming this is a permissions issue.

you could probably do a chmod a+w /dev/hda (as root) and temporarily fix the problem. Trouble is SELinux goes behind you and undoes the mode, setting it back to 664 (ordinary user can't write to it) and you are hosed again.

FC5, Install FC6 ,you are not going to get it to work in FC5, I have installed FC6 on three computers and now I can write Cd, DVD's as user.
This has been a problem in previous Fedora cores, Some would work as user and some won't.
It is a permissions problem.

This may or may not be useful, but do a
"ls -l /dev/hd*" and check ownership and permissions for your burner (assuming that your burner is an internal ide device that gets mapped to /dev/hd[a-d])

I've just discovered that it's not SELinux or udev that sets permissions on removable media, but pam, see /etc/security/console.perms

When logging into my box via VNC, k3b didn't work as pam left the drive owned by root, mode 0660. If I logged in at the console (X or tty) k3b worked fine, and "ls -l /dev/hdc #my burner" showed that I owned it whenever I was logged on at the console, not just VNC.

If ls -l shows your burner as owned by root and mode 0660, then pam is not giving you ownership of the drive. If ls -l shows someone else owning the drive, then maybe somebody logged onto a tty before you logged on, and pam is keeping removable media under their ownership.

I solved my problem by editing
/etc/security/console.perms.d/50-default.perms

Hi there

Thanks for the useful replies. If I do a

[root@localhost ~]# ls -l /dev/hda
brw------- 1 katrina disk 3, 0 Nov 14 11:37 /dev/hda

So under each user it is owned by that user and fails to write the dvd unless K3B is started still as root from command line.

On my laptop with Ubuntu it is owned by root even though I am logged in as a user and I have never had a problem

Ubuntu:

gimmee@EVO6:~$ ls -l /dev/hda
brw-rw---- 1 root disk 3, 0 /dev/hda

RedCharlie can you tell me what you edited in your 50-default.perms. Here is mine below

# device classes -- these are shell-style globs
<floppy>=/dev/fd[0-1]* \
/dev/floppy* /mnt/floppy*
<sound>=/dev/dsp* /dev/audio* /dev/midi* \
/dev/mixer* /dev/sequencer \
/dev/sound/* /dev/beep \
/dev/snd/*
<cdrom>=/dev/cdrom* /dev/cdroms/* /dev/cdwriter* /mnt/cdrom*
<pilot>=/dev/pilot
<jaz>=/mnt/jaz*
<zip>=/mnt/pocketzip* /mnt/zip* /dev/zip*
<ls120>=/dev/ls120 /mnt/ls120*
<scanner>=/dev/scanner* /dev/usb/scanner*
<rio500>=/dev/usb/rio500
<camera>=/mnt/camera* /dev/usb/dc2xx* /dev/usb/mdc800*
<memstick>=/mnt/memstick*
<flash>=/mnt/flash* /dev/flash*
<diskonkey>=/mnt/diskonkey*
<rem_ide>=/mnt/microdrive*
<fb>=/dev/fb /dev/fb[0-9]* \
/dev/fb/*
<kbd>=/dev/kbd
<joystick>=/dev/js[0-9]*
<v4l>=/dev/video* /dev/radio* /dev/winradio* /dev/vtx* /dev/vbi* \
/dev/video/*
<gpm>=/dev/gpmctl
<dri>=/dev/nvidia* /dev/3dfx* /dev/dri/card*
<mainboard>=/dev/apm_bios
<pmu>=/dev/pmu
<bluetooth>=/dev/rfcomm*
<raw1394>=/dev/raw1394

# permission definitions
<console> 0660 <floppy> 0660 root.floppy
<console> 0600 <sound> 0600 root
<console> 0600 <cdrom> 0660 root.disk
<console> 0600 <pilot> 0660 root.uucp
<console> 0600 <jaz> 0660 root.disk
<console> 0600 <zip> 0660 root.disk
<console> 0600 <ls120> 0660 root.disk
<console> 0600 <scanner> 0600 root
<console> 0600 <camera> 0600 root.disk
<console> 0600 <memstick> 0600 root.disk
<console> 0600 <flash> 0600 root.disk
<console> 0600 <diskonkey> 0660 root.disk
<console> 0600 <rem_ide> 0660 root.disk
<console> 0600 <fb> 0600 root
<console> 0600 <kbd> 0600 root
<console> 0600 <joystick> 0600 root
<console> 0600 <v4l> 0600 root
<console> 0700 <gpm> 0700 root
<console> 0600 <mainboard> 0600 root
<console> 0600 <rio500> 0600 root
<console> 0600 <pmu> 0600 root
<console> 0600 <bluetooth> 0600 root
<console> 0600 <raw1394> 0600 root

<xconsole> 0600 /dev/console 0600 root.root
<console> 0600 <dri> 060

Yes I think upgrading to FC6 would be the answer but it has been a couple of months now on and off getting the hang of this linux business and one of the main stumbling blocks I have with Fedora is being on dial up and getting things installed and updated. It is so slow that I just dont want to go through it all again just yet. I definately will but just not yet.

Thanks

Gimmee

Yes, all I changed wastoso that the drive would be brw-rw-rw when NOBODY is logged in at the console. I.e. anybody can access the drive if nobody is logged in. Sounds contradictory, but it's because logging in via VNC doesn't count as being logged in "at the console"

Unless you are doing the same (accessing your box via VNC) I don't think doing what I did will be any help.

Question: your post above shows user "katrina" owning /dev/hda So, is it user "katrina" having trouble with k3b, or some other user logged in at the same time?

Reason I'm askin': If "katrina" is having trouble even when she owns and has rw permission on /dev/hda, then it doesn't look like it's a permission issue with the drive. k3b also needs a work space (I've set it to use /tmp) for writing image files (*.iso etc) If user "katrina" doesn't have permission to write to /tmp or whatever work space k3b is trying to use, that could also cause a situation where a normal user can't use k3b but root can. Just an idea.

(Also, if "katrina" is not the one having the trouble, then the solution may be as easy as having her log off and let whoever else wants to use the drive log on and pam will give the new user ownership of the drive. Alternately, you could change the cdrom line toand add all the users who want to use the drive to group "disk", or just open up the drive to all comers all the time withbut this could be a problem if multiple users are logged on and trying to use the drive at the same time.

Hi there RedCharlie

On this desktop there is only one person logged on at each time so if katrina is logged on it is katrina that cant use k3b and same as if I am logged on as gimmee i cant use k3b. If i log on as root then root can burn whatever on k3b no problems.

I like your idea about k3b needing workspace and maybe user does not have access to it. Will look into that next.

Thanks for the helpful comments

Gimmee

Hi there

I set the K3B workspace and made sure each user had correct permissions to use that space. All to no avail. Still can only burn and format dvd under root. Think I will just have to use my Ubuntu laptop for doing this until I can upgrade to FC6.

Thanks for all the help.