Debian Bug report logs - #463772
gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Yaroslav Halchenko <debian@onerussian.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Date: Sun, 03 Feb 2008 00:49:35 -0500

[Message part 1 (text/plain, inline)]

Package: gimp
Version: 2.4.3-1
Severity: normal


Hi,

Just got my wacom pen configured, but only then mentioned that regular
mouse (actually thinkpad's stick now fails to paint). Boiled down to:
if I go to Preferences -> Input Devices -> Configure Extended Input
Devices, if I set 'Configured Mouse' to some mode (thus it appears in
Device Status), then if I try to do something using any tool I start
getting errors in original terminal + no actual result to the image.

Errors are :

(gimp:1947): Gimp-Base-CRITICAL **: temp_buf_resize: assertion `width > 0 && height > 0' failed

Relevant part of xorg.conf:

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Protocol"  "ExplorerPS/2"

        #Option         "ZAxisMapping" "4 5 6 7"
        
        Option "Device" "/dev/input/mice"
        Option "EmulateWheel" "on"
        Option "EmulateWheelTimeout" "200"
        Option "EmulateWheelButton" "2"
        Option "YAxisMapping" "4 5"
        Option "XAxisMapping" "6 7"
EndSection


real problem is revealed by xinput list, but unfortunately I found no way
to tune axis min/max values... I am attaching full output of xinput list along,
relevant part is:



"Configured Mouse"      id=5    [XExtensionPointer]
        Axis 0 :
                Min_value is -1
                Max_value is -1
                Resolution is 1

"Virtual core pointer"  id=1    [XPointer]
        Axis 0 :
                Min_value is 0
                Max_value is -1
                Resolution is 0

so my wild guess is that Configured Mouse should had Min_value == 0 and may be
resolution to 0? ot set to screen size?

It might be an issue with xserver as well  (1:7.3+10) so if you think that it
provides bogus default values for those params -- feel free to clone and
reassign, but I think gimp should handle this situation in a nice way
itself.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-rc7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gimp depends on:
ii  gimp-data              2.4.3-1           Data files for GIMP
ii  libaa1                 1.4p5-33          ascii art library
ii  libart-2.0-2           2.3.19-3          Library of functions for 2D graphi
ii  libatk1.0-0            1.20.0-1          The ATK accessibility toolkit
ii  libc6                  2.7-6             GNU C Library: Shared libraries
ii  libcairo2              1.4.14-1          The Cairo 2D vector graphics libra
ii  libdbus-1-3            1.1.2-1           simple interprocess messaging syst
ii  libdbus-glib-1-2       0.74-1            simple interprocess messaging syst
ii  libexif12              0.6.16-2.1        library to parse EXIF files
ii  libfontconfig1         2.5.0-2           generic font configuration library
ii  libfreetype6           2.3.5-1+b1        FreeType 2 font engine, shared lib
ii  libgimp2.0             2.4.3-1           Libraries for the GNU Image Manipu
ii  libglib2.0-0           2.14.5-2          The GLib library of C routines
ii  libgtk2.0-0            2.12.5-2          The GTK+ graphical user interface 
ii  libgtkhtml2-0          2.11.1-1          HTML rendering/editing library - r
ii  libhal1                0.5.10-5          Hardware Abstraction Layer - share
ii  libjpeg62              6b-14             The Independent JPEG Group's JPEG 
ii  liblcms1               1.16-8            Color management library
ii  libmng1                1.0.9-1           Multiple-image Network Graphics li
ii  libpango1.0-0          1.18.4-1          Layout and rendering of internatio
ii  libpng12-0             1.2.15~beta5-3    PNG library - runtime
ii  libpoppler-glib2       0.6.2-1           PDF rendering library (GLib-based 
ii  librsvg2-2             2.20.0-1          SAX-based renderer library for SVG
ii  libtiff4               3.8.2-7           Tag Image File Format (TIFF) libra
ii  libwmf0.2-7            0.2.8.4-6         Windows metafile conversion librar
ii  libx11-6               2:1.0.3-7         X11 client-side library
ii  libxext6               1:1.0.3-2         X11 miscellaneous extension librar
ii  libxmu6                2:1.0.4-1         X11 miscellaneous utility library
ii  libxpm4                1:3.5.7-1         X11 pixmap library
ii  zlib1g                 1:1.2.3.3.dfsg-11 compression library - runtime

Versions of packages gimp recommends:
ii  gimp-gnomevfs                 2.4.3-1    GNOME-VFS URI plugin for GIMP
ii  gimp-python                   2.4.3-1    Python support and plugins for GIM

-- no debconf information

[xinput.list.log (text/plain, attachment)]

[xorg.conf (text/plain, attachment)]

Message #10 received at 463772@bugs.debian.org (full text, mbox, reply):

From: Ari Pollak <ari@debian.org>

To: Yaroslav Halchenko <debian@onerussian.com>, 463772@bugs.debian.org

Subject: Re: Bug#463772: gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Date: Sun, 03 Feb 2008 01:07:53 -0500

Is there an actual problem here other than the warnings on standard
error? The core input device should work fine in GIMP without being
configured as an extended input device.

Message #15 received at 463772@bugs.debian.org (full text, mbox, reply):

From: Yaroslav Halchenko <debian@onerussian.com>

To: Ari Pollak <ari@debian.org>

Cc: 463772@bugs.debian.org

Subject: Re: Bug#463772: gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Date: Sun, 3 Feb 2008 01:45:27 -0500

well -- then it leads to another weird behaviors:

if I enable only stylus of wacom pen -- then core works but somewhat
funny --- if I switch to stylus (draw smth with it), then gimp doesn't
switch back to core unless I move mouse away from drawing canvas -- then
when I come back it works

if I enabled both stylus and eraser (or just eraser) -- core pointer has
no effect on the image and never becomes active in the list of devices

On Sun, 03 Feb 2008, Ari Pollak wrote:

> Is there an actual problem here other than the warnings on standard
> error? The core input device should work fine in GIMP without being
> configured as an extended input device.


-- 
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student  Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW:     http://www.linkedin.com/in/yarik        

Message #24 received at 463772@bugs.debian.org (full text, mbox, reply):

From: grin <grin@grin.hu>

To: 463772@bugs.debian.org

Subject: seen the same lately

Date: Tue, 3 Mar 2009 10:34:18 +0100

Version: 2.4.7-1
Found: 2.4.7-1

Actually met this one now, with a mousepen tablet. Basically I cannot
use tablet and mouse together. 

If I disable all extended input sources, I can use mouse. 

If I enable the tablet, the mouse will not work; either I disable
extended input which makes no mouse events inside gimp (except menus)
or enable it, which gives coordinates around minus MAXINT, which is
probably out of bounds (and sanity) for gimp so it
throws the warnings mentioned earlier.

I have the same effect with 'xinput list', looks bad, so it might not
be a gimp problem, I cannot point to anyone though.

Message #29 received at 463772@bugs.debian.org (full text, mbox, reply):

From: Cedric Laczny <cedric.laczny@gmx.de>

To: 463772@bugs.debian.org

Subject: Re: Bug#463772: gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Date: Sat, 11 Apr 2009 19:21:27 +0200

I experienced a similar problem. I don't know about error messages as I 
started GIMP directly and not via a console.
But I had a working stylus and eraser but when using to mouse, I got no effect 
on the image, no matter what drawing tool I used.
I figured out that disabling _all_ extended input devices made my mouse work 
again, although the stylus was now no longer pressure sensitive (seems 
reasonable).
But when I now enabled the stylus and eraser again (set to Mode: Screen) 
everything worked as expected! The mouse resulted in effects as well as the 
stylus/eraser including pressure sensitivity.
However, when I changed the characteristics of the stylus using wacomcpl, I 
ran into the same problem again. It could be fixed with the disable + enable 
procedure. So apparently, when using wacomcpl, it must mix up something in 
the configuration so that GIMP needs to "reset" the extended input devices.

Hope this helps.

Message #34 received at 463772@bugs.debian.org (full text, mbox, reply):

From: Cedric Laczny <cedric.laczny@gmx.de>

To: 463772@bugs.debian.org

Subject: Re: Bug#463772: gimp: enabled 'configured mouse' (insted of core pointer) brings an error

Date: Fri, 12 Feb 2010 23:41:06 +0100

[Message part 1 (text/plain, inline)]

Hi, after thinking the problem was fixed, once and for all, I ran into the 
same problem, again...
This time, my mentioned workaround did not work. I could specify whatever 
Input device combination and in whatever Mode. However, mouse and pen didn't 
want to work at the same time.
Then I read the answer grin:
which gives coordinates around minus MAXINT, which is
probably out of bounds (and sanity) for gimp
This finally brought me to change the mode from 'Relative' to 'Absolute' using wacomcpl.
And this made the combination of mouse and pen work, even with pressure sensitivity!
Therefore, my assumption: GIMP needs the Absolute position or its coordinates get mixed up.
For me, having one of the latest stable xorg-server and xorg-drivers installed (on gentoo) and working with evdev, nothing beats setting the wacom stuff directly in /etc/X11/xorg.conf.
Although I hope this will change, the sooner or the later.
Perhaps this helps someone.

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.