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 8024 - Mouse doesnt draw when using the Graphire graphics tablet.
Mouse doesnt draw when using the Graphire graphics tablet.
Status: VERIFIED INCOMPLETE
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal normal
: 1.2
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks: 127786
 
 
Reported: 2000-03-29 02:03 UTC by bse
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bse 2001-01-28 15:50:11 UTC
Package: gimp
Version: 1.1.18 (Latest CVS)

Name........: Alex Roberts
Email.......: bse@error.fsnet.co.uk
Platform....: Debian Woody, kernel 2.2.14, AMD k6-266, 64meg, A6 Wacom Graphire
GIMP Version: 1.1.18 (Latest CVS)
GTK Version.: 1.2.7


-- Other system notes:

--

-- Problem description:
I've configured gtk, gimp and X to use my new Wacom Graphire tablet. the tablet works fine, but i cant use the mouse to draw, select, or use the context menus, etc. it just doesnt respond. 
the graphire mouse also has the same problem. this problem doesnt appear in the gnome-iconedit app.
--


-- How to repeat:
um. try to draw or anything with the mouse while having the tablet active...
--


-- Other comments:

--




------- Additional Comments From gosgood@idt.net 2000-03-30 05:03:47 ----

Subject: Same case with Intuos
From: "Garry R. Osgood" <gosgood@idt.net>
To: 8024@bugs.gnome.org
Message-Id: <38E32681.F86E023B@idt.net>
Date: Thu, 30 Mar 2000 05:03:47 -0500

package:      gimp
EMail       : gosgood@idt.net
GIMP Version: 1.1.18
GTK Version.: 1.2.7
Platform....: SGI Indigo IP20, SGI O2 IP32_5k

Same phenomenon observed here. Also observered in Gimp Version 1.1.15

Both the mouse and wacom devices were enabled via
the Dialogs->Input Device dialog
and their behavior monitored through
Dialogs->Device Status

When taking up the mouse, Device Status would
register the change, switching from wacom to mouse

However, the cursor did not change shape on
mouse button down, leading me to surmise that
Tool::CursorUpdateFunc are not being invoked
on the currently active tool

Given that the bug is present in 1.1.15, I
don't think any recent changes have triggered
this.

Be good, be well

Garry




------- Additional Comments From egger@suse.de 2000-06-26 15:23:21 ----

Subject: Regarding GIMP bug #8024
From: egger@suse.de
To: 8024@bugs.gnome.org
Cc: gosgood@idt.net
Message-Id: <20000626211854.112DB5969@Nicole.muc.suse.de>
Date: Mon, 26 Jun 2000 21:23:21 +0200 (CEST)

Hiho!

 Have you been able to discover that problem with
 more recent versions of GIMP, too?

 If yes, I'm going to check the signalling in GIMP....

-- 

Servus,
       Daniel




------- Additional Comments From gosgood@idt.net 2000-07-31 12:51:19 ----

Subject: 8024 Addenda
From: "Garry R. Osgood" <gosgood@idt.net>
To: 8024@bugs.gnome.org
Message-Id: <3985AE87.5423E727@idt.net>
Date: Mon, 31 Jul 2000 12:51:19 -0400

All,

The problem persists with Gimp 1.1.24, and involves Wacom
Intuos as well as Grapphire. In investigating the possibility of
teaching the Hollywood branch about pressure sensitivity, I
came across this tasty morsel, which suggests that GTK itself
is having trouble with proximity events; these never happen
with the symmetry that one desires and may be contributory
to the mouse never being recognized as a device.

http://www.gtk.org/~otaylor/xinput/howto/setting-up.html

See the last article,

"The mouse doesn't work with the GIMP (or other GTK programs)"

The suggested workaround does not succeed on SGI platforms.

It seems this material is about a year old.

The hunt continues...

Garry Osgood




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 10:50 -------
This bug was previously known as bug 8024 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=8024
Originally filed under the gimp product and general component.

The original reporter (bse@error.fsnet.co.uk) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, egger@suse.de.

Comment 1 Raphaël Quinet 2001-04-26 18:10:58 UTC
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 2 Daniel Egger 2001-10-24 09:18:14 UTC
if this is really still an issue (which I can't verify in lack
of an Graphire, my Intuos works fine) AND we have a chance to
fix it in GIMP we should try to do it for 1.2.x. 
Comment 3 stryypgya 2003-02-16 05:33:39 UTC
I just got a Wacom Graphire 2 tablet, and set it up.  At first, I
fired up the Gimp (1.2.3), and everything was spiffy.  Then I closed
it down, and did some web surfing.  Went back in, and I can select
tools, edit layers, and do generally anything else I might need to,
but it won't accept any input into the "image area".  Tried switching
it back out for my optical mouse, and now it won't recognize that
anymore (!).  Everything else works fine, but I can't do ANY editing,
selecting, or anything.
Comment 4 Sven Neumann 2003-05-11 00:04:43 UTC
I am not sure this is even a GIMP bug. Without help from owners of
this particular tablet we can't do anything about it. Moving to
milestone 1.2.5.
Comment 5 Dave Neary 2003-05-21 16:26:04 UTC
Moving to 1.2.6 milestone, since it is looking like there will be a pretty quick
1.2.( release.
Comment 6 Sven Neumann 2003-06-12 11:02:33 UTC
This is very likely a driver problem. People keep reporting weird
problems with Graphire tablets.
Comment 7 Sven Neumann 2004-02-11 18:27:25 UTC
It's been a while since the last report on this subject and new
drivers have been released in the meantime. Can we get some feedback
from a Graphire user telling us if this is still a problem ?
Comment 8 Sven Neumann 2004-03-22 16:20:28 UTC
We are about to release 2.0 and will not put any more efforts into
gimp-1.2 development. So this bug report is not going to get any
further attention. I am closing it now.