© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Ok, here's the output of me using the keys them selves:
Even thought it seams like things are working only like 1/5 (if that) of the key presses are reported in these "logs". And they usually only "click" when it's already full bright, or min bright.
As I mentioned all of this worked just fine in dapper.
dem@mlap:~$ lshal -m
Start monitoring devicelist:
-------
computer_
computer_
computer_
computer_
computer_
computer_
computer_
computer_
computer_
computer_
dem@mlap:~$ dbus-monitor --system
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-down"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-down"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-down"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-down"
signal sender=:1.2 -> dest=(null destination) path=/org/
object path "/org/freedeskt
int32 83
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"
signal sender=:1.0 -> dest=(null destination) path=/org/
string "ButtonPressed"
string "brightness-up"