Bug 132404

Summary: cdrecord reports out of memory for standard users
Product: [Fedora] Fedora Reporter: Paul F. Johnson <paul>
Component: cdrtoolsAssignee: Harald Hoyer <harald>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-13 12:23:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of running cdrecord from the command line none

Description Paul F. Johnson 2004-09-12 19:52:32 UTC 
Description of problem:
If I run k3b as a normal user, all the drives are identified, but when
I come to burn, I get an error that there was not sufficient memory.
If I run k3b as su, the recording works fine

Version-Release number of selected component (if applicable):
cdrecord-2.1a38-dvd

How reproducible:
Always

Steps to Reproduce:
1. Start k3b
2. Select create data CD and drag some data for burning
3. Click on burn to burn the CD
  
Actual results:
cdrecord reports 

TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.8'.
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
/usr/bin/cdrecord: Cannot allocate memory. Cannot get SCSI I/O 

Expected results:
CD should record

Additional info:
Comment 1 Harald Hoyer 2004-09-13 09:23:11 UTC 
could you please try to burn manually as a user?

$ cdrecord dev=/dev/hdd debug=1000 myiso.iso
Comment 2 Paul F. Johnson 2004-09-14 22:37:42 UTC 
Please see the attached file. Same problem occurs from the command line
Comment 3 Paul F. Johnson 2004-09-14 22:38:40 UTC 
Created attachment 103849 [details]
Output of running cdrecord from the command line
Comment 4 Harald Hoyer 2004-10-13 12:21:51 UTC 
is this problem still current?
Comment 5 Paul F. Johnson 2004-10-13 12:23:39 UTC 
Seems okay on FC3t3 - I think it's safe to close