Bug 361218 – crash in Ekiga Softphone: Calling the ekiga echo s...

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 361218 - crash in Ekiga Softphone: Calling the ekiga echo s...


Summary:	crash in Ekiga Softphone: Calling the ekiga echo s...


Status:	RESOLVED DUPLICATE of bug 333311

Product:	ekiga
Classification:	Applications
Component:	general
Version:	2.0.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Ekiga maintainers
QA Contact:	Ekiga maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-10 18:24 UTC by johan
Modified:	2007-01-01 18:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description johan 2006-10-10 18:24:24 UTC

Version: 2.0.3

What were you doing when the application crashed?
Calling the ekiga echo service, using OSS as sound system. The crash occured when i tried to hang up.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 101466112 vsize: 0 resident: 101466112 share: 0 rss: 28614656 rss_rlim: 0
CPU usage: start_time: 1160504548 rtime: 0 utime: 3464 stime: 0 cutime:2428 cstime: 0 timeout: 1036 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1247099216 (LWP 15841)]
[New Thread -1302525024 (LWP 16027)]
[New Thread -1302258784 (LWP 15968)]
[New Thread -1301242976 (LWP 15967)]
[New Thread -1291908192 (LWP 15957)]
[New Thread -1291641952 (LWP 15956)]
[New Thread -1291375712 (LWP 15955)]
[New Thread -1290802272 (LWP 15904)]
[New Thread -1282409568 (LWP 15897)]
[New Thread -1249309792 (LWP 15844)]
[New Thread -1249043552 (LWP 15843)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75657

Thread 1 (Thread -1247099216 (LWP 15841))

#0 __kernel_vsyscall
#1 poll
from /lib/tls/i686/cmov/libc.so.6
#2 XProcessInternalConnection
from /usr/lib/libX11.so.6
#3 _XRead
from /usr/lib/libX11.so.6
#4 _XReply
from /usr/lib/libX11.so.6
#5 XSync
from /usr/lib/libX11.so.6
#6 gdk_flush
from /usr/lib/libgdk-x11-2.0.so.0
#7 gdk_image_new
from /usr/lib/libgdk-x11-2.0.so.0
#8 _gdk_image_get_scratch
from /usr/lib/libgdk-x11-2.0.so.0
#9 gdk_rgb_xpixel_from_rgb
from /usr/lib/libgdk-x11-2.0.so.0
#10 gdk_drawable_set_data
from /usr/lib/libgdk-x11-2.0.so.0
#11 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#12 gdk_draw_pixbuf
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_pixbuf_render_pixmap_and_mask
from /usr/lib/libgdk-x11-2.0.so.0
#14 gdk_draw_pixbuf
from /usr/lib/libgdk-x11-2.0.so.0
#15 gdk_window_get_window_type
from /usr/lib/libgdk-x11-2.0.so.0
#16 gdk_draw_pixbuf
from /usr/lib/libgdk-x11-2.0.so.0
#17 gtk_image_new_from_pixmap
from /usr/lib/libgtk-x11-2.0.so.0
#18 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_container_propagate_expose
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_container_propagate_expose
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_font_selection_new
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_frame_new
from /usr/lib/libgtk-x11-2.0.so.0
#31 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#33 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#37 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#38 gtk_container_propagate_expose
from /usr/lib/libgtk-x11-2.0.so.0
#39 gtk_container_propagate_expose
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_event_box_new
from /usr/lib/libgtk-x11-2.0.so.0
#44 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#45 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#46 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#47 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#49 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#50 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#51 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#52 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#53 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#54 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#55 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#56 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#57 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#58 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#59 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#60 PList<PString>::~PList
#61 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#62 ??
#0 __kernel_vsyscall

Comment 1 Snark 2006-10-10 18:48:35 UTC

Looks like a crash in X :-/

Comment 2 Damien Sandras 2006-10-10 20:30:43 UTC

I would think of a bug in :
PStandardColourConverter::MJPEGtoYUV420P

And it looks very much like :
http://bugzilla.gnome.org/show_bug.cgi?id=361218

Comment 3 Damien Sandras 2007-01-01 18:42:49 UTC

It is most probably a DUP of #333311 that Luc fixed. If it happens again when we release 2.0.4, please open a new bug report.

Thanks.

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