gmanedit crashed with SIGSEGV in value_lcopy_boolean()

[Terence Simpson]

Binary package hint: gmanedit

gmanedit crashed immediately after choosing File -> Quit
Steps to reproduce:
1) Start gmanedit
2) Choose File -> Quit

Kubuntu: 8.10
gmanedit: 0.4.1-1.1
libglib2.0-0: 2.18.2-0ubuntu2
libgtk2.0-0: 2.14.4-0ubuntu2

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gmanedit
NonfreeKernelModules: ath_hal
Package: gmanedit 0.4.1-1.1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/gmanedit
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 11
SourcePackage: gmanedit
StacktraceTop:
 value_lcopy_boolean (value=0xbfed0ea8, n_collect_values=1,
 IA__g_signal_emit_valist (instance=0x8bc1800, signal_id=36,
 IA__g_signal_emit_by_name (instance=0x8bc1800,
 IA__g_cclosure_marshal_VOID__VOID (closure=0x8c1fa58,
 IA__g_closure_invoke (closure=0x8c1fa58, return_value=0x0,
Title: gmanedit crashed with SIGSEGV in value_lcopy_boolean()
Uname: Linux 2.6.27-11-generic i686
UserGroups: adm admin audio cdrom dialout dip disk floppy fuse lpadmin netdev operator plugdev powerdev scanner staff video

[Apport retracing service (apport)]

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

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

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!.