Bug 133672 - gnome-sound-recorder package missing gstreamer prereqs
Summary: gnome-sound-recorder package missing gstreamer prereqs
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-media   
(Show other bugs)
Version: 2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-26 01:11 UTC by Doug Ransom
Modified: 2013-03-13 04:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-29 14:38:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Doug Ransom 2004-09-26 01:11:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
gnome-sound-recorder was installed (either with distro fc2 or via
apt). Synaptics shows 2.6.0-1 installed. 

It crashes on startup with the following output:
oug@localhost etc]$ gnome-sound-recorder
GStreamer-ERROR **: No default scheduler name - do you have a registry ?
[doug@localhost etc]$ gnome-sound-recorder

Intalling every gstreamer pacage via apt/synpatic corrects the problem.

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

How reproducible:

Steps to Reproduce:
1. install gnonme-soune-recorder on a fresh distro
2.  run it.

Additional info:

Comment 1 Colin Walters 2004-09-27 18:37:51 UTC
I can't reproduce this problem.  What gstreamer packages did you
install that you didn't already have installed?

Comment 2 John Thacker 2006-04-29 14:38:25 UTC
From the changelog for gnome-media:

* Tue May 17 2005 John (J5) Palmieri <johnp@redhat.com> 2.10.2-2
- remove gnome-sound-recorder because it hasn't worked for some time

FC2 is the responsibility of Fedora Legacy, and this does not seem
like a security bug.  Since gnome-sound-recorder was removed, it
does not seem like this is going to be fixed.

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