LinuxQuestions.org - Cd burning with K3B on Fedora 2 or3

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - Cd burning with K3B on Fedora 2 or3 (https://www.linuxquestions.org/questions/fedora-35/cd-burning-with-k3b-on-fedora-2-or3-252082/)

Cd burning with K3B on Fedora 2 or3

Using kde/k3b in user or root have problems of burning cd's.
Using Gnome/cdwriter user or root , burns cd's with no problems.
K3b keeps saying it has problems with cdrecord.
What's gives, is Redhat up to their old way's of tormenting us Kde users ?

Jim

What does k3b say exactly?

I was having the same difficulty and have been jumping from KDE to Gnome for my burning needs.I am slowly resolving the problem as I learn more.I ran " cdrecord -scanbus " from a terminal and it showed my cd-writer but it was not enabled for writing.I can't recall exactly how I enabled it but someone here will.I also went to K3b and checked my preferences and along the way I went to a site with a good tute on using K3b___http://fedoranews.org/mweber/. After making one tick mark in a box I was off and running.

We should not mix problems here. That most recent Fedora Core 2 update kernel 2.6.8-1.521 disables CD burners is something else. It's a kernel security feature which will be fixed in a future FC2 update. Meanwhile you either need to become root or try the newer kernel from the updates-testing repository for FC2.

Does anyone know of a work around for the cd burning problem associated with
the FC2 2.6.8 kernel? (no matter how ugly)

Have you tried the most recent FC2 update kernel yet? kernel-2.6.9-1.3_FC2

Re: Cd burning with K3B on Fedora 2 or3

Quote:

Originally posted by mickeyboa
Using kde/k3b in user or root have problems of burning cd's.
Using Gnome/cdwriter user or root , burns cd's with no problems.
K3b keeps saying it has problems with cdrecord.
What's gives, is Redhat up to their old way's of tormenting us Kde users ?

Jim

Go to the K3B web site for info on this. It doesn't have to do with Fedora per se, but with the 2.6 kernel. The authors of K3B are aware of the issue,

bl

There is no SCSI emulation for ATAPI (IDE) connected CD/DVD devices in FC2 (kernel 2.6).

This is why you have to scan for ATAPI burners with:

Code:

cdrecord dev=ATAPI: -scanbus

and select it with

Code:

cdrecord dev=ATAPI:x,y,z ...

Linus Torvalds comment

Quote:

The "somebody" strongly felt that ide-scsi was not just ugly but _evil_, and that the syntax and usage of "cdrecord" was absolutely stupid.

That somebody was me.

ide-scsi has always been broken. You should not use it, and indeed there was never any good reason for it existing AT ALL. But because of a broken interface to cdrecord, cdrecord historically only wanted to touch SCSI devices. Ergo, a silly emulation layer that wasn't really worth it.

The fact that nobody has bothered to fix ide-scsi seems to be a result of nobody _wanting_ to really fix it.

So don't use it. Or if you do use it, send the fixes over.

K3B News

Quote:

Do not use Kernel 2.6.8

A patch that was introduced into the kernel shortly before the 2.6.8 release makes K3b and also the dvd+rw-tools unusable on Linux (unless run as root but that is not recommended). The very important GET CONFIGURATION MMC command is rejected by the kernel for reasons I cannot see and writing commands like MODE SELECT also fail (K3b cannot detect CD writers without it) even when the device is opened O_RDWR. Until this issue has been solved I strongly recommend to stick to kernel version 2.6.7.

Update: The kernel guys are currently fixing the problem so the next kernel release should work again. :)

Update 2: The problem is NOT fixed in 2.6.8.1

Update 3: Be aware that kernel 2.6.8 also contains the memory leak which makes it impossible to write audio cds, even as root.

Quote:

Does anyone know of a work around for the cd burning problem associated with
the FC2 2.6.8 kernel? (no matter how ugly)

Code:

su -

Password:

k3b

;)

Boby

Actually, you would simply use cdrecord -dev=/dev/cdwriter ...

Thanks for your reply....

A little more background....I run fedora core 2. I am unable to burn CD's as a regular user, and must become root to do so. Obviously, this is not a good practice, and should be unnecessary.

I searched the posting at this site and have tried the following:

-updated cdrecord and cdrdao.
-manually going in and setting the setuid and setgid
bits on these two files (a practice I don't really like)
-running the latest k3b (0.11.17).
-I have searched but am unable to find the file k3bsetup2 anywhere on my harddrive, as was suggested in earlier posts.
I attempted to run k3bsetup using the kcmshell and get
session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. There is no facility under the menu /settings in the gui itself for modifying permissions

About the only thing that was suggested in earlier posts is that I haven't done is use a different kernel, which, to me, seems unnecessary. If something is having permission issues, I'd like to find the 'rc' file the controls it, and change it. If there is some file (or device) that needs elevated privileges, I'd like to identify that, and do it a smart way.

Thanks for any help

rhythmsection,

please read my earlier reply, and don't ignore the other replies either. The CD writing problem in Linux 2.6.8 is by design. It is the result of a security fix which takes away the ability to send arbitrary raw commands.

Please get the most recent kernel for FC2: kernel-2.6.9-1.3_FC2

And please downgrade k3b to the version from FC2 Updates. Else you're missing patches.

k3bsetup2 is not included, because it is not needed. This is mentioned in the FC2 release notes, too.

i stopped useing K3B for all the problems that have been listed above
i installed xcdroast which seems to do all i want for burning cd's...

jolly1701,

I got xcdroast, but get the following error when I attempt to blank a cd
'cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer.'

DId you run into this? I set the setuid and setgid bits on cdrecord, but did not help

Thanks

Whether k3b or xcdroast, both depend on cdrecord and are affected by kernel 2.6.8.

Quote:

I set the setuid and setgid bits on cdrecord, but did not help

Setting those bits is not necessary anyway.

misc,

Guess I'll do without for a while (I can use our Mac to burn CDs - I can scp files from my linux box to our Mac).

I don't really want to upgrade the kernel
right now, since I don't want to discover any "new features" that break other things I have working - one of which is
nvidia has a kernel module for 3D acceleration for my kernel version.

As versitile as linux (and especially Fedora) is, it's suprising that the only solution to this problem is
a kernel upgrade, as opposed to an adjustment to a configuration somewhere.

thanks for your help