Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 107106

Summary: xcdroast version is incompatible with cdrecord
Product: [Fedora] Fedora Reporter: Bill Baldwin <bill>
Component: xcdroastAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:59:08 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:

Description Bill Baldwin 2003-10-15 03:22:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4.1) Gecko/20031009

Description of problem:
** WARNING **: Invalid cdrecord version Clone found.
        Expecting at least version 1.11a34
        Start xcdroast with the -n option to override (not recommended!)

I get this message when I attempt to start xcdroast in root mode.  cdrecord
claims to be 2.01-0.a19.1

Version-Release number of selected component (if applicable):
0.98a14-1

How reproducible:
Always

Steps to Reproduce:
1.get in terminal in root mode
2.type xcdroast
3.look at the message.

(This probably happens when called from the menu, but I cannot see it.)    

Actual Results:  ** WARNING **: Invalid cdrecord version Clone found.
        Expecting at least version 1.11a34
        Start xcdroast with the -n option to override (not recommended!)

followed by a prompt

Expected Results:  xcdroast should come up.

Additional info:

I loaded "everything" on my machine.

It appears to work if the -n option is entered.

Comment 1 Harald Hoyer 2003-10-15 06:53:09 UTC

*** This bug has been marked as a duplicate of 106716 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:59:08 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.