GNOME Bugzilla – Bug 587543
crash when invoking certain actions by keyboard shortcut
Last modified: 2009-07-08 19:46:44 UTC
What were you doing when the application crashed? Pressing shift+- which I have shortcutted to the Unsharp Mark filter. Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.29-2-amd64 #1 SMP Sun May 17 17:15:47 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10601901 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 422907904 vsize: 422907904 resident: 164544512 share: 18485248 rss: 164544512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1246469048 rtime: 894 utime: 770 stime: 124 cutime:73 cstime: 20 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gimp-2.6' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fd3b6921760 (LWP 24473)] [New Thread 0x7fd3aabf1950 (LWP 24475)] [New Thread 0x7fd3ab3f2950 (LWP 24474)] (no debugging symbols found) 0x00007fd3b295826f in waitpid () from /lib/libpthread.so.0
+ Trace 216282
Thread 1 (Thread 0x7fd3b6921760 (LWP 24473))
---- Critical and fatal warnings logged during execution ---- ** Gimp-PDB **: gimp_procedure_get_arguments: assertion `GIMP_IS_PROCEDURE (procedure)' failed ----------- .xsession-errors --------------------- [swscaler @ 0x1693bc0]No accelerated colorspace conversion found. (nautilus:5031): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (nautilus:5031): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (nautilus:5031): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (nautilus:5031): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (gimp-2.6:24473): Gimp-PDB-CRITICAL **: gimp_procedure_get_arguments: assertion `GIMP_IS_PROCEDURE (procedure)' failed warning: .dynamic section for "/usr/lib/libz.so.1" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libbz2.so.1.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
If I do not use the keyboard shortcut, I do not get a crash. Also, if I use the keyboard shortcut after having used Unsharp Mask by clicking the menu, it doesn't crash. So I only get the crash if I use the keyboard shortcut to invoke the function the first time I use it. Hm, it seems that I have shift+- configured to invoke the Recently Used filter (I thought I had configured it to run Unsharp Mask), so the crash is coming from invoking that with no filters having been used before! That makes sense: Invoking the Recently Used filter is not going to work if no filters has ever been used. I guess the menu-entry doesn't appear, so it is impossible to reach this crash using the mouse, but with the keyboard shortcut it is. To reproduce: 1) Put this line in your ~/.gimp-2.6/menurc: (gtk_accel_path "<Actions>/plug-in/plug-in-recent-01" "underscore") 2) Start Gimp 3) Open an image 4) Press shift+- (_)
Thanks for a good bug report, they are rare these days. Fix pushed to master and gimp-2-6: commit f07d89de2aafdc3f1e28f87017cfcb6ede2f2791 Author: Martin Nordholts <martinn@src.gnome.org> Date: Wed Jul 1 21:45:33 2009 +0200 Bug 587543 – crash in GNU Image Manipulation Program: Pressing shift+- Not all actions have procedures associated with them, for example unused "plug-in-recent-[N]" actions, so check for NULL before we invoke the plug-in action app/widgets/gimppluginaction.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-)
Thank you for the swift resolution.