Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8752 - [gimp 2.4.2-1] no tools at all work with tablet, everything moves layer

Attached to Project: Arch Linux
Opened by Gerry (gerry) - Saturday, 24 November 2007, 12:53 GMT
Last edited by Greg (dolby) - Monday, 21 July 2008, 00:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture x86_64
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Whenever I attempt to use any tool at all with a tablet input device, Gimp now always uses the move layer tool in stead, effectively making the program totally unusable with tablet devices. The first time I enabled the tablet in this version of Gimp things seemed to work, but then I noticed after a little while that the eyedropper tool didn't work (moving the layer in stead), and after a restart of the Gimp hoping to fix this, I discovered that ALL tools, including pen and pencil, now behaves in this way. Removing ~/.gimp* and reconfiguring from scratch has no effect.

gimp version 2.4.2-1, 64-bit.

Steps to reproduce:
1. Make sure Gimp is configured to use extended tablet input devices (stylus etc).
2. Use the enabled tablet devices for a while, switching tools and such
3. Eventually everything acts like 'move layer', with no way of fixing things
This task depends upon

Closed by  Greg (dolby)
Monday, 21 July 2008, 00:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  Assuming fixed
Comment by Tobias Kieslich (tobias) - Sunday, 25 November 2007, 00:51 GMT
hm, the build of the latest package was straight forward for me. But 1. I'm the 32bit maintainer and 2. I dun have a tablet (/me looking jealously at Gerry). Okay, on the more serious part, I don't think Andy, who probably built the 64 bit version has one either. So we have to figure out:
1. if the problem happens on a 32 bit platform, too. If anyone can try that it would really help.
2. Gerry, if you could build the package on your box (2.4.2) and confirm if the error is still there
3. Gerry, also on your side, if the error still is there, build 2.4.1 and see if it's gone (If so, it's most likely upstream and we shall report to gimp.org)

From my end there is nothing I can do but to guide you, since I lack both hardware (64bit and a tablet)
BTW, do you have a wacom or another brand?
Comment by Tobias Kieslich (tobias) - Tuesday, 04 December 2007, 18:53 GMT
Any input? I CANT REPRODUCE IT
Comment by Gerry (gerry) - Wednesday, 05 December 2007, 12:45 GMT
Hey, sorry for not getting back to you before. I have problems consistently reproducing this myself, unfortunately. Perhaps it's related to that seemingly random mouse-doesn't-work-with-tablet bug that's been in Gimp for years without getting fixed. Anyway, the bug definitely IS there, but whether or not it happens is so random that coming to any conclusions as to what is causing it is very hard. Sometimes -- like when I reported the bug -- it happens all the time, other times it doesn't happen at all. When it does happen the only way to get rid of it is a reboot (so exactly like the mouse bug then). Uninitialized variables somewhere, perhaps.

Sorry I can't be of much help. I'll let you know if I figure out some way to consistently reproduce this.
Comment by Tobias Kieslich (tobias) - Wednesday, 05 December 2007, 18:17 GMT
okay, those bugs suck, the ones you can't reproduce ...
but still some questions:
was the error there in 2.4.1, or did it happen in there?
and maybe you can build it for you from abs and see if it more reliable
Comment by Gerry (gerry) - Thursday, 06 December 2007, 21:01 GMT
Unfortunately I don't know if this happened in 2.4.1, as I didn't try that version with the tablet. The tablet is a Wacom Intuos2, btw, using the linuxwacom driver. The tablet works fine in Windows and also in non-GTK Linux apps.

I haven't had the all-tools-work-the-same bug return, but I've been having some other issues that's probably related. Just a moment ago, for example, the Gimp practically locked itself into draw mode so that none of the UI responded at all, and just moving around the cursor would draw in the image window. Undo completely messed up the image, too (not undoing anything, just making things worse). I ended up having to use the keyboard to switch to a terminal and kill the Gimp to get out of it, since quit didn't work.

Anyway, I'll try building from ABS and see if that improves things.
Comment by Tobias Kieslich (tobias) - Thursday, 06 December 2007, 21:18 GMT
thanks for the round up, you mentioned that gtk apps are affected, I wonder if inkscape which apparently has tablet support too, is also affected. Dio you use Inkscape at all?
Comment by Gerry (gerry) - Monday, 17 December 2007, 18:48 GMT
Update: I compiled GTK and Gimp from source and have used that for three or four days now, and have not had any problems yet (except the occasional old mouse-doesn't-work bug, but even that was fixable by switching virtual desktops).
Comment by Tobias Kieslich (tobias) - Wednesday, 12 March 2008, 03:42 GMT
Did you have problems again with the pre-compiled packages?
Comment by Greg (dolby) - Saturday, 24 May 2008, 09:10 GMT
Does it still happen? Even with latest gimp?

Loading...