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 556045 - crash in GNU Image Manipulation Program: I was opennig a new proj...
crash in GNU Image Manipulation Program: I was opennig a new proj...
Status: RESOLVED DUPLICATE of bug 554966
Product: GIMP
Classification: Other
Component: General
2.6.0
Other All
: High critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2008-10-12 18:36 UTC by Simone
Modified: 2008-10-12 18:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Simone 2008-10-12 18:36:37 UTC
What were you doing when the application crashed?
I was opennig a new project with a psd document opened with GIMP in the background


Distribution: openSUSE 11.0 (i586)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche

Memory status: size: 254521344 vsize: 254521344 resident: 129007616 share: 21291008 rss: 150298624 rss_rlim: 1805035520
CPU usage: start_time: 1223832964 rtime: 43260 utime: 40298 stime: 2962 cutime:4732 cstime: 1530 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb71a56c0 (LWP 4163)]
[New Thread 0xb6429b90 (LWP 4165)]
[New Thread 0xb6c2ab90 (LWP 4164)]
0xffffe430 in __kernel_vsyscall ()

Thread 1 (Thread 0xb71a56c0 (LWP 4163))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 gimp_display_shell_scale_update_rulers
  • #10 gimp_display_shell_set_unit
  • #11 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #14 gimp_display_shell_new
  • #15 gimp_display_new
  • #16 gui_display_create
  • #17 gimp_template_create_image
  • #18 image_new_create_image
  • #19 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #30 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #35 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #38 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #43 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #46 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #50 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #51 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #52 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #53 app_run
  • #54 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (29 sec old) ---------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
(script-fu:4022): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
(script-fu:4113): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0xa0a2250)" of type `GString'
--------------------------------------------------
Comment 1 Martin Nordholts 2008-10-12 18:39:04 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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