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 83780 - Wacom in window mode, crash in ink_pen_ellipse
Wacom in window mode, crash in ink_pen_ellipse
Status: RESOLVED DUPLICATE of bug 83779
Product: GIMP
Classification: Other
Component: libgimp
1.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
Daniel Egger
Depends on:
Blocks:
 
 
Reported: 2002-06-01 06:13 UTC by Akkana Peck
Modified: 2002-06-01 08:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Akkana Peck 2002-06-01 06:13:29 UTC
I have a new Wacom Graphire 2 (usb) that I just got working.  The three
wacom devices are using Absolute coordinates in XF86Config-4 (because the
howtos all recommend that setting).

If I set all three devices (stylus, eraser and mouse) to Screen mode, then
stylus and eraser work (mouse has some problems, maybe contending with the
PS2 mouse, but I'll track those down some other time).  But since my screen
is big and my window may not fill it, I end up having to draw in a tiny
postage-stamp area.  I'd prefer to use Window mode and have the full area
of my tablet correspond to the image window (that is what it's for, right?)

If I set any of the three devices to Window mode, and set the stylus
drawing tool to the ink pen, then as soon as I touch stylus to tablet, gimp
crashes, in ink_pen_ellipse, line 786 of ink.c (the line where it's calling
ink_options->function()).  It turns out that x_center is nan, though
y_center looks more reasonable.

We got here via ink_button_press, and it looks like that nan X coordinate
came from 
  gdisplay_untransform_coords_f (gdisp, bevent->x, bevent->y,
				 &x, &y, TRUE);

I haven't traced it any further than that yet -- had trouble debugging
because of the server grab (I have to debug from another machine and my
laptop batteries ran out.)  Looks like maybe I can just comment out the
grabs in ink_button_press if I want to debug this more easily.  Let me know
if you need more details or further tracing.

I also checked 1.3.7, but it looks like 1.3 doesn't handle tablets yet?  It
has Device Status but doesn't see anything but core pointer, and it doesn't
have the Input Devices dialog.  Or has that just moved somewhere else?
Comment 1 Sven Neumann 2002-06-01 08:21:37 UTC

*** This bug has been marked as a duplicate of 83779 ***