RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 842906 - brasero video disc burning not supported, shows ugly error
Summary: brasero video disc burning not supported, shows ugly error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: brasero
Version: 7.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: 7.1
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-24 21:36 UTC by Mark Gordon
Modified: 2015-09-08 20:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-08 20:14:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 719991 0 None None None Never

Description Mark Gordon 2012-07-24 21:36:03 UTC 
Description of problem:

If you attempt to burn a video disc project in brasero, you get an obscure error message.

Version-Release number of selected component (if applicable):
3.4.1-1.el.7

How reproducible:
100%

Steps to Reproduce:
1. Run brasero
2. Click the "Video Project / Create a video DVD or an SVCD" button.
3. Click the "+" button
4. In the file browser, select a video file.  I've been using /usr/share/gnome/help/evince/C/figures/synctex_screencast.ogv, but I get similar results with other files.
5. Project -> Burn...
  
Actual results:
"All required applications and libraries are not installed.

Please install the following manually and try again:
mplex (GStreamer plugin)
ffenc_mp2 (GStreamer plugin)
ffenc_ac3 (GStreamer plugin)
ffenc_mpeg2video (GStreamer plugin)
vcdimager (application)."

Expected results:
Good question; I was quite skeptical about whether it would work.  Perhaps the real question is how exactly it could be failing better.  The error message was probably written for end-users with the technical expertise to find "bad" apps and GStreamer plugins but I'm not sure it's a great idea for us to offer our users that advice, at the very least because it's not terribly user-friendly advice.  Might it be better to present a different error message? Dim and disable the Burn... option iff it's not supported?  Are there third-party vendors from whom users could buy codecs, in which case we could direct them to those vendors? 

Additional info:
Google suggests that Ubuntu users had similar problems.
Comment 8 Jiri Koten 2015-05-13 12:44:32 UTC 
Still reproducible in brasero-3.12.0-1.el7, it asks for manual install instead of packagekit.
Comment 9 Matthias Clasen 2015-09-08 20:14:20 UTC 
It seems unlikely that we'll get a fix for this, unless it gets fixed upstream first.
Note You need to log in before you can comment on or make changes to this bug.