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 749231 - GIMP slows down my mouse even with minimal hardware resource load
GIMP slows down my mouse even with minimal hardware resource load
Status: RESOLVED DUPLICATE of bug 736411
Product: GIMP
Classification: Other
Component: User Interface
2.8.14
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-05-11 14:59 UTC by Jeb Eldridge
Modified: 2015-07-16 14:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeb Eldridge 2015-05-11 14:59:08 UTC
While editing a Searchable PDF file I have imported to GIMP, the mouse tends to slow down and appear to "skip" or "hop" around the computer screen when I move it, almost in a fashion like when you slow down the frames per second on a video clip - the same idea.
This is causing severe problems while working on a file, as it is difficult to determine where exactly I am editing on the photograph/PDF.

I have attempted bringing down the DPI of the image during import and also switched out of Single Window Mode to Classic Mode (with three individual windows) to no luck. Bringing down the DPI doesn't even help speed up the mouse. It's really an odd situation as I've never experienced this while attempting to edit a JPEG or PNG photo.



Here are my computer specs:

OS: Windows 10 Professional Technical Preview Build 10074 (64-Bit)
Processor: AMD Phenom II X4 850 @ 3.30GHz
RAM: 8GB DDR3
Graphics: NVidia GeForce GT 440, Driver 347.52, DirectX Runtime 11, NVidia Control Panel 8.1.760.0
GIMP Version: 2.8.14
Comment 1 Michael Schumacher 2015-05-11 19:37:28 UTC
Bug 736411, maybe?
Comment 2 Michael Schumacher 2015-07-16 14:39:34 UTC
Let us assume it is that.Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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