anjuta crashed with SIGSEGV in IA__gtk_bin_get_child()

[Justin Lee]

Binary package hint: anjuta

I was trying out anjuta, opened a new glade file, added some dialog and playing with the docking windows. When I added an input dialog and tried to move the property dock to the bottom, anjuta crashed. This problem is easy to be reproduced so far on my three different machines. I will attach some screen shots explaining how to reproduce it later.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/anjuta
Package: anjuta 2:2.24.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: anjuta
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: anjuta
StacktraceTop:
 IA__gtk_bin_get_child (bin=0xa09c600)
 gtk_input_dialog_set_device (w=0xa2608e8, data=0x9c36288)
 gtk_input_dialog_screen_changed (widget=0xa2608e8,
 IA__g_cclosure_marshal_VOID__OBJECT (closure=0x9c6ac60,
 g_type_class_meta_marshal (closure=0x9c6ac60,
Title: anjuta crashed with SIGSEGV in IA__gtk_bin_get_child()
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Justin Lee (cf9404)]

Please see the attachment to reproduce the crash.

[Apport retracing service (apport)]

StacktraceTop:IA__gtk_bin_get_child (bin=0xa09c600)
gtk_input_dialog_set_device (w=0xa2608e8, data=0x9c36288)
gtk_input_dialog_screen_changed (widget=0xa2608e8,
g_cclosure_marshal_VOID__OBJECT ()
?? () 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.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".