Filippo Giunchedi wrote: > On Thu, Jan 15, 2009 at 02:49:46PM +0100, Josselin Mouette wrote: >> Le jeudi 15 janvier 2009 � 13:57 +0100, Jelle de Jong a �crit : >>> Program received signal SIGSEGV, Segmentation fault. >>> [Switching to Thread 0xb401eb90 (LWP 4217)] >>> 0xb726bc1c in memcpy () from /lib/i686/cmov/libc.so.6 >>> (gdb) backtrace full >>> #0 0xb726bc1c in memcpy () from /lib/i686/cmov/libc.so.6 >>> No symbol table info available. >>> #1 0xb3816a16 in bluetooth_a2dp_write () from >>> /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so >>> No locals. >>> #2 0xb6282bc1 in ?? () from /usr/lib/libasound.so.2 >>> No symbol table info available. >> Thanks, looks like a bug in the ALSA bluetooth module. > > can you reproduce with bluez 4 in unstable? > > filippo
Hi Filippo, The problem is still there but this is the real issue; The bluez developers found a critical bug in the alsa api system that makes audio systems crash in some situation on i368 and on powerpc or arm it will not even work. So the bluez developers decided together with the alsa developpers to force a more stricture api use to fix the crashes. The result; correctly totem-xine does not even work anymore with bluez and alsa. If you reverse the patch on the bluez code that allow the incorrect alsa use then the behavior described in the original bug report will occur. So the solution is to fix the totem-xine alsa implementation so the new bluez code will work again and the above bug will be fixed. see: http://git.kernel.org/?p=bluetooth/bluez.git;a=commitdiff;h=593bd41ed861d80f498fa8cfe0cea06e0c11f442 http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014392.html git revert 593bd41ed861d80f498fa8cfe0cea06e0c11f442 You can ask on #bluez for more information I really hope some developer can fix the alsa implementation in totem-xine so I and all other bluez users can use totem-xine again without continuing crashes. Thanks in advance, Best regards, Jelle de Jong -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
