Bug 97

Summary: gnome-sound-recorder freezes on close
Product: Mageia Reporter: Jan Merta <lunruj>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: mageia, marja11
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: gnome-media CVE:
Status comment:
Attachments: amixer output
amixer -c0 output
ck-list-sessions output
getfacl /dev/snd/pcm* output
pacmd list output

Description Jan Merta 2011-02-18 16:23:38 CET
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b10) Gecko/20110206 Firefox/4.0b10
Build Identifier: 

Description of problem:
The gnome-sound-recorder don't record and freezes on close or new record after you try to record.

Version-Release number of selected component (if applicable):
gnome-sound-recorder 2.32.0

Steps to Reproduce:
1. Run gnome-sound-recorder
2. Start recording: the stop button stays disabled, play button is enabled, but recording doesn't seems to be running.
3. If you press record or close and choose continue without saving or close without saving, the application freezes. If you choose to save, it freezes after you choose file to save and confirm it. If you choose play, an error message "no data in stream" appears.

Version: Mageia alpha 1, this error also occurs in Mandriva Linux (more versions, I'm not sure which ones). I tested current PCLinuxOS and it didn't freeze (and the application was recording, but no sound on play).

Note: My soundcard seems to not working correctly with current Linux distributions.

Reproducible: 

Steps to Reproduce:
Comment 1 Ahmad Samir 2011-02-22 19:21:45 CET
Is pulseaudio enabled (it's enabled by default)?

Can you try running it from terminal and post any useful output here?

Keywords: (none) => NEEDINFO
Source RPM: (none) => gnome-media

Comment 2 Jan Merta 2011-02-26 22:58:53 CET
PA was enabled. It's the same with PA disabled. When I run it from console, i got:

[lunruj@localhost ~]$ gnome-sound-recorder
/tmp/gsr-record-Untitled-3152.XBDQRV
(gnome-sound-recorder:3152): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
Killed

[lunruj@localhost ~]$ gnome-sound-recorder
/tmp/gsr-record-Untitled-3210.URFNRVERROR: Stream contains no data.
DEBUG MESSAGE: gsttypefindelement.c(948): gst_type_find_element_activate (): /GstPlayBin:playbin/GstDecodeBin:decodebin1/GstTypeFindElement:typefind:
Can't typefind empty stream

First one was when i chose to save record, the secong one was when I tried to play the record, but then there was no output when I chose record again and it froze.

Note: I don't know why, but it started to work normally one day. I reinstalled Mageia to find if some update didn't fixed it. After reinstallation the bug is here again and after installing updates it still freezes.
Comment 3 Ahmad Samir 2011-03-03 20:51:28 CET
Try disabling pulseaudio, from draksound (as root);after you log out => log in make sure pulseaudio is dead by running this in terminal 'killall pulseaudio'. Then try again.

(This is just to see if the problem is related to pulseaudio).

CC: (none) => mageia

Comment 4 Jan Merta 2011-06-18 22:01:23 CEST
The bug is still valid in Mageia 1. I tried to killed pulseaudio a got the same result. It seems to be related with microphone, it appears if microphone doesn't work. But I am not sure about it and I can't test it since I can't make my mic work in Mageia.
Comment 5 Ahmad Samir 2011-06-18 22:43:59 CEST
By "killed" you mean you disabled it via draksound?

Please post the output of 'amixer', so that we can see how the channels are configured on your setup.
Comment 6 Jan Merta 2011-06-19 10:21:07 CEST
Created attachment 584 [details]
amixer output
Comment 7 Jan Merta 2011-06-19 10:23:51 CEST
I disabled pulseaudio in draksound, logged out, logged in and run 'killall pulseaudio'.
Colin Guthrie 2011-06-19 18:05:01 CEST

Attachment 584 mime type: application/octet-stream => text/plain

Comment 8 Colin Guthrie 2011-06-19 18:10:02 CEST
Wow, that's the worlds simplest amixer output :D It looks suspiciously like PA is still enabled (as it causes this nice and simple interface to be presented) rather than your real card.

I suspect some confusion/manual tweaking in your alsa setup.

I can help you make PA work, but I will need you to reenable PA in draksound and then reboot.

When done please do the following:

 1. Attach output from: amixer -c0 (please pick text/plain as the type of file when you attach here).
 2. Attach output from: cat $HOME/.asoundrc
 3. Attach output from: ck-list-sessions
 4. Attach output from: getfacl /dev/snd/pcm*
 5. Run "parec >/dev/null" on the command line and leave it there then:
 5a: Attach output from: pacmd list
 5b: Attach output from: sudo fuser /dev/snd/pcm*


Many thanks :)
Comment 9 Jan Merta 2011-06-19 20:13:05 CEST
That would be because PA was running. I just checked what happen when I disable PA and then enabled it again. ;-) When I disable it via draksound, the output is different.

2) gives 'cat: /home/lunruj/.asoundrc: AdresáŠnebo soubor neexistuje' (directory or file doesn't exist)
5b) gives '/dev/snd/pcmC0D0c:    3997m' (respectively running as root gives this output, sudo doesn't work)
Comment 10 Jan Merta 2011-06-19 20:13:53 CEST
Created attachment 589 [details]
amixer -c0 output
Comment 11 Jan Merta 2011-06-19 20:14:28 CEST
Created attachment 590 [details]
ck-list-sessions output
Comment 12 Jan Merta 2011-06-19 20:15:33 CEST
Created attachment 591 [details]
getfacl /dev/snd/pcm* output
Comment 13 Jan Merta 2011-06-19 20:16:25 CEST
Created attachment 592 [details]
pacmd list output
Comment 14 Colin Guthrie 2011-06-20 10:25:43 CEST
Oh, I meant fuser -v, but it doesn't really matter as I'm sure that single PID was pulseaudio anyway. Otherwise, all the outputs are as I'd expect so should be fine.

So the recording appears to be working fine, it's running and connected to the correct source. You are recording from the external mic at the moment rather than the built in one. Is that intentional? 

If not, then please select Microphone 1 from the ports list on the Input Devices tab of pavucontrol (or in gnome-volume-control).

This should allow the internal mic to be used instead.

Not sure if this will help the gnome-sound-recorder problem tho'. If you try that then attach the ouput of pacmd list again when gnome-sound-recorder is running, that might help.

Cheers
Comment 15 Marja Van Waes 2011-09-24 19:46:09 CEST
@ Jan

You never replied to comment 14 from Colin. Therefore I'm closing this bug. Feel free, however, to reopen it and upload the output of pamcd list again, as asked by Colin.

If you encounter the same bug in Mageia 1, that should be filed as a seperate bug (preferably with a link to this one)

Status: NEW => RESOLVED
CC: (none) => m.van.waes
Resolution: (none) => OLD