** Changed in: gnome-power
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/314547
Title:
notification daemon shows two popups for fn-f
** Changed in: gnome-power
Importance: Unknown => Medium
--
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
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
** Branch linked: lp:ubuntu/gnome-power-manager
--
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
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bug
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 mod
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 de
** Changed in: gnome-power
Status: Unknown => New
--
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
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
de
Chris:
Thanks for helping to root cause this so quickly. It looks like this is
a pretty easy issue to fix for this release, but future gnome power
manager releases are going to have it, so i've filed a bug to see what
upstream can do about it (maybe a compile time switch to ./configure to
disable
This bug was fixed in the package gnome-power-manager - 2.24.0-0ubuntu13
---
gnome-power-manager (2.24.0-0ubuntu13) jaunty; urgency=low
* Drop 79-enable-battery-hotkey.patch. It appears that HAL is now sending
a dbus event for Battery hotkey presses, so gpm doesn't actually nee
It doesn't matter so much for Fn+F10 as that is handled by g-s-d, which
I don't think looks at DBUS signals anyway (I might be wrong though).
Could you also attach the output of "lshal" please?
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You rece
It does for FN-F10 for me, which is ejectcd-close. Probably a few others
too, but that's all i see offhand.
On Thu, Jan 8, 2009 at 11:31, Chris Coulson
wrote:
> Thanks. Yeah, it seems that HAL emits a signal for that key as well,
> which is undesirable. Do you know if you get HAL signals for any
Thanks. Yeah, it seems that HAL emits a signal for that key as well,
which is undesirable. Do you know if you get HAL signals for any other
hotkeys, or is it just the battery key?
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug
Here's the dbus-monitor --system log.
** Attachment added: "log"
http://launchpadlibrarian.net/21013296/log
--
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
Desktop Bugs, which
I wonder if HAL is emitting a signal on this keypress (in addition to
the keypress through the Xserver). Could you please run "dbus-monitor
--system" as you press the key combination and then post the output?
Thanks
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Incomplet
I'll check if this is an upstream issue shortly, unless someone beats me
to it.
--
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
Desktop Bugs, which is subscribed to gnome-power-man
Confirmed - g-p-m is raising the same event twice through 2 separate
code paths, it seems:
TI:14:31:40 TH:0x8b0b640FI:gpm-button.c
FN:gpm_button_filter_x_events,122
- Key 244 mapped to HAL key battery
TI:14:31:40 TH:0x8b0b640FI:gpm-manager.c
FN:button_pressed_cb,1020
- B
whoops, that was actually me, just on the wrong launchpad login :)
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => New
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a memb
Attached is gpm output as asked. I tee'd all the output to this log, so
it includes from when it started and one button press.
** Attachment added: "gpm verbose output"
http://launchpadlibrarian.net/20991530/log
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.n
Thanks. Could you kill gnome-power-manager again and then re-run it with
"gnome-power-manager --verbose --no-daemon", and then post any output as
you press the key combination?
Thanks
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Incomplete
--
notification daemon shows two p
I've killed gnome-power-manager, and without it running, I only see a
single keypress and single keyrelease event for XF86Battery in xev.
That should rule out the kernel and xorg.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => New
--
notification daemon shows two popup
Thanks Mario. The message is actually sent twice, so this is not a
notification-daemon bug. I'll tentatively re-assign it to gnome-power-
manager for now, but it could be g-p-m, libnotify, xorg or the kernel.
Could you kill gnome-power-manager and run xev, to see if you are
experiencing multiple ev
** Attachment added: "log.txt"
http://launchpadlibrarian.net/20986321/log.txt
--
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
Desktop Bugs, which is subscribed to notification-
This could also be a g-p-m or libnotify issue. Would you mind running
"dbus-monitor --session" whilst you press Fn+F3 and then post the
messages that you see?
** Changed in: notification-daemon (Ubuntu)
Status: New => Incomplete
--
notification daemon shows two popups for fn-f3 event
http
** Attachment added: "popups.png"
http://launchpadlibrarian.net/20963123/popups.png
--
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
Desktop Bugs, which is subscribed to notific
23 matches
Mail list logo
