ekiga crashed with SIGSEGV in malloc()

Bug #282568 reported by Duncan Lithgow
6
Affects Status Importance Assigned to Milestone
Ekiga
Expired
Critical
gconf (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: ekiga

Ubuntu 8.10 updated October 13th
Ekiga 2.0.12-0ubuntu5

I started ekiga, went to the address book, created a new local address book and ekiga hung for a while and then crashed. Apport picked up the crash straight away.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/ekiga
NonfreeKernelModules: nvidia
Package: ekiga 2.0.12-0ubuntu5
ProcAttrCurrent: unconfined
ProcCmdline: ekiga
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 xmlDictCreate () from /usr/lib/libxml2.so.2
 xmlInitParserCtxt () from /usr/lib/libxml2.so.2
Title: ekiga crashed with SIGSEGV in malloc()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare scanner video

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

Following the guide at https://wiki.ubuntu.com/Backtrace here is a backtrace:

Starting program: /usr/bin/ekiga
[Thread debugging using libthread_db enabled]
[New Thread 0xb5692720 (LWP 21590)]
[New Thread 0xb54dbb90 (LWP 21596)]
[New Thread 0xb549ab90 (LWP 21597)]

(ekiga:21590): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(Gtk-Warning repeats four times)

[New Thread 0xb4c26b90 (LWP 21600)]
[New Thread 0xb4425b90 (LWP 21601)]
[New Thread 0xb3c24b90 (LWP 21602)]
[New Thread 0xb3423b90 (LWP 21604)]
[Thread 0xb4c26b90 (LWP 21600) exited]
[New Thread 0xb33e2b90 (LWP 21607)]
[New Thread 0xb33a1b90 (LWP 21608)]
[New Thread 0xb3360b90 (LWP 21609)]

(ekiga:21590): GLib-GIO-CRITICAL **: g_content_type_get_mime_type: assertion `type != NULL' failed
[New Thread 0xb331fb90 (LWP 21610)]
[New Thread 0xb32deb90 (LWP 21611)]
[New Thread 0xb329db90 (LWP 21612)]
[Thread 0xb3360b90 (LWP 21609) exited]

(ekiga:21590): GConf-CRITICAL **: gconf_client_get: assertion `GCONF_IS_CLIENT (client)' failed
[Thread 0xb4425b90 (LWP 21601) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb5692720 (LWP 21590)]
0xb76ffca9 in e_source_list_sync () from /usr/lib/libedataserver-1.2.so.11
(gdb)

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

I just noticed that the file made by gdb had a little bit more information and ended like this:

...
(gdb) Hangup detected on fd 0
error detected on stdin
The program is running. Exit anyway? (y or n) EOF [assumed Y]

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

Upstream says this is a GConf problem. I've opened question # 47868 <https://answers.edge.launchpad.net/ubuntu/+source/ekiga/+question/47868> to get me up and running again...
So how do we mark this as a gconf bug?

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
xmlDictCreate () from /usr/lib/libxml2.so.2
xmlInitParserCtxt () from /usr/lib/libxml2.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in ekiga:
importance: Undecided → Medium
Changed in ekiga:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

re assigned to gconf.

Changed in ekiga:
status: New → Triaged
Changed in ekiga:
status: New → Incomplete
Changed in ekiga:
importance: Unknown → Critical
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.