Gnome-sound-recorder deadlocks if capture source is toggled off

Bug #69960 reported by Vincenzo Ciancia
2
Affects Status Importance Assigned to Milestone
GNOME media utilities
Fix Released
Medium
gnome-media (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-media

It took time to figure out what was happening here: gnome-sound-recorder, usually after a first recording, mutes the capture input on my snd-hda-intel soundcard. I didn't notice it at first, however this cause the program to deadlock if one tries to record, and you have to kill the app. However, if you unmute the capture input using a mixer program, gnome-sound-recorder "unlocks" and starts recording. Don't know if this is "almost" normal behavior but something mus be broken. I don't understand why, but sometimes it will mute the capture input by itself on first startup, resulting in the program to appear "just broken", while it is not, unmuting the audio in fact results in correct recording. This may be related to my soundcard, if you need more info just ask. Backtrace is as follows:

Thread 4 (Thread -1269314656 (LWP 6096)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb736c816 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7eb4b38 in gst_system_clock_obtain ()
   from /usr/lib/libgstreamer-0.10.so.0
#3 0xb73d438f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#4 0xb7369504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb72fd51e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread -1286980704 (LWP 6112)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb736c816 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7eb4b38 in gst_system_clock_obtain ()
   from /usr/lib/libgstreamer-0.10.so.0
#3 0xb73d438f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#4 0xb7369504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb72fd51e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1278588000 (LWP 6115)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb72f3803 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb6f81cb8 in snd_pcm_wait_nocheck () from /usr/lib/libasound.so.2
#3 0xb6f81e99 in snd_pcm_wait () from /usr/lib/libasound.so.2
#4 0xb6f81fbb in snd_pcm_read_areas () from /usr/lib/libasound.so.2
#5 0xb6f8db18 in snd_pcm_mmap_readi () from /usr/lib/libasound.so.2
#6 0xb6f7c623 in snd_pcm_readi () from /usr/lib/libasound.so.2
#7 0xb45d0e4e in ?? () from /usr/lib/gstreamer-0.10/libgstalsa.so
#8 0x084536a8 in ?? ()
#9 0x0847be18 in ?? ()
#10 0x000001d6 in ?? ()
#11 0xb458b586 in gst_ring_buffer_prepare_read ()
   from /usr/lib/libgstaudio-0.10.so.0
#12 0xb4585849 in gst_audio_src_get_type () from /usr/lib/libgstaudio-0.10.so.0
#13 0xb73d438f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#14 0xb7369504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#15 0xb72fd51e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1226312016 (LWP 6092)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb736a6c8 in pthread_join () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb741ea96 in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0xb3ca4ba0 in ?? ()
#4 0xbff0ddf0 in ?? ()
#5 0x08360584 in ?? ()
#6 0xb7ef11d8 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#7 0x08360580 in ?? ()
#8 0x08389000 in ?? ()
#9 0xbff0ddf8 in ?? ()
#10 0xb741e8a8 in ?? () from /usr/lib/libgthread-2.0.so.0
#11 0xb3ca4ba0 in ?? ()
#12 0x00000000 in ?? ()
#0 0xffffe410 in __kernel_vsyscall ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? Could you get a backtrace with gstreamer0.10-plugins-base-dbg libglib2.0-0-dbg libgstreamer0.10-0-dbg installed?

Changed in gnome-media:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I am using ubuntu edgy, attaching required information.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Marking unconfirmed, somebody having that problem should forward it upstream, we have thousand of bugs open and very few people working on them at the moment and it's not likely anybody not getting that bug will spend time on it for the moment

Changed in gnome-media:
importance: Undecided → Low
status: Needs Info → Unconfirmed
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

In feisty, if one tries to close the window while the program is blocked, it unblocks and says something like "unable to determine stream type". I guess this is because it does not get data, but I do not understand why. By the way in feisty it has stopped to mute capture by itself, but the deadlock remains. Will take care of forwarding to gnome bug tracker.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for forwarding that upstream

Changed in gnome-media:
status: Unconfirmed → Confirmed
Changed in gnome-media:
status: Unknown → Unconfirmed
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

In gutsy, capture source is unmuted automatically, moreover, if you set its volume to 0, gnome-sound-recorder correctly records silence instead of deadlocking.

Changed in gnome-media:
status: Confirmed → Fix Released
Changed in gnome-media:
status: New → Fix Released
Changed in gnome-media:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.