GNOME Bugzilla – Bug 556045
crash in GNU Image Manipulation Program: I was opennig a new proj...
Last modified: 2008-10-12 18:39:04 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 ()
+ Trace 208079
Thread 1 (Thread 0xb71a56c0 (LWP 4163))
----------- .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' --------------------------------------------------
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 ***