fossapup64_9.5 in RAM-only mode
This has not happened before. Every time I press the UP arrow key, the OS takes a full screenshot and opens it instantly in mtpaint.
It is extremely difficult to work with this malfunctioning UP key!
Any ideas?
Moderator: Forum moderators
fossapup64_9.5 in RAM-only mode
This has not happened before. Every time I press the UP arrow key, the OS takes a full screenshot and opens it instantly in mtpaint.
It is extremely difficult to work with this malfunctioning UP key!
Any ideas?
"I awoke only to find that the rest of the world was still asleep.”
Leonardo Da Vinci
Could you hot key assignments have been changed somehow?
Assuming you already checked out the actual keyboard by swapping it out with another, or trying that keyboard on another PC, or OS, you may want to look at the hot key settings.
Go to the Start Menu > Desktop > JWMDesk Manager.
Look near the bottom of the window for the “JWM Hotkey” button.
Check out you Key/Keycode and the “Action” fields.
On mine, the “UP” Key/Keycode is mapped to the “up“ action. The “Print” key is mapped to the “exec:defaultscreenshot” action.
For what it is worth, on my Xenial64 machine, the 111 Keycode is mapped to the “exec:defaultscreenshot” action.
I had the same problem years ago. The Up arrow was producing keycode 111, which was mapped to defaultscreenshot. In a terminal running xev, when the print screen was pressed, it is keycode 107. The JWMDesk hotkey assignment needs to be changed to match the keycode for the print screen key.
When you use xev, it will identify the keycode of pressed keys. Make sure the cursor remains within the pop up window to see the output.
New Laptop - ASUS ZenBook Ryzen 7 5800H Vega 7 iGPU / 16 GB RAM
TerryH wrote: ↑Sun May 19, 2024 1:55 amI had the same problem years ago. The Up arrow was producing keycode 111, which was mapped to defaultscreenshot. In a terminal running xev, when the print screen was pressed, it is keycode 107. The JWMDesk hotkey assignment needs to be changed to match the keycode for the print screen key.
When you use xev, it will identify the keycode of pressed keys. Make sure the cursor remains within the pop up window to see the output.
I remapped 111 to up. It worked!
What a relief. Will this have any other effects?
Thanks.
"I awoke only to find that the rest of the world was still asleep.”
Leonardo Da Vinci
chris_r wrote: ↑Sun May 19, 2024 1:10 amCould you hot key assignments have been changed somehow?
Assuming you already checked out the actual keyboard by swapping it out with another, or trying that keyboard on another PC, or OS, you may want to look at the hot key settings.
Go to the Start Menu > Desktop > JWMDesk Manager.
Look near the bottom of the window for the “JWM Hotkey” button.
Check out you Key/Keycode and the “Action” fields.
On mine, the “UP” Key/Keycode is mapped to the “up“ action. The “Print” key is mapped to the “exec:defaultscreenshot” action.For what it is worth, on my Xenial64 machine, the 111 Keycode is mapped to the “exec:defaultscreenshot” action.
I re-mapped 111 to up, and that worked!
"I awoke only to find that the rest of the world was still asleep.”
Leonardo Da Vinci