ekiga crashed with SIGSEGV in g_type_check_is_value_type()

Bug #349719 reported by Kevin Soviero
10
Affects Status Importance Assigned to Milestone
ekiga (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: ekiga

ekiga crashed with SIGSEGV in g_type_check_is_value_type()

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.0.1-1ubuntu2
ProcCmdline: ekiga
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 g_type_check_is_value_type ()
 g_value_type_compatible () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
Title: ekiga crashed with SIGSEGV in g_type_check_is_value_type()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:IA__g_type_check_is_value_type (type=168052584)
IA__g_value_type_compatible (src_type=168052584,
g_value_object_collect_value (value=0xa0800dc,
IA__g_signal_emit_valist (instance=0x9fc00c8,
IA__g_signal_emit_by_name (instance=0x9fc00c8,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
visibility: private → public
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in ekiga (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in ekiga (Ubuntu):
status: Incomplete → Invalid
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.