GNOME Bugzilla – Bug 605444
Wrong webcam device detected and video call crashes.
Last modified: 2010-02-15 15:28:42 UTC
Created attachment 150376 [details] In GDB `t a a bt full`. Dear Empathy hackers, I tried Empathy out especially the Jingle(?) extension. The one system (A) has a webcam. Doing an audio call (Audioanruf) and clicking on the webcam button/symbol/icon to send the webcam picture closes the call window and most of the time Empathy crashes too. I tried to debug this according to [1]. Unfortunately the Debugging Console crashes sometimes with the application. Since the one system has small storage space I did not install all debugging symbols. Just those from Empathy. I hope that works, if not tell me please what symbols you need. I am using Debian Sid/unstable. $ LANG=C dpkg -l empathy* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=======================================-=======================================-============================================================================================== ii empathy 2.28.2-1 High-level library and user-interface for Telepathy ii empathy-dbg 2.28.2-1 High-level library and user-interface for Telepathy (debug symbols) ii empathy-doc 2.28.2-1 High-level library and user-interface for Telepathy (Empathy documentation) Here is the corresponding part from the debug console. […] tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) _tf_stream_try_sending_codecs: called (send_local:1 send_supported:0) tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) _tf_stream_try_sending_codecs: 96: video THEORA clock:90000 channels:0 delivery-method=inline tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) _tf_stream_try_sending_codecs: 26: video JPEG clock:90000 channels:0 tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) _tf_stream_try_sending_codecs: 97: video JPEG2000 clock:90000 channels:0 tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) fs_codecs_to_tp: adding codec THEORA [96] tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) fs_codecs_to_tp: adding codec JPEG [26] tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) fs_codecs_to_tp: adding codec JPEG2000 [97] tp-fs-FEHLERDIAGNOSE: 1,261774e+09: stream 2 0x814be30 (video) _tf_stream_try_sending_codecs: calling MediaStreamHandler::Ready empathy-NACHRICHT: 1,261774e+09: Element error: Gerät »/dev/video1« kann nicht identifiziert werden. -- v4l2_calls.c(488): gst_v4l2_open (): /GstV4l2Sink:autovideosink0-actual-sink-v4l2: system error: Datei oder Verzeichnis nicht gefunden […] (translation: • Gerät »/dev/video1« kann nicht identifiziert werden. = Device »/dev/video1« can not be identified. • Datei oder Verzeichnis nicht gefunden = File or directory not found.) After this sometimes Empathy crashes afterward on system A. I attach the GDB backtraces. I deleted – hopefully all – account information. Thanks, Paul [1] http://live.gnome.org/Empathy/Debugging
Created attachment 150377 [details] Backtrace of other crash. (In GDB `t a a bt full`.)
Paste Here the trace
+ Trace 219793
Thread 1 (Thread 0xb452b780 (LWP 2287))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Fabio, thank you for your comment. The space on the hard drive is very limited. Can you see from the incomplete backtrace and the fact that it is related to the video call, what debugging symbols I need to install i. e. from what component (GTK, telepathy, …)? Thanks!
Hi Paul. I managed to reproduce the same v4l2 error message but that didn't lead to a crash? Any chance you could try with 2.29.4 (which is packaged in experimental). I suspect that the crash is in GStreamer, so installing debug symbols for those packages could be useful.
Dear Guillaume, (In reply to comment #5) > I managed to reproduce the same v4l2 error message but that didn't lead to a > crash? Any chance you could try with 2.29.4 (which is packaged in > experimental). > > I suspect that the crash is in GStreamer, so installing debug symbols for those > packages could be useful. I think that some GStreamer plugins were not installed. Installing the debug symbols the following packages were installed too. gstreamer0.10-alsa, gstreamer0.10-esd, gstreamer0.10-sdl, gstreamer0.10-x Now I am not able to reproduce the crash anymore. Maybe there should be some checks and error out without a crash if some plugins are missing. I have not yet had time to test the version 2.29.4 in Debian experimental, but filed a bug report too [1]. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564678
Closing this bug for now as I didn't mention to reproduce the crash in master; even after uninstalling the extra gst package you mentioned in the Debian bug report. Feel free to reopen if you manage to reproduce the crash with a recent Empathy.