Can't burn wiht k3b

alkos333 · 03-29-2007, 08:08 PM

I'm running Slackware 11.0, 2.6.20.

I'm trying to run k3b to burn my CDs.

Here are the things I installed:

kdelibs-3.5.4-i486-1
cdparanoia-IIIalpha9.8-i486-2
cdrtools-2.01-i486-1
cdrdao-1.2.1-i486-1

When I launch k3b, I get the following:

http://img402.imageshack.us/img402/9013/ssbv0.jpg

Since I got that error, I tried searching k3bsetup manually and found it in /opt/kde/bin/k3bsetup and
tried running it:

Code:

me@alkos333:~$ k3bsetup 
/opt/kde/bin/k3bsetup: line 20: kdesu: command not found
me@alkos333:~$ ICE default IO error handler doing an exit(), pid = 9151, errno = 0

I found that kdesu was located in kdebase-3.5.4-i486-7 and installed it. Ran k3bsetup again and it changed permissions
accordingly and said it was successful. I then tried running k3b and no errors were reported this
time. However, when I tried burning an ISO, I got the following again:

http://img253.imageshack.us/img253/8559/ssqq7.jpg

What's k3bsetup2 and where do I get it?

{BBI}Nexus{BBI} · 03-29-2007, 08:21 PM

In the K3b program it's in Settings --> Setup System Permissions. Your will need to enter your root password to continue.

MS3FGX · 03-29-2007, 08:26 PM

I am fairly sure k3bsetup and k3bsetup2 are the same thing. I am not sure what the deal is with the two names, but I know that I have only ever used the k3bsetup binary to configure K3B.

Not sure why it isn't letting you burn if k3bsetup doesn't detect any errors though. It has been so long since I actually configured my burners that I don't recall if any special adjustments were required.

alkos333 · 03-29-2007, 09:18 PM

Ok, I set up my permissions, so that k3b starts and doesn't complain about a thing:

Code:

crw-rw-rw- 1 root cdrom   21, 1 2007-03-29 09:55 /dev/sg1
brw-rw-rw- 1 root cdrom   11, 0 2007-03-29 09:55 /dev/sr0
-rwxr-xr-x 1 root root  2263284 2006-08-23 22:49 /opt/kde/bin/k3b*
-rwsr-xr-x 1 root root   572308 2006-05-04 20:14 /usr/bin/cdrdao*
-rwxr-xr-x 1 root root   317404 2004-09-09 18:41 /usr/bin/cdrecord*

Looks like a scsi drive:

Code:

root@alkos333:~# dmesg | grep CD-ROM
scsi 1:0:0:0: CD-ROM            MATSHITA UJDA765 DVD/CDRW 1.70 PQ: 0 ANSI: 5
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0

However, if I go and try to burn an ISO onto my CD-ROM, I get the following:

http://img253.imageshack.us/img253/8559/ssqq7.jpg

masonm · 03-29-2007, 09:36 PM

Manually set the permissions for cdrecord to 755

H_TeXMeX_H · 03-29-2007, 09:40 PM

I always run k3b as root, because it needs numerous permissions in order to burn properly. So, you already tried running it as root ?

alkos333 · 03-29-2007, 11:06 PM

Yeah, I just tried running k3b as a root and it worked flawlessly. I would prefer not to run it as a root. My root isn't even allowed to connect to X. I had to do 'xhost +' and DISPLAY=:0.0

I would not want to run it as a root. Others have been able to run it without root, so I see no reason why I should.

anon243 · 03-30-2007, 01:48 AM

Hi.

Try run kuser and include yourself in the cdrom group that should help.

masonm · 03-30-2007, 08:07 AM

With the newer 2.6 kernels k3b is going to complain if cdrecord isn't set with the proper permissions. That's why the k3bsetup2 was released.

Unless it sees cdrecord set with 755 root.root it is simply going to refuse.

Use the super user file manager in KDE, right click /usr/bin/cdrecord and open the permissions tab. Under advanced permissions make sure that all 3 user boxes are checked and that group and others only have read and execute permissions. Also make sure all three "special" boxes are unchecked. Click ok, and ok. k3b should now run for you.

alkos333 · 03-30-2007, 10:09 AM

Quote:

Originally Posted by Errotan

Hi.

Try run kuser and include yourself in the cdrom group that should help.

Already was included in the group:

Code:

[me@alkos333:~$ id
uid=1000(me) gid=100(users) groups=11(floppy),17(audio),18(video),19(cdrom),100(users),104(qemu)

alkos333 · 03-30-2007, 10:11 AM

Quote:

Originally Posted by masonm

With the newer 2.6 kernels k3b is going to complain if cdrecord isn't set with the proper permissions. That's why the k3bsetup2 was released.

Unless it sees cdrecord set with 755 root.root it is simply going to refuse.

Use the super user file manager in KDE, right click /usr/bin/cdrecord and open the permissions tab. Under advanced permissions make sure that all 3 user boxes are checked and that group and others only have read and execute permissions. Also make sure all three "special" boxes are unchecked. Click ok, and ok. k3b should now run for you.

I don't use kde. Besides, I already did all those things manually and pasted an output of ls -l
of "all" files involved. Look above.

K3b used to complain about cdrecord permissions and all that stuff on startup. After I fixed all
all of my permissions manually, it stopped doing that, but when it gets to the burning part, it
says cdrecord doesn't have permissions to access the drive, which doesn't make any sense at all
because it should.

alkos333 · 03-30-2007, 10:25 AM

Here is a command that k3b ran. I decided to run it manually and see what output it gives me:

Code:

me@alkos333:~$ /usr/bin/cdrecord -v gracetime=2 dev=1,0,0 speed=24 -dao driveropts=burnfree -eject -data /home/me/testing/slackware-11.0-install-d2.iso 
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
/usr/bin/cdrecord: Warning: Running on Linux-2.6.20
/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
TOC Type: 1 = CD-ROM
/usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
/usr/bin/cdrecord: Permission denied. Cannot open '/dev/sg0'. Cannot open SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

Like I said, I ran it as a root and things worked fine. However, others said it runs fine from a normal user, which is what I'm trying to achieve.

alibar · 03-30-2007, 11:04 AM

Okay this is a complete newbie comment so please don't shoot me down, but i had problem buring cd's when i first installed, i wasnt aware that you dont mount the drive before burning. Oh and 1 more thing k3b has problems burning under kernel versions equal to or above 2.6.XX have you tried uninstalling it and downloading an uptodate version.

REMEMBER

here.

masonm · 03-30-2007, 11:29 AM

Quote:

Originally Posted by alkos333

I don't use kde. Besides, I already did all those things manually and pasted an output of ls -l
of "all" files involved. Look above.

K3b used to complain about cdrecord permissions and all that stuff on startup. After I fixed all
all of my permissions manually, it stopped doing that, but when it gets to the burning part, it
says cdrecord doesn't have permissions to access the drive, which doesn't make any sense at all
because it should.

Sorry, I missed the post where you posted your permissions. I compared that with my own, which works fine as normal user, and this is the one thing I spotted that is different:

19032 -rws--x--x 1 root root 559K 2006-05-04 20:14 /usr/bin/cdrdao*

alkos333 · 03-30-2007, 12:14 PM

Quote:

Originally Posted by masonm

Sorry, I missed the post where you posted your permissions. I compared that with my own, which works fine as normal user, and this is the one thing I spotted that is different:

19032 -rws--x--x 1 root root 559K 2006-05-04 20:14 /usr/bin/cdrdao*

The fact that your cdrdao executable doesn't have read permissions for anybody, but the owner is completely irrelevant in my case.

What kernel are you running?