Bug 171400 - Cannot burn since Fedora Upgrade
Summary: Cannot burn since Fedora Upgrade
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cdrtools
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-21 15:41 UTC by Benoit Charbonneau
Modified: 2008-03-09 04:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-09 04:06:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Benoit Charbonneau 2005-10-21 15:41:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:
I can write a CD when root but it does not work when I am a regular user.  I'm using XCDRoast version 0.98alpha15-1, cdrecord version 2.01.1-9.0.FC4.1 and kernel  2.6.13-1.1526_FC4smp and I have activated the non-root mode.

My drive is a LG DVD+RW ( model DVDRAM GSA-4163B Rev. A102 )

When I click on the "Master and write on the fly" button and I get the following error message from cdrecord ( see attachement for the full error message ):

cdrecord: Cannot allocate memory. Cannot get SCSI I/O buffer.



Version-Release number of selected component (if applicable):
cdrecord-2.01.1-9.0.FC4.1

How reproducible:
Always

Steps to Reproduce:
1. Open xcdroast
2. Click on "Create CD/DVD"
3. Click on "Master track"
4. add files
5. Click on "create session/image"
6. Click on "Master and write on the fly"
  

Actual Results:  Error writing track ( see attachement for the complete error message )

Expected Results:  When I am doing this log in as root, everything is working fine the track burned on the cd.

Additional info:

Comment 1 Harald Hoyer 2006-04-19 11:38:12 UTC
which attachemen?

Comment 3 petrosyan 2008-03-09 04:06:28 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.


Note You need to log in before you can comment on or make changes to this bug.