Lose mouse control after switching to Antix 15 via KVM

[duane]

I have 3 computers sitting around my desk and on the one that is running Antix 15 frequently when I switch back to it after using one of the other computers, I lose all control of the mouse. It jumps around the screen opening stuff that I don't want to.
The only solution is to shut it down by holding down the power button.
Once I reboot it says something about recovering an orphaned inode several times but boots up OK otherwise.
I am typing from it right now.
I know that this old junk PC doesn't have the best hard drive in the world. I remember getting a warning about it when I did the installation.
How much of this should I attribute to KVM VS the hard drive.
I wonder how they are interacting to cause this problem?

I should probably get rid of this computer anyway. It is just an old Dell Dimension 4600 that I use for a test box and do minor work on.
Duane

[uncle mark]

How much of this should I attribute to KVM VS the hard drive.

I'd guess 98% KVM, but the only way to know for sure would be to isolate it.

The mouse itself could be the culprit as well.

EDIT: One other thing, which is kind of off the wall but possibly related...

The antiX-15 full 64 bit I loaded up several days ago (and then added KDE) had this irritating (to me) "feature" where the mouse pointer disappeared when not in use.

Mr. Google had some hits attributing that behavior to the 'unclutter' package, which was installed. Uninstalled and that fixed my issue. As far as your issue is concerned, perhaps something weird is going on with your system and that package.

[duane]

Thanks for you input.
Gotta run some errands.
Will look into it more later.

[duane]

I got an idea. When I bought this KVM there was an optional power supply for it.
I ordered it even though it was expensive for a power supply.
Most of the time I use it when am using the KVM. This time I had not been using it.
So I plugged it in and the switch from one computer to the other seems to be crisper with the power supply connected and it has not had a mouse error since.
That may be the solution. Time will tell.

[m_pav]

Generally, if a KVM has a power supply option, you should use it. I am with Uncle Mark, KVM's are too often the culprit in Human Input Device errors.

As for the hard disk, I would doubt it was causing the issue, but I'd place very little trust in it if you got a warning. I decommission drives as soon as they develop their first fault. If you see a single splice error, that's the hard disk and you're already on your way to losing data.

[uncle mark]

...KVM's are too often the culprit in Human Input Device errors.

Not counting the human input, of course.

[m_pav]

We could always make it AI, ( Alien Input ) :)