linuxdcpp crashed with SIGSEGV in g_type_check_is_value_type()

Bug #260378 reported by Andrey Zhekov
12
Affects Status Importance Assigned to Milestone
linuxdcpp (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: linuxdcpp

Ubuntu 8.10 dev. branch
linuxdcpp 1.0.2-1

Don't know the reason of the crash...the program worked as usual

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/linuxdcpp
NonfreeKernelModules: nvidia
Package: linuxdcpp 1.0.2-1
ProcAttrCurrent: unconfined
ProcCmdline: linuxdcpp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: linuxdcpp
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: linuxdcpp crashed with SIGSEGV in g_type_check_is_value_type()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse pulse-access pulse-rt sambashare video

Revision history for this message
Andrey Zhekov (x3ro.daemon) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_type_check_is_value_type () from /usr/lib/libgobject-2.0.so.0
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

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in linuxdcpp:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in linuxdcpp:
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.