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 613631 - Spacebar panning skips erratically all over the place.
Spacebar panning skips erratically all over the place.
Status: RESOLVED DUPLICATE of bug 602752
Product: GIMP
Classification: Other
Component: User Interface
2.6.7
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-03-22 20:50 UTC by Paul d'Aoust
Modified: 2010-03-23 17:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Paul d'Aoust 2010-03-22 20:50:03 UTC 
Hi there. In Linux (specifically, Ubuntu 9.04), I experience erratic behaviour when trying to pan via holding down the spacebar. It doesn't matter whether I have compositing turned on or off. I have tested it in Windows, but I've forgotten the results; sorry!

Here's what happens. If I hold down the spacebar and move my mouse down and to the right, for example, it will move a bit, then snap back to the centre and erratically move in the opposite direction from my mouse direction, hopping very small distances each time -- around 50 pixels per skip.
Comment 1 Sven Neumann 2010-03-22 23:51:25 UTC 
What version of the X.org server is that? What version of GTK+? Did you report this in the Ubuntu bug-tracker already (you should)?
Comment 2 Sven Neumann 2010-03-22 23:54:28 UTC 
Might be a duplicate of bug #602752.
Comment 3 Paul d'Aoust 2010-03-23 17:13:45 UTC 
Looks like this is a dupe. Funny, I searched through all the bugs that mentioned 'pan' before I posted this.

Anyway, if you still want my details, they are xorg 1.6.4-2ubuntu4.2, nvidia 173.14.20-0ubuntu5, and libgtk 2.18.3-1ubuntu2.2.

So, if someone's already got a bug going in the GNOME tracker, and potential issues are already being discussed there, am I exonerated from having to post a report downstream? :-)

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