Bug 115105 - Gnome-Sound-Recorder saves files as 0KB
Gnome-Sound-Recorder saves files as 0KB
Status: CLOSED DUPLICATE of bug 100774
Product: Red Hat Linux
Classification: Retired
Component: gnome-media (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Colin Walters
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-02-06 13:09 EST by Jared
Modified: 2007-04-18 13:02 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:01:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jared 2004-02-06 13:09:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)

Description of problem:
I am a DJ so I record on Line in (igain) to gnome sound recorder....

Problem is I can record and play back...but If I save the file as a
.wav (regardless of what kind of .wav) it says it saves but the file
is 0KB....and the files I save should be are 400MB. 

When it saves as 0KB I can no longer open it, play it back, or do
anything with it other than delete it...

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

How reproducible:

Steps to Reproduce:
1. open gnome sound recorder
2. record
3. save file as .wav (any format of .wav)

Actual Results:  file saves, but saves as 0KB. non working file.

Expected Results:  expect to see approximately a 400MB file that is a
playable .wav file.

Additional info:

also if I duplicate gnome sound recorder it crashes.
Comment 1 Colin Walters 2004-07-26 13:43:44 EDT
Hi - this looks like a duplicate of 100774.  

This bug was originally opened against RH9 - have you tried with FC2?

*** This bug has been marked as a duplicate of 100774 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:01:06 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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