kinu-garage / hut_10sqft

Computer setup tools for my own environment, and public discussion place holder.
2 stars 1 forks source link

p50: An app first in the window manager's queue taking mouse cursor #689

Closed 130s closed 2 years ago

130s commented 2 years ago

Issue

I started seeing since the end of 2022/06 that a mouse cursor moves occasionally from Emacs to an app that wasn't taking a focus.

Some observation

130s commented 2 years ago

I started noticing this after I moved to the current temporary location.

In reaction to this, I noticed I had a kitchen towel (k/b cover I've been using for 10 years) covering the entire touch pad. Now, I folded it so only the half of the touch pad is (still) covered. Continuing experiment.

130s commented 2 years ago

I started noticing this after I moved to the current temporary location.

In reaction to this, I noticed I had a kitchen towel (k/b cover I've been using for 10 years) covering the entire touch pad. Now, I folded it so only the half of the touch pad is (still) covered. Continuing experiment.

Hypothesis turned to be false; Even without the kitchen paper, the issue still occurs.

130s commented 2 years ago

I can't tell why this keeps happening. It does happen withOUT the following, so these are ruled out (removed FF from the title):

I experimented the following:

130s commented 2 years ago

Happened again.

I saw it happened a few times over at least 55 times I repeated the same phrase.

130s commented 2 years ago

Thought something might touch the touchpad unexpectedly while the mouse cursor is on another app, not on Emacs. While that is a possible scenario, it is unlikely because nothing is touching the touchpanel:

I doubt that this happens when I use an external k/b at home connected to p50. Just more theory: This happens more when I use p50 with its embeded k/b. And now at parents home where I connect an external monitor, the mouse cursor is usually at the external monitor while Emacs in at the embedded monitor so this happens a lot.

And yet, I don't know what is causing this.

130s commented 2 years ago

Not fixed yet though, this is not an issue either if the input is done NOT from the local k/b. I don't plan to work on this.