Bug 495988 - k3b gives incorrect warning about cdrdao, cdrdao no longer reports version
Summary: k3b gives incorrect warning about cdrdao, cdrdao no longer reports version
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: cdrdao
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-15 20:39 UTC by Bruno Wolff III
Modified: 2014-01-13 00:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-19 19:17:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2009-04-15 20:39:34 UTC
Description of problem:
When starting k3b I get the following warning in a pop up:
Unable to find cdrdao executable
K3b uses cdrdao to actually write CDs.
Solution: Install the cdrdao package.

However cdrdao-1.2.3-0.rc2.1.i586 is installed and burning works fine despite the warning.

Version-Release number of selected component (if applicable):
k3b-1.0.5-8.fc11.i586

How reproducible:
100%

Steps to Reproduce:
1. Start k3b in gnome
2.
3.
  
Actual results:
Incorrect pop up warning

Expected results:
No warning

Additional info:

Comment 1 Roman Rakus 2009-04-16 09:30:08 UTC
This will be problem in cdrdao - now it doesn't tell version and k3b is confused.

Comment 2 Rex Dieter 2009-04-16 13:00:29 UTC
ok, adjusting summary, component.

Comment 3 Denis Leroy 2009-04-16 13:52:05 UTC
I've reverted the version printing behavior and checked it in upstream. F-11 is building now.

Roman, can you take care of getting rel-eng to tag it for F-11 ?

Comment 4 Roman Rakus 2009-04-16 14:34:07 UTC
Hmmm... on thing is changed output of `cdrdao' and second is that k3b should check version with running `cdrdao version'. But it is working this way, so why to change it?
And yes, I will contact rel-eng...

Comment 5 Bruno Wolff III 2009-04-19 19:17:41 UTC
I am not seeing this in today's rawhide.


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