After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 597597 - crash in Empathy: I was testing jabber vid...
crash in Empathy: I was testing jabber vid...
Status: RESOLVED DUPLICATE of bug 597892
Product: empathy
Classification: Core
Component: General
0.1
Other All
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-06 19:36 UTC by misc
Modified: 2009-10-14 12:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description misc 2009-10-06 19:36:36 UTC 
Version: 2.28.0.1

What were you doing when the application crashed?
I was testing jabber video capacity using 2 empathy on the local network. I was the caller, and the other pc just accepted the call.


Distribution: Mandriva Linux release 2010.0 (Cooker) for x86_64
Gnome Release: 2.28.0 2009-09-21 (Mandriva)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.1-desktop-1mnb #1 SMP Fri Sep 25 16:06:41 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 1061355520 vsize: 1061355520 resident: 51040256 share: 27930624 rss: 51040256 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254857431 rtime: 4601 utime: 3572 stime: 1029 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/empathy'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f5c7b907730 (LWP 4269)]
[New Thread 0x7f5c447dd910 (LWP 4850)]
[New Thread 0x7f5c44fde910 (LWP 4849)]
[New Thread 0x7f5c457fc910 (LWP 4848)]
[New Thread 0x7f5c54899910 (LWP 4845)]
[New Thread 0x7f5c5509a910 (LWP 4844)]
[New Thread 0x7f5c63723910 (LWP 4843)]
[New Thread 0x7f5c562e2910 (LWP 4842)]
[New Thread 0x7f5c56ae3910 (LWP 4841)]
[New Thread 0x7f5c57ceb910 (LWP 4840)]
[New Thread 0x7f5c5f681910 (LWP 4839)]
[New Thread 0x7f5c60ea8910 (LWP 4838)]
[New Thread 0x7f5c47ffd910 (LWP 4837)]
[New Thread 0x7f5c616a9910 (LWP 4835)]
[New Thread 0x7f5c620af910 (LWP 4834)]
[New Thread 0x7f5c604a4910 (LWP 4832)]
[New Thread 0x7f5c416b3910 (LWP 4831)]
[New Thread 0x7f5c42ad5910 (LWP 4830)]
[New Thread 0x7f5c572e4910 (LWP 4829)]
0x00007f5c77ace5ad in waitpid () from /lib64/libpthread.so.0

+ Trace 218108

Thread 1 (Thread 0x7f5c7b907730 (LWP 4269))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 abort
    at abort.c line 88
  • #7 IA__g_logv
    at gmessages.c line 549
  • #8 IA__g_log
    at gmessages.c line 569
  • #9 g_mutex_free_posix_impl
    at gthread-posix.c line 171
  • #10 ??
    from /usr/lib64/gstreamer-0.10/libgstcoreelements.so
  • #11 IA__g_object_unref
    at gobject.c line 2421
  • #12 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #13 gst_mini_object_unref
    from /usr/lib64/libgstreamer-0.10.so.0
  • #14 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #15 IA__g_main_context_dispatch
    at gmain.c line 1960
  • #16 g_main_context_iterate
    at gmain.c line 2591
  • #17 IA__g_main_loop_run
    at gmain.c line 2799
  • #18 IA__gtk_main
    at gtkmain.c line 1205
  • #19 main
    at empathy.c line 910 






Comment 1


Guillaume Desmottes





          2009-10-14 12:44:59 UTC
        



Seems to be a problem in gstreamer but can't tell without debug symbols. Any chance you could reproduce with more debug symbols installed and paste the output of Empathy before the crash?






Comment 2


Guillaume Desmottes





          2009-10-14 12:48:38 UTC
        



Where you using the same bugged telepathy-farsight as on bug #597892. If yes, please retry with a fixed version.






Comment 3


misc





          2009-10-14 12:58:04 UTC
        



I think I was using the non fixed version of farsight, so I will close this one as duplicate, and open a new report if there is a problem.

*** This bug has been marked as a duplicate of bug 597892 ***