Chris: I think there is a lot of confusion in this model to having HAL sending these events, but it's the eventual correct solution that HAL should send them and they shouldn't have a keysym in X assigned I think. Steve Langasek and I had a short discussion about this on IRC.
The reason this model makes more sense is because then events that should be broadcast to the system will be and events that should be broadcast to specific user's sessions would be. If there are a lot of other problems that crop up like this for Jaunty, I think your hal-info solution will be a good idea, but either way this needs to be revisited at the next UDS. On Fri, Jan 9, 2009 at 10:49, Chris Coulson <[email protected]>wrote: > 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 direct subscriber > of the bug. > -- Mario Limonciello [email protected] -- 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
