01-21-2023, 08:22 AM
I don't know what a SWEEP program is in computing terms, but as you mention attack, I guess you are referencing anti-malware.
Linux has a small range of anti-malware compared with Windows or MAC OS.
For regular use integrated into the OS search for 'clamav' which seems to be the standard for Linux
For making a one off disk to boot your machine from and then scan the whole disk system you could try something like Avira Rescue System which claims to work on Linux disks.
I've not used either.
It still seems the problem is likely hardware.
If you can physically change the keyboard, that would be my first thing to do. I don't know your model, but dismantling and cleaning may be possible.
Otherwise, there is a utility called 'xev' which is for debugging mouse and keyboard input.
Open a terminal by pressing 'ctrl' 'alt' and 't' together and then type
followed by return.
This should open a small 'Event Tester' window.
While the Event Tester window is selected the terminal window will report mouse and keyboard activity.
So, if you operate the mouse within the Event Tester window, the terminal will report all the happenings.
Similarly, operating any key on the keyboard should report two actions in the terminal, one for press and one for release.
To test
Ensure the Event Tester window is selected, then keep the mouse pointer well away from the window.
Press a few keys to see how the terminal reports them. You should see two events logged each time you press and release a key.
Make a note of the timestamp of the last actual press/release.
Then leave the system alone to monitor for any spurious '3' events. You may want to disable screensaver to avoid confusion.
If xev shows '3' occurring randomly, it would suggest that the keyboard is generating them. See if tapping gently near the '3' keys changes things.
To end the xev session, select the terminal window and press 'ctrl' and 'c'
Linux has a small range of anti-malware compared with Windows or MAC OS.
For regular use integrated into the OS search for 'clamav' which seems to be the standard for Linux
For making a one off disk to boot your machine from and then scan the whole disk system you could try something like Avira Rescue System which claims to work on Linux disks.
I've not used either.
It still seems the problem is likely hardware.
If you can physically change the keyboard, that would be my first thing to do. I don't know your model, but dismantling and cleaning may be possible.
Otherwise, there is a utility called 'xev' which is for debugging mouse and keyboard input.
Open a terminal by pressing 'ctrl' 'alt' and 't' together and then type
Code:
xevThis should open a small 'Event Tester' window.
While the Event Tester window is selected the terminal window will report mouse and keyboard activity.
So, if you operate the mouse within the Event Tester window, the terminal will report all the happenings.
Similarly, operating any key on the keyboard should report two actions in the terminal, one for press and one for release.
To test
Ensure the Event Tester window is selected, then keep the mouse pointer well away from the window.
Press a few keys to see how the terminal reports them. You should see two events logged each time you press and release a key.
Make a note of the timestamp of the last actual press/release.
Then leave the system alone to monitor for any spurious '3' events. You may want to disable screensaver to avoid confusion.
If xev shows '3' occurring randomly, it would suggest that the keyboard is generating them. See if tapping gently near the '3' keys changes things.
To end the xev session, select the terminal window and press 'ctrl' and 'c'
stevef
clueless
clueless