LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 10-11-2006, 12:49 PM   #1
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Rep: Reputation: 16
k3b setup


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?
 
Old 10-11-2006, 12:53 PM   #2
b0uncer
Guru
 
Registered: Aug 2003
Distribution: CentOS, OS X
Posts: 5,131

Rep: Reputation: Disabled
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.
 
Old 10-11-2006, 01:06 PM   #3
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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:
 
Old 10-11-2006, 01:12 PM   #4
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 60
# chmod +s /usr/bin/cdrecord
# chmod +s /usr/bin/cdrdao
 
Old 10-11-2006, 01:18 PM   #5
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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?
 
Old 10-11-2006, 01:37 PM   #6
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
update

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.
 
Old 10-11-2006, 01:46 PM   #7
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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) *
 
Old 10-11-2006, 02:38 PM   #8
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,473
Blog Entries: 4

Rep: Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525
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.
 
Old 10-11-2006, 03:42 PM   #9
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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

Last edited by tfrei; 10-11-2006 at 05:11 PM.
 
Old 10-11-2006, 04:35 PM   #10
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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.

Last edited by tfrei; 10-11-2006 at 05:13 PM.
 
Old 10-12-2006, 12:55 AM   #11
anakin
LQ Newbie
 
Registered: Feb 2006
Location: Tirnaveni, Romania
Distribution: Slackware 12.2 (current)
Posts: 24

Rep: Reputation: 15
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
 
Old 10-12-2006, 01:48 PM   #12
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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

Last edited by tfrei; 10-12-2006 at 01:49 PM.
 
Old 10-12-2006, 02:22 PM   #13
JockVSJock
Member
 
Registered: Jan 2004
Posts: 636

Rep: Reputation: 31
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:
there is no group burning

Last edited by JockVSJock; 10-12-2006 at 02:26 PM.
 
Old 10-12-2006, 02:55 PM   #14
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
The output you see in the previous post was from a konsole terminal inside KDE, running as root.
 
Old 10-12-2006, 02:58 PM   #15
JockVSJock
Member
 
Registered: Jan 2004
Posts: 636

Rep: Reputation: 31
Quote:
Originally Posted by tfrei
The output you see in the previous post was from a konsole terminal inside KDE, running as root.
Try logging into X as root and running K3Bsetup from there and see what happens?

thanks
 
  


Reply

Tags
k3b


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
k3b Setup Soulful93 Linux - Software 5 05-06-2005 01:56 PM
K3B setup problem THX1138 Linux - Software 3 03-30-2005 12:29 AM
no K3B setup? so it doesn't recog. the CDRW Trinity22 Linux - Software 1 03-28-2005 12:25 AM
k3b setup johnyy Linux - Software 10 06-23-2003 08:01 AM
k3b setup Ice9 Linux - Software 3 01-26-2003 10:45 AM


All times are GMT -5. The time now is 07:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration