Xfce Forum

Sub domains
 

You are not logged in.

Pages: 1

#1 2024-10-15 20:31:00

mocha
Member
Registered: 2022-12-12
Posts: 23
LinuxFirefox 131.0

Double key press after idle for a while

After upgrading my desktop from Xubuntu 23.10 to 24.04.1 I am getting a double key press from the keyboard after the system has been idling for a while (like on the order of 5 minutes or more).

So the first time I press a key like for example "x", I will get two of that key like "xx", then everything works normal until the next time the system is idle for more than 5 minutes or so.

I had evtest running to check this and it DOES NOT register the double press! How else can I troubleshoot this in XFCE or which bug tracker should I be looking at for other reports of this? Thanks for any suggestions.

Offline

#2 2024-10-16 23:12:18

mocha
Member
Registered: 2022-12-12
Posts: 23
LinuxFirefox 131.0

Re: Double key press after idle for a while

Here is the output of "$xev -event keyboard" after letting it go idle for about 5 minutes. There are clearly two key press/release cycles, in this case lowercase "f". The weird thing I see there is the time of the first release and second press are the same. So it's like it gets a "press" command when the key is lifted.


KeyPress event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182094653, (69,-14), root:(921,429),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XmbLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182094904, (69,-14), root:(921,429),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182094904, (69,-14), root:(921,429),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XmbLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182094907, (69,-14), root:(921,429),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

A "normal" press/release of lowercase "f" looks like this:

KeyPress event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182191081, (173,166), root:(1025,609),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XmbLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0xa400001,
    root 0x1e4, subw 0x0, time 1182191179, (173,166), root:(1025,609),
    state 0x10, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

Offline

#3 2024-10-17 01:13:36

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,481
LinuxFirefox 131.0

Re: Double key press after idle for a while

Have you tried another keyboard?

Are you using some power management tool like powertop or TLP?

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#4 2024-10-17 07:47:00

mocha
Member
Registered: 2022-12-12
Posts: 23
LinuxFirefox 131.0

Re: Double key press after idle for a while

I got another Logitech Wireless USB keyboard and mouse and tested it on this desktop. It works OK!

Then I put the double typing keyboard and mouse on a different computer, and it doesn't double type on that computer....

I was thinking, does Linux or some window managers or DEs store some keyboard cache or settings somewhere under your home? It must be something like that, like some bad cached settings for this keyboard.

Offline

#5 2024-10-17 13:48:34

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,481
LinuxFirefox 131.0

Re: Double key press after idle for a while

mocha wrote:

I was thinking, does Linux or some window managers or DEs store some keyboard cache or settings somewhere under your home? It must be something like that, like some bad cached settings for this keyboard.

Not that I am aware of. Perhaps there was something in the firmware of the keyboard that was interfering. If you put the original keyboard back on the original computer, does the double-typing return?

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#6 2024-10-17 20:49:23

mocha
Member
Registered: 2022-12-12
Posts: 23
LinuxFirefox 131.0

Re: Double key press after idle for a while

To answer your question, yes, the double typing does occur when I reconnect this original keyboard back on the desktop! I've tried many things such as changing batteries, unpairing/re-pairing it to the dongle, off/on reset cycles, etc. It always goes back to having this double letter behavior only on my main desktop. I even tried a full shutdown power off/on sequence of the computer. This is a real mystery. I guess the only solution is a new keyboard/mouse.

Offline

#7 2024-10-17 22:25:19

eriefisher
Member
From: ON, Canada
Registered: 2008-10-25
Posts: 527
LinuxFirefox 131.0

Re: Double key press after idle for a while

I'm not sure what *buntu uses but if it is libinput then it has it's own set of tools built in for settings and debugging input devices. If you don't use libinput then it might be a good time to start.

https://wiki.archlinux.org/title/Libinput

Siduction
Debian Sid
Xfce 4.18

Offline

#8 2024-10-18 00:07:01

mocha
Member
Registered: 2022-12-12
Posts: 23
LinuxFirefox 131.0

Re: Double key press after idle for a while

Thanks for that info. I was trying to find something like this to hopefully get further with this problem.

Here's what I get from some of the diagnostics. It's interesting that the K520 is listed twice. I also tried my other wireless mouse/keyboard and they also show the keyboard listed twice.

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Sony Interactive Entertainment DualSense Wireless Controller Touchpad	id=11	[slave  pointer  (2)]
⎜   ↳ Logitech M510                           	id=9	[slave  pointer  (2)]
⎜   ↳ Logitech K520                           	id=10	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Logitech K520                           	id=12	[slave  keyboard (3)]

Here's the further details for the two K520 devices. I'm not sure what to make of this. I connected my good wireless keyboard/mouse and get some different outputs since it's a different model, but still I'm not sure what to do with this info.

$ xinput list-props 10
Device 'Logitech K520':
	Device Enabled (156):	1
	Coordinate Transformation Matrix (158):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (284):	0
	libinput Natural Scrolling Enabled Default (285):	0
	libinput Rotation Angle (267):	0.000000
	libinput Rotation Angle Default (268):	0.000000
	libinput Send Events Modes Available (269):	1, 0
	libinput Send Events Mode Enabled (270):	0, 0
	libinput Send Events Mode Enabled Default (271):	0, 0
	Device Node (272):	"/dev/input/event7"
	Device Product ID (273):	1133, 8209
	libinput Drag Lock Buttons (286):	<no items>
	libinput Horizontal Scroll Enabled (287):	1
	libinput High Resolution Wheel Scroll Enabled (288):	1
$ xinput list-props 12
Device 'Logitech K520':
	Device Enabled (156):	1
	Coordinate Transformation Matrix (158):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Rotation Angle (267):	0.000000
	libinput Rotation Angle Default (268):	0.000000
	libinput Send Events Modes Available (269):	1, 0
	libinput Send Events Mode Enabled (270):	0, 0
	libinput Send Events Mode Enabled Default (271):	0, 0
	Device Node (272):	"/dev/input/event7"
	Device Product ID (273):	1133, 8209

Added later 02 min 45 s:
Here's the xinput diagnostics from my "good" keyboard/mouse:

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Sony Interactive Entertainment DualSense Wireless Controller Touchpad	id=11	[slave  pointer  (2)]
⎜   ↳ Logitech Wireless Mouse                 	id=9	[slave  pointer  (2)]
⎜   ↳ Logitech Wireless Keyboard PID:4023     	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Logitech Wireless Mouse                 	id=10	[slave  keyboard (3)]
    ↳ Logitech Wireless Keyboard PID:4023     	id=13	[slave  keyboard (3)]
$ xinput list-props 12
Device 'Logitech Wireless Keyboard PID:4023':
	Device Enabled (156):	1
	Coordinate Transformation Matrix (158):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (284):	0
	libinput Natural Scrolling Enabled Default (285):	0
	libinput Rotation Angle (267):	0.000000
	libinput Rotation Angle Default (268):	0.000000
	libinput Send Events Modes Available (269):	1, 0
	libinput Send Events Mode Enabled (270):	0, 0
	libinput Send Events Mode Enabled Default (271):	0, 0
	Device Node (272):	"/dev/input/event6"
	Device Product ID (273):	1133, 16419
	libinput Drag Lock Buttons (286):	<no items>
	libinput Horizontal Scroll Enabled (287):	1
	libinput High Resolution Wheel Scroll Enabled (288):	1
$ xinput list-props 13
Device 'Logitech Wireless Keyboard PID:4023':
	Device Enabled (156):	1
	Coordinate Transformation Matrix (158):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Rotation Angle (267):	0.000000
	libinput Rotation Angle Default (268):	0.000000
	libinput Send Events Modes Available (269):	1, 0
	libinput Send Events Mode Enabled (270):	0, 0
	libinput Send Events Mode Enabled Default (271):	0, 0
	Device Node (272):	"/dev/input/event6"
	Device Product ID (273):	1133, 16419

Added later 18 h 54 min 49 s:
I was able to bandaid this problem by increasing the keyboard auto repeat delay from 250 up to 300. Very strange, this makes no sense. Using the libinput diagnostics I was not seeing any indication of the double press which got me thinking that it wasn't a double press but rather a key repeat! I cannot explain why this keyboard is suddenly sensitive to making a key repeat at 250 vs 300 after many years. I suspect something very low level was changed in going from Xubuntu 23.10 to 24.04 which is ultimately the root cause for this weirdness.

Offline

Pages: 1

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.011 seconds, 7 queries executed - Memory usage: 589.01 KiB (Peak: 605.85 KiB) ]