Bug 555705 – Creating two new images successively crashes GIMP

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 555705 - Creating two new images successively crashes GIMP


Summary:	Creating two new images successively crashes GIMP


Status:	RESOLVED DUPLICATE of bug 554966

Product:	GIMP
Classification:	Other
Component:	User Interface
Version:	2.6.0
Hardware:	Other Windows

Importance:	Normal major
Target Milestone:	---
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-10-09 17:12 UTC by André Köhler
Modified:	2008-10-09 19:57 UTC

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

Description André Köhler 2008-10-09 17:12:39 UTC

How to reproduce:
1. Start GIMP 2.6.0 for Windows
2. File->New
3. Select Preset "A5" and press OK
4. File->New
5. Select Preset "A5" or "A6" or anything else and press OK
6. CRASH!



Moreover I found out, that the other presets (800x600, 1024x768 etc.) do NOT crash GIMP.

Comment 1 Chris Mohler 2008-10-09 18:00:12 UTC

Can confirm on linux, 2.6.0.

Backtrace:
Starting program: /opt/gimp-2.6/bin/gimp-2.6 
[Thread debugging using libthread_db enabled]
[New Thread 0xb712d720 (LWP 9843)]
[New Thread 0xb6ecab90 (LWP 9849)]
[New Thread 0xb66c9b90 (LWP 9850)]

Program received signal SIGSEGV, Segmentation fault.

+ Trace 207966

Thread 3071465248 (LWP 9843)

#0 gimp_display_shell_scale_update_rulers
at gimpdisplayshell-scale.c line 167
#1 gimp_display_shell_set_unit
at gimpdisplayshell.c line 1492
#2 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#3 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#4 g_object_new
from /usr/lib/libgobject-2.0.so.0
#5 gimp_display_shell_new
at gimpdisplayshell.c line 805
#6 gimp_display_new
at gimpdisplay.c line 384
#7 gui_display_create
at gui-vtable.c line 343
#8 gimp_template_create_image
at gimptemplate.c line 416
#9 image_new_create_image
at image-new-dialog.c line 343
#10 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgobject-2.0.so.0
#33 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#34 ??
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#39 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgdk-x11-2.0.so.0
#41 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#42 ??
from /usr/lib/libglib-2.0.so.0
#43 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#44 app_run
at app.c line 246
#45 main
at main.c line 406

Comment 2 Sven Neumann 2008-10-09 18:36:47 UTC

Please check that you are using the latest released version before filing a bug report. We already released a bug-fix for this problem.

*** This bug has been marked as a duplicate of 554966 ***

Comment 3 Chris Mohler 2008-10-09 18:38:22 UTC

Sorry - should have checked for dupes first.  Will do so in the future...

Comment 4 André Köhler 2008-10-09 19:57:25 UTC

Sorry, didn't find it here at bugzilla and there was no 2.6.1 for Windows available.