Bug 572403 – gimp-2.6 crashed with SIGSEGV in IA__g_object_get()

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 572403 - gimp-2.6 crashed with SIGSEGV in IA__g_object_get()


Summary:	gimp-2.6 crashed with SIGSEGV in IA__g_object_get()


Status:	RESOLVED FIXED

Product:	GIMP
Classification:	Other
Component:	General
Version:	2.6.5
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	2.6
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Duplicates:	573777 574176 (view as bug list)
Depends on:
Blocks:

Reported:	2009-02-19 13:08 UTC by Pedro Villavicencio
Modified:	2012-10-20 21:20 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
patch to gimpuimanager.c which does "#undef GTK_DISABLE_DEPRECATED" to avoid these crashes (408 bytes, patch) 2009-03-09 10:45 UTC, Nils Philippsen	none	Details \| Review

Description Pedro Villavicencio 2009-02-19 13:08:57 UTC

this report has been opened here:

https://bugs.edge.launchpad.net/ubuntu/+source/gimp/+bug/331306

"I'm trying select a region and do Autocrop to selection, so i open Gimp, select a region and click on the menu Image and get a crash"

".

+ Trace 212690

Thread 1 (process 6911)

#0 IA__g_object_get
at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1585
#1 gimp_ui_manager_menu_item_select
at /build/buildd/gimp-2.6.5/./app/widgets/gimpuimanager.c line 918
#2 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.8/gobject/gclosure.c line 767
#3 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 3244
#4 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 2977
#5 IA__g_signal_emit
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 3034
#6 IA__gtk_menu_item_select
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmenuitem.c line 795
#7 gtk_menu_shell_real_select_item
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmenushell.c line 1080
#8 gtk_menu_shell_button_press
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmenushell.c line 598
#9 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmarshalers.c line 84
#10 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.8/gobject/gclosure.c line 767
#11 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 3282
#12 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 2987
#13 IA__g_signal_emit
at /build/buildd/glib2.0-2.19.8/gobject/gsignal.c line 3034
#14 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkwidget.c line 4761
#15 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmain.c line 2396
#16 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.15.4/gtk/gtkmain.c line 1601
#17 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.15.4/gdk/x11/gdkevents-x11.c line 2363
#18 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.19.8/glib/gmain.c line 1814
#19 g_main_context_iterate
at /build/buildd/glib2.0-2.19.8/glib/gmain.c line 2448
#20 IA__g_main_loop_run
at /build/buildd/glib2.0-2.19.8/glib/gmain.c line 2656
#21 app_run
at /build/buildd/gimp-2.6.5/./app/app.c line 246
#22 main
at /build/buildd/gimp-2.6.5/./app/main.c line 406

Comment 1 Martin Nordholts 2009-02-19 18:13:18 UTC

Can this be reproduced when using stable versions of GLib and GTK+?

Comment 2 Sven Neumann 2009-02-19 21:54:35 UTC

Since you are using an unstable development version of gtk+, you should not be surprised that you observe crashes. Please report this to gtk+ instead.

Comment 3 Pedro Villavicencio 2009-02-19 23:10:25 UTC

re assigning to gtk+ then, thanks both.

Comment 4 Sebastien Bacher 2009-03-02 15:56:31 UTC

that seems to be a frequent crasher for gimp nowadays

Comment 5 Martin Nordholts 2009-03-02 17:59:24 UTC

*** Bug 573777 has been marked as a duplicate of this bug. ***

Comment 6 edward.coffey 2009-03-03 00:02:53 UTC

Sebastien - yes, for many people testing Ubuntu Jaunty at the moment GIMP is pretty-much a no-go area. It will run for a short while, but at some point, usually when accessing a menu (not clicking, just mousing around within the menu), it will lock up.

Comment 7 Sven Neumann 2009-03-04 21:05:09 UTC

*** Bug 574176 has been marked as a duplicate of this bug. ***

Comment 8 lcid-fire 2009-03-08 20:32:09 UTC

The very strange thing (to me) is - why is this just happening for gimp? There are quite many apps using gtk - but they don't have the problems gimp has...

Comment 9 Nils Philippsen 2009-03-09 10:11:52 UTC

Maybe comment #27 on the Fedora bugzilla ticket for this sheds some light on the issue: 

https://bugzilla.redhat.com/show_bug.cgi?id=486122

Comment #27 From  Matthias Clasen (mclasen@redhat.com)  2009-03-07 21:51:53 EDT

This is likely miscompilation due to

gimpuimanager.c: In function ‘gimp_ui_manager_menu_item_select’:
gimpuimanager.c:912: warning: implicit declaration of function
‘gtk_widget_get_action’
gimpuimanager.c:912: warning: initialization makes pointer from integer without
a cast


Don't compile with -DGTK_DISABLE_DEPRECATED if you are using deprecated
functions...

Comment 10 Sebastien Bacher 2009-03-09 10:42:44 UTC

reassigning to gimp since the comments make clear that the issue is there

Comment 11 Nils Philippsen 2009-03-09 10:45:26 UTC

Created attachment 130319 [details] [review]
patch to gimpuimanager.c which does "#undef GTK_DISABLE_DEPRECATED" to avoid these crashes

Comment 12 Sven Neumann 2009-03-10 13:56:04 UTC

That's definitely the wrong way to fix this. But I think I found where the actual problem is:

2009-03-10  Sven Neumann  <sven@gimp.org>

	Bug 572403 – gimp-2.6 crashed with SIGSEGV in IA__g_object_get()

	* configure.in: fixed check for newer version of GTK+ that
	determines if GTK_DISABLE_DEPRECATED is used.

Comment 13 Bob Vincent 2012-10-19 19:43:20 UTC

Why is this marked as "fixed" when I'm still seeing the problem in gimp 2.8.2?

Comment 14 Michael Schumacher 2012-10-19 21:53:40 UTC

Maybe because you are seeing something else, or maybe because some change made it to reappear - the original bug is three years old and was about the problem in a previous stable version of GIMP.

Comment 15 Michael Natterer 2012-10-20 21:20:29 UTC

If you still see the issue, please attach a stack trace and reopen the bug.