I just had a think about this, and if this really is just caused by HAL relaying a signal from the same /dev/input/eventX device that the X server already grabbed, then perhaps a slightly longer-term solution would be a hal-info rule to stop hald-addon-input from monitoring evdev devices (or any device with a 'input.x11_driver' property, if possible), which we know will be grabbed by Xorg anyway? The reason is that this problem could easily affect other hotkeys, eg brightness.
As an example, on my desktop the power button isn't grabbed by Xorg, and has no input.x11_driver property in HAL so I want HAL to relay signals from this device (which it does). But I don't want HAL to relay signals from any hotkeys on my keyboard, which have a input.x11_driver property. What do you think? Could you think of any issues with doing something like that? -- notification daemon shows two popups for fn-f3 event https://bugs.launchpad.net/bugs/314547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
