k3b does not burn

[sisqonrw]

Hi my k3b does not burn.
i get this german error message:

cdrecord hat ungenügende Zugriffsrechte um das Gerät zu öffnen.
cdrecord has not access privileges to open the device.

http://paste.ubuntuusers.de/409397/

the settings you can find here:

http://is.gd/sWTy5e

[OneLine]

Kubuntuguide is suggesting: http://ubuntuguide.org/wiki/Kubuntu:...e_device_error

[sisqonrw]

i have done this:

sudo chmod 777 /dev/sr0

but i get the same error report.

[gnomek]

You can also check permissions of the folder to which /dev/sr0 is mounted. Perhaps it would be good to reboot after changes.

drwxr-xr-x    4 root root  4096 lip  2 17:55 media
drwxr-xr-x  2 root    root   4096 maj 24 15:20 cdrom

Check also fstab entry. I have:

#cdwriter
/dev/cdrom /media/cdrom udf,iso9660 rw,noauto,user,exec,utf8 0 0

[sisqonrw]

please let me know the command for both.

my fstab is here:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda6 during installation
UUID=1b7aac6b-792e-4015-a96c-a014536d6a3e / ext3 errors=remount-ro 0 1
# /home was on /dev/sda7 during installation
UUID=ce9152af-a986-4612-a3d0-84b7c8d607d7 /home ext3 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=5f4808db-3b9a-41ed-85a4-9e5f30ebebaa none swap sw 0 0

[vinnywright]

cat /etc/fstab

will show you the fstab file .........mine dosent even show a cd/dvd device but K3b works perfectly .

vinny@Vinnys-HP-G62:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=686ed85e-a21b-4a72-aa03-5e9b6c7d50b0 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=e1f3a7e8-8884-4598-a25c-ecb5056462c9 /home ext4 defaults 0 2
# swap was on /dev/sda1 during installation
UUID=89534f2e-ad31-4941-87b0-22e9875efac8 none swap sw 0 0

and this will show the related info from /dev

ls -l /dev | grep sr0

hears mine

vinny@Vinnys-HP-G62:~$ ls -l /dev | grep sr0
lrwxrwxrwx 1 root root 3 Jul 4 12:13 cdrom3 -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 12:13 cdrw3 -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 12:13 dvd3 -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 12:13 dvdrw3 -> sr0
brw-rw----+ 1 root cdrom 11, 0 Jul 4 12:13 sr0

on the settings page in your first post did you check all the boxes and apply the changes ?

VINNY

[sisqonrw]

here the results of the both commands:

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda6 during installation
UUID=1b7aac6b-792e-4015-a96c-a014536d6a3e / ext3 errors=remount-ro 0 1
# /home was on /dev/sda7 during installation
UUID=ce9152af-a986-4612-a3d0-84b7c8d607d7 /home ext3 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=5f4808db-3b9a-41ed-85a4-9e5f30ebebaa none swap sw 0 0


ls -l /dev | grep sr0
lrwxrwxrwx 1 root root 3 Jul 4 21:31 cdrom -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 21:31 cdrw -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 21:31 dvd -> sr0
lrwxrwxrwx 1 root root 3 Jul 4 21:31 dvdrw -> sr0
brw-rw----+ 1 root cdrom 11, 0 Jul 4 21:31 sr0

is every think ok? or should i have to edit something?

what should i check on the settings?

[gnomek]

My settings are different
http://img31.otofotki.pl/ot71_k3b-.png.html
As you can see I didn't mark burning group.

Check if this user belongs to cdrom group. Just type in Konsole: id, or check in system settings → user management

Learn about fstab
https://help.ubuntu.com/community/Fstab
http://ubuntuforums.org/showthread.php?t=283131

When I add appropriate entry about cd/dvd drive to fstab it mounts it with appropriate permissions on every boot. I don't know if it is necessary for k3b to work properly, but it may be the case here.

[sisqonrw]

Wenn i do this. i get the error message

there is not a group "burning"

when i type id i get this:

id
uid=1000(salsero) gid=1000(salsero) Gruppen=1000(salsero),4(adm),24(cdrom),27(sudo),30 (dip),46(plugdev),109(lpadmin),121(sambashare)

i dont know why you can burn with the same settings and i can not burn....

[gnomek]

when i type id i get this:
id
24(cdrom),

That's ok. You are in cdrom group.

Wenn i do this. i get the error message
there is not a group "burning"

When you do what?
Compare my and your screenshots. I don't have "burning" group marked. And I have different permissions. I don't recall changing them so perhaps this is the result of adding entry to fstab.

Set all settings to default.
/home/user/.kde/share/config/
there is k3brc file. Copy it somewhere else and remove from this folder.

You can create /media/cdrom folder and check permissions, then:
add entry to fstab. Perhaps this may look like this:

#cdwriter
/dev/sr0 /media/cdrom udf,iso9660 rw,noauto,user,exec,utf8 0 0

and reboot and check.

To edit fstab you can use nano editor.

sudo nano /etc/fstab

Save by right Ctrl+O and quit by right Ctrl+X

[sisqonrw]

i have done it but it doesnt works

[weha]

Just checking. Is DMA on ?

sudo hdparm -I /dev/sr0|grep dma

* indicates which mode the drive is in.

[sisqonrw]

i get this:

sudo hdparm -I /dev/sr0|grep dma
[sudo] password for x:
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5

[gnomek]

Bad news - this is very old bug
https://bugs.launchpad.net/ubuntu/+s...it/+bug/149076
Search google for "cdrecord has not access privileges to open the device" or "Cannot raise RLIMIT_MEMLOCK limits".

[sisqonrw]

i am not a expert. is it possible to fix this problem? how can i do it?