This seems to be happening when dbus-daemon hogs the CPU, looks like the key down/up events are blocked in a queue somewhere and arrive in a span longer than 2s, making the dialog show up.
This seems to be happening when dbus-daemon hogs the CPU, looks like the key down/up events are blocked in a queue somewhere and arrive in a span longer than 2s, making the dialog show up.