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 704658 - Backspacing on the keyboard shortcuts dialog seems to hang Gimp
Backspacing on the keyboard shortcuts dialog seems to hang Gimp
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: User Interface
2.8.6
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-07-22 06:49 UTC by srihari
Modified: 2013-10-04 11:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of Gimp Hanging when trying to backspace in the Keyboard Shortcuts Dialog (138.85 KB, image/png)
2013-07-27 08:16 UTC, srihari
Details

Description srihari 2013-07-22 06:49:59 UTC
- Open the keyboard shortcuts dialog
- Type in something > 3 characters long
- backspace all the way

It takes a very long time, close to 30 seconds, to backspace till the last character and type again.
Comment 1 Michael Natterer 2013-07-27 06:46:21 UTC
I can type dozens of characters and backspace them away, each key stroke
takes about a fraction of a second to filter the action tree.

I have no idea what's going on there, can anyone reproduce this?
Comment 2 Michael Schumacher 2013-07-27 07:10:03 UTC
We know virtually nothing about srihari's system, only that it seem to be some sort of Linux if the OS field is set correctly...
Comment 3 srihari 2013-07-27 08:16:27 UTC
Created attachment 250254 [details]
Screenshot of Gimp Hanging when trying to backspace in the Keyboard Shortcuts Dialog

I try to backspace something I entered. It stops backspacing when 2 characters are left and then Hangs GIMP 2.8.6.
Comment 4 Michael Schumacher 2013-07-27 08:18:59 UTC
You should report this to your distro's bugtracker - they can continue it here if they can determine that this is a bug in GIMP and not distro-specific.
Comment 5 srihari 2013-07-27 08:27:20 UTC
This happens even in the gimp I built from source, on the master branch.
Here is some system information:

head -n1 /etc/issue:
 Ubuntu 12.04.2 LTS \n \l

uname -a:
Linux srihari-laptop 3.2.0-51-generic-pae #77-Ubuntu SMP Wed Jul 24 20:40:32 UTC 2013 i686 i686 i386 GNU/Linux

Not sure if this is useful, but when the keyboard shortcut dialog hangs, I see this on my terminal:


(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed

(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed

(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed

(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed

(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed

(gimp-2.9:25194): Gtk-CRITICAL **: IA__gtk_tree_path_compare: assertion 'b->depth > 0' failed
Comment 6 Michael Natterer 2013-07-27 15:58:04 UTC
Smells like Unbuntu GTK+ destruction to me. For completeness, please
paste the output of "gimp --version --verbose", and please report
this to the ubuntu bug tracker anyway.
Comment 7 srihari 2013-07-28 06:09:08 UTC
gimp --version --verbose 
GNU Image Manipulation Program version 2.8.6
git-describe: GIMP_2_8_4-123-g82888aa

using GEGL version 0.2.1 (compiled against version 0.2.1)
using GLib version 2.32.4 (compiled against version 2.32.3)
using GdkPixbuf version 2.26.1 (compiled against version 2.26.1)
using GTK+ version 2.24.10 (compiled against version 2.24.10)
using Pango version 1.30.0 (compiled against version 1.30.0)
using Fontconfig version 2.8.0 (compiled against version 2.8.0)
using Cairo version 1.10.2 (compiled against version 1.10.2)


Thanks Mitch.
Will report to ubuntu bug tracker.
Comment 8 srihari 2013-07-28 16:22:03 UTC
Reported to ubuntu here:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1205769
Comment 9 Michael Schumacher 2013-10-04 11:25:46 UTC
That bug suggests that it might be specific to Ubuntu 12.04.
Comment 10 Michael Natterer 2013-10-04 11:48:18 UTC
Most likely caused by some patch in Ubuntu 12.04's GTK+, let's close it
as NOTGNOME.