Bug 1309489 - xfburn chokes on audio formats
xfburn chokes on audio formats
Product: Fedora
Classification: Fedora
Component: xfburn (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christoph Wickert
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-17 19:03 EST by Richard Jasmin
Modified: 2016-07-19 14:43 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:43:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
image of choke (634.25 KB, image/png)
2016-02-17 19:03 EST, Richard Jasmin
no flags Details

  None (edit)
Description Richard Jasmin 2016-02-17 19:03:48 EST
Created attachment 1128060 [details]
image of choke

Description of problem:
xfburn chokes on non-free audio formats when attempting to burn a audio cd

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

How reproducible:

Steps to Reproduce:
2.audio cd(new)
3.drop mp3 on it

Actual results:

Expected results:
should not choke or hang app, if we want to force a 'free' build, then offer non-free build also or allow for non-free via plugin support. most people have some mp3 lying around.

Additional info:
see attachment
Comment 1 Fedora End Of Life 2016-07-19 14:43:57 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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