I should have been more clear. That is what I did. Logged in as root, started up X, and then tried to run K3bsetup through a terminal. There was no menu option to call it up through X directly.

Really?

Nothing under:

/K Menu/System/K3bsetup

?

Hi,

From console as root;
Make sure your PATH is correct. If not be absolute with the command;

@tfrei

The only thing k3bsetup is going to be used for is to
change cdrdao and cdrecord to this condition

---------
-rwsr-xr-x 1 root burning 572308 2006-05-04 21:14 cdrdao
-rwxr-xr-x 1 root burning 317404 2004-09-09 19:41 cdrecord
---------

I think its a little overkill to install kdebase package
just to see kdesu -> k3bsetup work.

1. You need to create a group called `burning' (k3b uses
this group)
# groupadd burning

2. change ownership on cdrdao and cdrecord to the above
condition
# chown root:burning /usr/bin/cdrdao
# chown root:burning /usr/bin/cdrecord

3. Change permision on cdrdao to the above condition
# chmod 4755 /usr/bin/cdrdao
--Where execute, for user, is going to be set to `set user ID'

Good Luck

-W

mokele, thanks. I've already done:

and

Question: Is "chmod 4755" = "chmod +s" ?

I think not. if you set execute to `set user ID'
using +s, you get a capital S on user execute. I'm
not sure what it is and I've had troubles before
using letters whenever I have to set any ID that are
not r-w-x. So, for `set user ID' I always use number
as explained in the slack-book. Its just one page.

When I had this trouble I fixed this on a step by step
basis. I saw you are going to change execute to `set user ID'
on cdrecord too. If I'm not mistaken its not necessary.

Try changing permissions only on cdrdao alone and see if
that solves the problem, if not change cdrecord too.

-W

Thanks again, mokele. Your reference to the slackbook entry is what I really need to learn.

I implemented your suggestions and k3b complains it doesn't have a writer. I'm tempted to "chmod 666 /dev/hdc", but I suspect there is a more elegant way to do this by adding me, the user, to the right group in /etc/group. I'll probably work my way through this one way or another.

But still, the initial problem is with k3bsetup:

1) Yes, I have k3bsetup, but it stops after I enter the password for root.

2) k3bsetup calls up k3bsetup2, which does not exist--as far as I can see.

3) Does anybody else see this?

For now, smarter people can figure out that problem. I'll try to concentrate on how a regular user can have k3b recognize the writer.

Did a "chmod 666 /dev/cdrom" and all is well with the world.

I thought I read somewhere that this is not the best solution, but I it does work.

Thank you for everybody's help.

This is all very odd

If as user you

cd /opt/kde/bin
kcmshell k3bsetup2

You can bring up the k3bsetup screen. Administrator mode does not work and there are numerous errors on the console

kdesu kcmshell k3bsetup2
After entering the password nothing happens

If you log on as root and try it the k3b2setp module cannot be found

Judging from the setup screen the changes that are supposed to be made are
chmod 666 /dev/hda
chmod 4711 /usr/bin/cdrdao
chmod 755 /usr/bin/cdrecord
chmod 4711 /usr/bin/growisofs

I experienced this exact same problem back when I first ran Slack 10.2 and installed the k3b package from linuxpackages.net. K3bSetup just didn't run from the GUI, and I got the exact same error you get from the command line.

My solution was to delete a file (which got recreated automatically after I deleted it). Unfortunately, its been so long since that happened that I can't remember the exact directory and filename of the file I deleted. Apparently that file had some cached information that was keeping K3bsetup from starting, and deleting it so that it recreated a fresh file corrected the problem.I know that isn't very specific, but maybe it can point in the right direction. I eventually found that answer after many many Google searches.

Also, I found this here:

http://www.linuxpackages.net/view_co...=3250&cid=1793

May be worth trying if nothing else has helped so far.....

It probably does not matter. In my case the permissions have been set manually and as far as I can see k3b itself is running fine.

In fact even before I set the permissions all I needed to do was add myself to the cdrom group. Changing tje permissions has stopped k3b complaining about them when I run it.