Red Hat Bugzilla – Bug 130617
gnome-sound-record Save and Save As commands fail silently
Last modified: 2007-11-30 17:10:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
gnome-sound-recorder is able to record, and the temporary file
containing the recording is visible in /tmp (e.g.,
/tmp/gsr-record-Untitled-12893.5EQjWV), but the Save and Save As
commands don't do anything. The file the user selects via the file
chooser is not created, and gnome-sound-recorder still calls the
This was reported by Phil Barnes in a comment on bug #100774, but is
almost certainly not related to the main bug reported there, thus I
have entered this as a separate bug. Please do not close this as a
duplicate of 100774 without studying it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open gnome-sound recorder
2. Click the "record" button.
3. Wait a bit
4. Click the "stop" button.
5. Click the "save as" button.
6. Select a filename to save using the file chooser.
Actual Results: No file created. gnome-sound-record still calls the
Expected Results: File user selected should be created.
Same here, after installing gstreamer-0.8.5-1 from rawhide.
The machine on which I observed this behavior had a fairly plain
install of FC2. It did have gstreamer-0.8.3-2 installed, but nothing
In case it matters, my system is a dual Athlon 1900+ (Asus A7M266-D)
with 1.25GB of RAM and an Audigy Platinum sound card, running
*** This bug has been marked as a duplicate of 100774 ***
Colin, thanks ever so much for carefully reading my comments then
deciding to close 130617 as a duplicate anyhow. :-(
The problem Phil Barnes and I experienced is NOT the crash described
in 100774. In our case, the recording works fine, but is not saved.
No crash occurs.
Look, there are a ton of varied bugs against gnome-volume-control,
many of which overlap. There are too many for me to track
individually. I am going to make a decision soon about whether to
simply remove it entirely for FC3.
If we decide to ship it, we can reopen this one and start examining
and forwarding issues upstream individually.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.