** Changed in: gnome-settings-daemon
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage no
** Changed in: gnome-settings-daemon
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage notifi
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage
This patch is in 3.9-rc1, so it won't be available for ubuntu
precise/quantal/raring kernel
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
No good result while discussing with gnome-settings-daemon maintainer, so
asus-wmi driver will report the key events anyway.
This will lead to another problem that the brightness will be adjusted twice by
a single key stroke.
This patch is still in platform-x86 maintainer's tree, and will be merg
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage notifica
** Changed in: gnome-settings-daemon
Status: New => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage notifica
** Changed in: gnome-settings-daemon
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage notif
gouri, yes, that's the exactly the same problem you encountered.
Sorry, we don't have any progress for this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does no
Hi, I'm wondering if the bug I'm experiencing (bug 1042359 ) is linked
to this one.
What are the effects, observable by the user, of the bug being discussed
here ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
There is another bug which seems to be very similar
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/257827
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not
There is a patch provided by Gary Ching-Pang Lin.
https://bugzilla.gnome.org/show_bug.cgi?id=672380#c7
I made Debian packages for amd64 on http://people.canonical.com/~sylee/959106/.
Does anyone want to try this package to see how it works?
--
You received this bug notification because you are a
** Changed in: gnome-settings-daemon
Status: Unknown => Incomplete
** Changed in: gnome-settings-daemon
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Ti
I agree, if the brightness keys are hardwired, then it sounds better to
just let the notification popups not work than doing brightness changes
twice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9591
Subscribing Martin to ensure he sees the comments being made here.
Martin, can you respond to the comments made here and on the upstream
bug? Among the kernel devs there seems to be a consensus that the kernel
*should not* be sending key events in situations like this.
--
You received this bug n
** Also affects: linux via
https://bugzilla.gnome.org/show_bug.cgi?id=672380
Importance: Unknown
Status: Unknown
** Project changed: linux => gnome-settings-daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Seth,
No, asus-wmi driver doesn't send out the key event, since it changed the
brightness already.
If the driver send out the key event, g-s-d will changes the brightness again,
it's not we want.
So, it only send out the uevent to notify the g-s-d that brightness is changed,
please read the act
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver does not emit brightness key events
To manage notificati
So the bug is that the brightness changes but the notifier isn't
displayed?
If the driver sends the key event, then isn't g-s-d going to change the
brightness again? I think this is why the driver behaves this way. It's
providing information to userspace to indicate that the brightness has
changed
** Summary changed:
- brightness changing problem in ASUS machines
+ ASUS WMI driver does not emit brightness key events
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
ASUS WMI driver
20 matches
Mail list logo
