Bug 684066 - Unable to locate gnome-audio-profile-edit.ui
Summary: Unable to locate gnome-audio-profile-edit.ui
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: libgnome-media-profiles
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Yanko Kaneti
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 01:34 UTC by Brian Pepple
Modified: 2011-12-21 15:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-21 15:48:50 UTC
Type: ---


Attachments (Terms of Use)

Description Brian Pepple 2011-03-11 01:34:01 UTC
Description of problem: When attempting to edit a gstreamer pipeline, libgnome-media-profiles is unable to locate the gnome-audio-profile-edit.ui gtkbuild file


Version-Release number of selected component (if applicable): libgnome-media-profiles-2.91.2-15.fc15.i686


How reproducible: Always


Steps to Reproduce:
1. Run 'gnome-audio-profiles-properties'
2. Select an audio profile, and hit the edit button.
  
Actual results: An error dialog is shown saying that the gnome-audio-profile-edit.ui file is missing.


Expected results: A dialog is shown that would allow the user to edit the gstreamer profile.


Additional info: The gktbuilder file is located at /usr/share/libgnome-media-profiles/gnome-audio-profile-edit.ui, so just need to verify where the src code is looking for gtkbuilder file. If I've got some free time, I'll look at fixing this since it should be fairly simple.

Comment 1 Yanko Kaneti 2011-03-11 02:30:33 UTC
This was fixed upstream a while back. I was/am expecting a new release.

Comment 2 Brian Pepple 2011-03-12 18:08:47 UTC
I'll see if I can track hadess down and see what the eta is on a new upstream release. If it's not too soon, it's probably worthwhile to backport that one-line patch, since it's an easy fix.

Comment 3 Yanko Kaneti 2011-12-21 15:48:50 UTC
This was fixed upstream before 3.0.0  afair. Closing


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