| Summary: | k3bsetup breaks cdrecord | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | crusaderky |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
crusaderky
2004-11-02 11:27:33 UTC
I do 'emerge cdrtools' and cdrecord works fine, both as a normal user (obviously with priority 0) and as root. I launch k3bsetup, leaving the option "use cdrecord group" unchecked, and it becomes completely impossible for normal users to burn CDs (it will still work for root), both using k3b and cdrecord: $ cdrecord -v -dao -eject speed=32 fs=32 dev=ATAPI:0,0,0 driveropts=burnfree DataCD1.iso cdrecord: Fifo size 32 too small, turning fifo off. Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling cdrecord: Warning: Running on Linux-2.6.10-rc1 cdrecord: There are unsettled issues with Linux-2.5 and newer. cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris. TOC Type: 1 = CD-ROM scsidev: 'ATAPI:0,0,0' devname: 'ATAPI' scsibus: 0 target: 0 lun: 0 Warning: Using ATA Packet interface. Warning: The related Linux kernel interface code seems to be unmaintained. Warning: There is absolutely NO DMA, operations thus are slow. Using libscg version 'schily-0.8'. Driveropts: 'burnfree' SCSI buffer size: 64512 cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer. I've got: cdrtools-2.01 cdrdao-1.1.8-r1 k3b-0.11.17 linux-2.6.10-rc1-vanilla _NO_ scsi emulation from lilo NEC DVD+/-RW 3500 on secondary master This is what I get _before_ launching k3bsetup: # ls -l /usr/bin/cdrecord -rwxr-xr-x 1 root root 341956 2 nov 20:23 /usr/bin/cdrecord And this is what I get after launching it: # ls -l /usr/bin/cdrecord -rws--x--x 1 root root 341956 2 nov 20:32 /usr/bin/cdrecord Workaround: re-merge cdrtools, so that you recover the default permissions, and don't run k3bsetup. Obviously, this way you'll get priority 0 when running as a normal user, which is bad. |
