Bug 358155 – crash in Ekiga Softphone:

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 358155 - crash in Ekiga Softphone:


Summary:	crash in Ekiga Softphone:


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	357898 358201 358219 358265 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-28 16:55 UTC by etelerro
Modified:	2006-10-25 14:57 UTC

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

Description etelerro 2006-09-28 16:55:01 UTC

Version: 2.0.3

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 90734592 vsize: 0 resident: 90734592 share: 0 rss: 25743360 rss_rlim: 0
CPU usage: start_time: 1159462074 rtime: 0 utime: 170 stime: 0 cutime:151 cstime: 0 timeout: 19 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 -1247107408 (LWP 6227)]
[New Thread -1283109984 (LWP 6245)]
[New Thread -1282843744 (LWP 6244)]
[New Thread -1282577504 (LWP 6242)]
[New Thread -1274184800 (LWP 6240)]
[New Thread -1249031264 (LWP 6233)]
[New Thread -1248765024 (LWP 6232)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73482

Thread 1 (Thread -1247107408 (LWP 6227))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gdk_x11_display_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#5 gtk_text_buffer_insert_plain
#6 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#7 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#8 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#9 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 PList<PString>::~PList
#15 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#16 ??
#0 __kernel_vsyscall

Comment 1 Snark 2006-09-28 18:07:48 UTC

What where you doing when it crashed ?

Comment 2 Snark 2006-09-29 12:34:22 UTC

*** Bug 358201 has been marked as a duplicate of this bug. ***

Comment 3 Snark 2006-09-29 12:34:32 UTC

*** Bug 358219 has been marked as a duplicate of this bug. ***

Comment 4 Snark 2006-09-29 12:34:38 UTC

*** Bug 357898 has been marked as a duplicate of this bug. ***

Comment 5 Snark 2006-09-29 12:34:51 UTC

*** Bug 358265 has been marked as a duplicate of this bug. ***

Comment 6 Snark 2006-09-29 12:35:43 UTC

We're suspecting an edgy-specific problem ; perhaps a problem with gtk+2.10...

I have closed quite a few bug reports as duplicate : they haven't more information than this one anyway.

Comment 7 André Klapper 2006-10-25 14:57:04 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for, and if this is still reproducible (no duplicates for 3 weeks now; i guess this happened due to the broken gtk+-2.10.4).
Thanks!