k3b setup

tfrei · 10-11-2006, 11:49 AM

My new Slackware 11 works just fine. My problem is with setting up k3b. I called it up the first time and it encouraged me to run the setup program with root password--which I did. After that, it just did nothing. The program did not freeze, but it did not go forward with the setup program. Subsequent tries yielded the same result. I also tried setting it up through the KDE menu ("System--K3B Setup"), but nothing happens. Any ideas?

b0uncer · 10-11-2006, 11:53 AM

It's a good practise to run k3b from a terminal, so you'll probably get to see some messages that hopefully shed some more light on why the settings window won't open.

tfrei · 10-11-2006, 12:06 PM

Here is the output from the terminal:

k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi
k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption

and then further down:

k3b: (K3bDevice:

eviceManager) scanning fstab: /dev/hda1
k3b: (K3bDevice:

evice) Error: could not open device /dev/hda1for reading
k3b: could not open device /dev/hda1 (Permission denied)
k3b: /dev/hda1 resolved to /dev/hda1
k3b: (K3bDevice:

evice) Error: could not open device /dev/hda1for reading
k3b: could not open device /dev/hda1 (Permission denied)

and it runs through the devices, and then:

k3b: Devices:
k3b: ------------------------------
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3b::cutToWidth) not able to cut text to 26!
k3b: linux kernel version: 2.4.33.3
k3b: (K3bCore) System problems:
k3b: CRITICAL
k3b: PROBLEM: cdrecord will be run without root privileges
k3b: DETAILS: It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr.
k3b: SOLUTION: Use K3bSetup to solve this problem.
k3b:
k3b: CRITICAL
k3b: PROBLEM: cdrdao will be run without root privileges
k3b: DETAILS: It is highly recommended to configure cdrdao to run with root privileges to increase the overall stability of the burning process.
k3b: SOLUTION: Use K3bSetup to solve this problem.
k3b:

rickh · 10-11-2006, 12:12 PM

# chmod +s /usr/bin/cdrecord
# chmod +s /usr/bin/cdrdao

tfrei · 10-11-2006, 12:18 PM

Quote:

Originally Posted by rickh

# chmod +s /usr/bin/cdrecord
# chmod +s /usr/bin/cdrdao

Thanks. I imagine that will fix the permission problems, but I wonder why the k3b setup program stopped and couldn't accomplish the same?

tfrei · 10-11-2006, 12:37 PM

Did "chmod +s" to cdrecord and cdrdao as richk suggested. Thanks.

Now, k3b cannot find the device. This is my first time using k3b so I will look around for some help. In the meantime, if anybody has any specific ideas, you have my thanks in advance.

tfrei · 10-11-2006, 12:46 PM

Here is my output from cdrecord -scanbus:

Quote:

mycomputer~$ cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.8'.
scsibus1:
1,0,0 100) '' '' '' Removable not present Disk
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
scsibus2:
2,0,0 200) '' '' '' Removable not present Disk
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *

onebuck · 10-11-2006, 01:38 PM

Hi,

Which kernel?

Code:

uname -r                    #post release
uname -a                    #post all
dmesg |grep hd              #see the hd devices
dmesg |grep atapi           #what about atapi

The dmesg |grep will see what hardware is recognized at boot.

tfrei · 10-11-2006, 02:42 PM

Thanks for the tip. "grep" is cool. Here is the output. It didn't return anything for "atapi", but it returned devices for "scsi".

Quote:

mycomputer@tom:~$ uname -a
Linux tom 2.4.33.3 #1 Fri Sep 1 01:48:52 CDT 2006 i686 pentium4 i386 GNU/Linux

So, 2.4.33.3 kernel..

And here is everything else:

Quote:

mycomputer@tom:~$ dmesg |grep hd
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
mycomputer@tom:~$ dmesg |grep atapi
mycomputer@tom:~$ dmesg |grep scsi
scsi singledevice 0 0 0 0
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 4 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 6 0
scsi singledevice 0 0 7 0
scsi1 : SCSI emulation for USB Mass Storage devices
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0

tfrei · 10-11-2006, 03:35 PM

Update.

I had a line in lilo.conf wrong. I had "append=ide=scsi"; should be "append=ide-scsi". So now, reboot and "dmesg |grep ATAPI" gets me:

Quote:

mycomputer@tom:~$ dmesg |grep ATAPI
hdc: SAMSUNG CD-R/RW SW-252B, ATAPI CD/DVD-ROM drive
hdc: ATAPI 52X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
scsi0 : SCSI host adapter emulation for IDE ATAPI devices

k3b, however, still does not recognize the writer. Tried to add /dev/scsi0 via k3b configure, but no dice.

"cdrecord --scanbus" returns:

Quote:

mycomputer@tom:~$ cdrecord --scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

Update: Just tried k3b in root, and now it works. It still does not work as a regular user. The permission thing is really confusing to me.

anakin · 10-11-2006, 11:55 PM

Hi tfrei, I had the same permission problem with k3b in the past, but I use it with root access so it works just fine...I still have a problem with the screensaver in KDE 3.5.4, on my Slack 11 machine.I didnt have the problem when using 10.2...Can anyone help me ?By the way I run KDE as root but don't tell me not to do it, I just like it this way, if you could tell me a way to force the screensaver to work as root I would apreciate it...Thank you

tfrei · 10-12-2006, 12:48 PM

anakin: Your approach will work, but most people do not recommend it.

By the way, in a similar thread dedicated to k3b problems, the following solutions are given. I think they pretty much sum up the approaches you can use. They come from user dracolich:

Quote:

You have three choices, none of which includes changing the owner from root to a user:

1) K3B setup offers to create a group called burning and add your user to it.

2) Your hdc and hdd are both owned by the group called disk. Simply add your user to that group.

3) Add a line to your /etc/rc.d/rc.local to run during startup
Code:

chmod 666 /dev/hdc

But ... My problem from the beginning has been with k3bsetup (solution #1 above). It doesn't work. Here is my output as I try to call it up as root:

Quote:

root@tom:/opt/kde/bin# k3bsetup
kcmshell (kdelibs): WARNING: Could not find module 'k3bsetup2'.
root@tom:/opt/kde/bin#

Could it be that k3bsetup2 is missing? I'm running a fresh install of Slackware 11.0

JockVSJock · 10-12-2006, 01:22 PM

How are you running K3Bsetup?

Thru a terminal session?

Or from X (KDE) as root?

From this thread...

http://www.linuxforums.org/forum/sla...-k3b-root.html

UPDATE: Ok, I logged in as root and started X, and I tried to run K3B, but I still got the error message,

Code: