GIMP Version: 2.8.4
Operating System: Windows
OS Version: Windows 8 32bit
GIMP Experience: Basic Level
I have a Motion Computing LE1700 tablet PC with Wacom Digitizer running Windows 8. This problem happens with every version of the Wacom driver that works on Windows 8 - 7.0.9-5, 7.1.0-8, and 7.1.0-9.
When making a stroke, the brush circle will sometimes get "stuck" at the end of the stroke - it wont follow the arrow cursor under my pen like it normally does. The cursor and the tools on the left side will start rapidly switching between whatever tools were last selected via the "Core Pointer" device and the "Wacom" input device (even if the core pointer - the mouse - is physically disconnected). If I try to draw another stroke, it usually just makes a dot and will continue to do this for every stroke I attempt to make. The issue seems random and doesn't happen all the time, but often enough to be irritating. If I move the cursor anywhere outside of the GIMP window or even just to the status bar at the bottom, the problem will be resolved - the tools will stop freaking out and the next stroke will be fine. It's almost like after a random stroke GIMP starts to think the pen is both the core pointer AND the wacom input device, and gets confused. I found no way to disable the core input device which is pretty much the only thing I can imagine fixing this.
The BIG problem here? Any of those "dots" that end up getting drawn instead of the intended stroke do not appear on the undo history. CTRL+Z will undo the last correctly working stroke, so the dots are basically permanent unless I use the eraser tool to erase them, which isn't always an option.
Is there any way to fix this? I've tried re-installing gimp and using all versions from 2.8.0 to 2.8.4 with the same problem. I tried disabling the eraser, and changing all the pen and touch settings in windows such as disabling right click to hold. Nothing seems to fix this problem

I couldn't find anyone else reporting this as a problem either. I even tried re-installing windows 8 but the problem persists.