GNOME Bugzilla – Bug 89130
Unable to record for more than one second
Last modified: 2004-12-22 21:47:04 UTC
Using the sound recorder, pressing record only records for around one second then stops itself. To Reproduce: 1) Choose applications menu -> click sound and video option. 2) Click sound recorder. 3) Click the record button. Result: Recording begins, then stops after around one second.
What defaults and options do you have set in your preferences menus? I can't test it ATM, but in the past this has worked just fine for me.
I am also seeing this problem both in Solaris and Linux, when I do pkill esd and then start sound recorder, it works fine. Can you please conform this. Luis: If this is the case can we move this bug to esd, so that Frederic Crozat might be aware of this issue, Thanks One more thing I noted is: If we choose "Enable sound server startup" and "Sound for events" in Desktop preferences->sound then logout and login, start sound recorder and recording is fine.
I would bet that this is esd not paying attention to the fact that a client is recording, and thus doing its release-sound-device-and-go-idle routine.
Have found if 'Sound for Events' box is checked in sound preferences, the sound recorder will record normally - without logout.
As earlier mentioned, after pkill esd, recording works fine. In both the cases (that is before and after doing a pkill esd) the value of sock obtained from sock = esd_record_stream_fallback (format, rate, host, name); in /grecord/grec.c is 17. But the value of length got from while ((length = read(sock, buf, ESD_BUF_SIZE)) > 0) is 0 before pkill esd and thats the reason why recording stops immediately It is 4096 after pkill esd and hence recording works fine.
Reassigning to ESound pending verification....
Another problem noted while esd is running is that gnome-sound-recorder will not play any wav files successfully on Solaris sparc. (Tested nightly build 10th August). The application appears to play the file but no sound is heard. Appears to be bug 86134 back again.
*** This bug has been marked as a duplicate of 90719 ***