![](https://seccdn.libravatar.org/avatar/4500c2fdff620749d47e7e4637d59181.jpg?s=120&d=mm&r=g)
Hi Folks, During the setup of K3b on SUSE 9.2 it issued a msg box stating: "System Configuration Problems cdrecord does not run with root privileges 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. Solution: Use K3bSetup to solve this problem. cdrdao does not run with root privileges It is highly recommended to configure cdrdao to run with root privileges to increase the overall stability of the burning process. Solution: Use K3bSetup to solve this problem." Well it seems that there is no "K3bSetup" anymore! Here is what I found by Googling around a bit: http://www.bright-ideas-tx.com/phpbb/viewtopic.php?p=23&sid=731e31a28914f7476f95cce8749f3e93 "Login as 'root' and set UID for 'cdrecord' and 'cdrdao'. Linux oldtimers know how to do this from a command line. Linux newcomers may feel more comfortable doing this from within their KDE GUI. Here's how: 1. Logout and log back in as 'root'. 2. Open your Konqueror File Manager and browse to: /usr/bin/cdrecord 3. Right-click on file 'cdrecord' and select 'Properties'. 4. Select the 'Permissions' tab. 5. Click the 'Advanced Permissions' button. 6. Put a checkmark in the 'Set UID' checkbox in the 'User' row. 7. Click the 'Ok' button on each panel as you back out. 8. Repeat this process for the '/usr/bin/cdrdao' file. 9. Logout and log back into your regular user account. Now when you start K3b you won't get those errors and you can have fun burning CDs again. " Said Thomas of Kerrville Tx But once that was done I encountered the show stoper: I set up a straight CD to CDR copy using 2 drives and no matter what speed I choose inc 1X the copy fails. Here is the debug output: "System ----------------------- K3b Version:0.11.15cvs KDE Version: 3.3.0 QT Version: 3.3.3 cdrecord ----------------------- /usr/bin/cdrecord: Resource temporarily unavailable. Cannot get mmap for 4198400 Bytes on /dev/zero. Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdb speed=8 -dao driveropts=burnfree -eject -data /tmp/kde-pbvanca/k3b_0.iso " I sent the requested feedback. Now what can/should I do next? It seems that SUSE has modified cdrecord and is looking for user experiances. Note that debug info speaks of "/dev/zero" which baffles me. This is an ATAPI drive. Do we still need scsi emulation? PeterB
![](https://seccdn.libravatar.org/avatar/235069ec40fbac54c9d92c8a57c2a547.jpg?s=120&d=mm&r=g)
* Peter B Van Campen
cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdb speed=8 -dao driveropts=burnfree -eject -data /tmp/kde-pbvanca/k3b_0.iso "
I sent the requested feedback. Now what can/should I do next? It seems that SUSE has modified cdrecord and is looking for user experiances. Note that debug info speaks of "/dev/zero" which baffles me.
Just guessing, but the copy-from drive is ?? /dev/hda ??, meaning both drives are on the same cable. If so, try again with the drives on different cables. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
![](https://seccdn.libravatar.org/avatar/4500c2fdff620749d47e7e4637d59181.jpg?s=120&d=mm&r=g)
On Saturday 27 November 2004 5:27 pm, Patrick Shanahan wrote:
* Peter B Van Campen
[11-27-04 18:18]:
Just guessing, but the copy-from drive is ?? /dev/hda ??, meaning both drives are on the same cable. If so, try again with the drives on different cables.
Hi Pat, recorder = /dev/hdb on slave pos of 1st cable Master is main HD reader = /dev/hdd on slave pos of 2nd cable master open I have edited Grub to do ide=scsi for hdb I'll post when I know something. PeterB
![](https://seccdn.libravatar.org/avatar/664f9ff1ca74482f957907648e78172b.jpg?s=120&d=mm&r=g)
On Sat November 27 2004 6:27 pm, Patrick Shanahan wrote:
* Peter B Van Campen
[11-27-04 18:18]: cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdb speed=8 -dao driveropts=burnfree -eject -data /tmp/kde-pbvanca/k3b_0.iso "
I sent the requested feedback. Now what can/should I do next? It seems that SUSE has modified cdrecord and is looking for user experiances. Note that debug info speaks of "/dev/zero" which baffles me.
Just guessing, but the copy-from drive is ?? /dev/hda ??, meaning both drives are on the same cable. If so, try again with the drives on different cables.
K3b was working as long as cdrecord etc., was set so that I was the owner. If set so root is the owner, even with UID set, it can't find the drive. XCDRoast won't run no matter how it's setup. It SHOULD be a matter of rocket science to get burners to work.........we've been complaining about this for I don't know how many versions. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
![](https://seccdn.libravatar.org/avatar/41ed85ec60b719fa1654d12375dd9bd6.jpg?s=120&d=mm&r=g)
On Sat, 2004-11-27 at 21:13, Fred A. Miller wrote:
On Sat November 27 2004 6:27 pm, Patrick Shanahan wrote:
K3b was working as long as cdrecord etc., was set so that I was the owner. If set so root is the owner, even with UID set, it can't find the drive. XCDRoast won't run no matter how it's setup. It SHOULD be a matter of rocket science to get burners to work.........we've been complaining about this for I don't know how many versions.
One thing I have done for a long time is create an icon on the desktop for k3b (hint - go to the menu entry, right click and hold and drag to the desktop), go into the properties and change the the "run as" to root. Now when I launch k3b it will ask for the root password and I never have a problem burning CD's/DVD's. -- Ken Schneider UNIX since 1989 SuSE since 1998 * Only reply to the list please*
![](https://seccdn.libravatar.org/avatar/664f9ff1ca74482f957907648e78172b.jpg?s=120&d=mm&r=g)
On Sun November 28 2004 7:13 am, Ken Schneider wrote:
On Sat, 2004-11-27 at 21:13, Fred A. Miller wrote:
On Sat November 27 2004 6:27 pm, Patrick Shanahan wrote:
K3b was working as long as cdrecord etc., was set so that I was the owner. If set so root is the owner, even with UID set, it can't find the drive. XCDRoast won't run no matter how it's setup. It SHOULD be a matter of rocket science to get burners to work.........we've been complaining about this for I don't know how many versions.
Now, it's ALL "messed up." K3b won't see the CD burner as user or root, but XCDRoast is working ONLY as root, so at least I can burn discs.
One thing I have done for a long time is create an icon on the desktop for k3b (hint - go to the menu entry, right click and hold and drag to the desktop), go into the properties and change the the "run as" to root. Now when I launch k3b it will ask for the root password and I never have a problem burning CD's/DVD's.
Thanks......simple fix!! Now, XCDRoast runs the same way.....not what I want, but it works till someone FINALLY gets "with the program" and eliminates the permissions problems that have plagued us for a very long time! Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
![](https://seccdn.libravatar.org/avatar/4500c2fdff620749d47e7e4637d59181.jpg?s=120&d=mm&r=g)
On Sunday 28 November 2004 10:10 am, Fred A. Miller wrote:
On Sun November 28 2004 7:13 am, Ken Schneider wrote:
On Sat, 2004-11-27 at 21:13, Fred A. Miller wrote:
On Sat November 27 2004 6:27 pm, Patrick Shanahan wrote:
K3b was working as long as cdrecord etc., was set so that I was the owner. If set so root is the owner, even with UID set, it
***************** clip *************** Solved!! Drag an instance of K3b to the desktop and using its 'properties' dialog to set 'run as...' to root has fixed the problem as I experience it. But Fred is right, we need to do a lot better about managing this vague "Permissions" scheme. If only it was clearly defined and documented how SUSE has setup up who, what and where they have put permission restrictions. PeterB
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
Peter B Van Campen wrote:
Solved!! Drag an instance of K3b to the desktop and using its 'properties' dialog to set 'run as...' to root has fixed the problem as I experience it. But Fred is right, we need to do a lot better about managing this vague "Permissions" scheme. If only it was clearly defined and documented how SUSE has setup up who, what and where they have put permission restrictions.
Another method, is to create a directory, which is configured in sudoers. Then place symlinks for all "root" apps, that you wish to run as user in it. Adjust the menu items accordingly.
participants (5)
-
Fred A. Miller
-
James Knott
-
Ken Schneider
-
Patrick Shanahan
-
Peter B Van Campen