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 614034 - crash in GIMP: Closing the Main_Window....
crash in GIMP: Closing the Main_Window....
Status: RESOLVED INCOMPLETE
Product: GIMP
Classification: Other
Component: General
2.6.8
Other All
: Normal critical
: 2.6
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-03-26 16:31 UTC by mushroomcult
Modified: 2010-09-25 03:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description mushroomcult 2010-03-26 16:31:57 UTC
What were you doing when the application crashed?
Closing the Main_Window...


Distribution: openSUSE 11.2 (x86_64)
Gnome Release: 2.28.2 (null) (SUSE)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: tish-aquastyle
Icon Theme: Gilouche
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 548298752 vsize: 548298752 resident: 224088064 share: 19734528 rss: 224088064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1269620826 rtime: 4426 utime: 4006 stime: 420 cutime:801 cstime: 29 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/local/bin/gimp-2.6'

[Thread debugging using libthread_db enabled]
[New Thread 0x7fbc88903710 (LWP 7908)]
[New Thread 0x7fbc89104710 (LWP 7907)]
0x00007fbc8ff79e6d in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 0x7fbc9368c7a0 (LWP 7906))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 file_save_cmd_callback
    at file-commands.c line 319
  • #6 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 gimp_ui_manager_activate_action
    at gimpuimanager.c line 525
  • #16 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #35 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #39 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #40 ??
    from /usr/lib64/libglib-2.0.so.0
  • #41 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #42 app_run
    at app.c line 246
  • #43 main
    at main.c line 406

	Inferior 1 [process 7906] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** Gtk **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed 
** Gtk **: gtk_box_pack: assertion `child->parent == NULL' failed 


----------- .xsession-errors ---------------------
Try: zypper install -C "debuginfo(build-id)=59c0fc3015abed7b7cf73daf0579a840f0f982a8"
Missing separate debuginfo for /usr/lib64/pango/1.6.0/modules/pango-basic-fc.so
Try: zypper install -C "debuginfo(build-id)=203a868751cb88b05a0b5f4224fac50f43432105"
Missing separate debuginfo for /usr/lib64/gio/modules/libgvfsdbus.so
Try: zypper install -C "debuginfo(build-id)=b382b3f9add202a5d7fc7dc926f0fce956ad0a6c"
Missing separate debuginfo for /usr/lib64/libgvfscommon.so.0
Try: zypper install -C "debuginfo(build-id)=9e9ab02215e444bd1e826a86fa14bd43dd6e984f"
Missing separate debuginfo for /lib64/libudev.so.0
Try: zypper install -C "debuginfo(build-id)=ced1c3712bd992340cd506bfc262826627fecdcc"
Missing separate debuginfo for /usr/lib64/gio/modules/libgioremote-volume-monitor.so
Try: zypper install -C "debuginfo(build-id)=99b0c12b19ab48b4560bf64c9166374050aa795b"
Missing separate debuginfo for /usr/lib64/liblcms.so.1
Try: zypper install -C "debuginfo(build-id)=ae9729f30893ed80f616fefc8b6db5c12b5f6da9"
Missing separate debuginfo for /usr/lib64/gtk-2.0/2.10.0/immodules/im-cedilla.so
Try: zypper install -C "debuginfo(build-id)=c58f5be928580154ed4d0ce92b7be25a98263205"
--------------------------------------------------
Comment 1 Martin Nordholts 2010-03-26 18:12:26 UTC
The crash is marked with <<<<:

  if (save_mode == GIMP_SAVE_MODE_SAVE_AND_CLOSE &&
      saved && ! display->image->dirty)  <<<<
    {
      gimp_display_close (display);
    }

So either display or display->image is NULL. I don't see how they could be NULL here though.
Comment 2 Martin Nordholts 2010-06-29 15:38:22 UTC
We need a step-by-step on how to reproduce
Comment 3 Fabio Durán Verdugo 2010-08-26 16:25:09 UTC
@mushroomcult: any news?
Comment 4 Fabio Durán Verdugo 2010-09-25 03:13:55 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!