Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 103277

Summary: gnome-sound-record is broken
Product: [Retired] Red Hat Raw Hide Reporter: Tim Waugh <twaugh>
Component: gnome-mediaAssignee: Havoc Pennington <hp>
Status: CLOSED RAWHIDE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-21 19:54:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 100643    

Description Tim Waugh 2003-08-28 14:05:32 UTC
Description of problem:
When trying to record a sound using gnome-sound-recorder, I get this in
.xsession-errors:

INFO (10821: 0) Initializing GStreamer Core Library version 0.6.2
INFO (10821: 0) CPU features: (c1c3fbff) MMX SSE 3DNOW MMXEXT
INFO (10821: 0) registry: loaded global_registry in 0.077873 seconds
          (/var/cache/gstreamer-0.6/registry.xml)
 
** (gnome-sound-recorder:10821): WARNING **: FIXME: guard from double entry

and the window will not update.

Version-Release number of selected component (if applicable):
gnome-media-2.3.7-1

How reproducible:
100%

Steps to Reproduce:
1. Press record.

Comment 1 Alexander Larsson 2003-09-05 14:50:31 UTC
http://bugzilla.gnome.org/show_bug.cgi?id=118077 upstream bug.


Comment 2 John Thacker 2003-10-10 14:29:03 UTC
This should be fixed with the update to gnome-media-2.4.0-1 judging by the
comments in the upstream bug.  I certainly can't reproduce it any more.  I
recommend closing the bug.