You have been subscribed to a public bug:
The brightness keys don't work on my msi X340 on Maverick Meerkat after
a clean install, although the multimedia keys (volume, etc ...) work
well.
In order to solve this problem, I modified /etc/rc.local this way:
#########/etc/rc.local#########
#! /bin/bash
setkeycodes e077 130 &
setkeycodes e078 131 &
exit 0
#########/etc/rc.local#########
Then, I created ~/.xmodmap.conf :
##########~/.xmodmap.conf########
keycode 138 = XF86MonBrightnessDown NoSymbol XF86MonBrightnessDown
keycode 139 = XF86MonBrightnessUp NoSymbol XF86MonBrightnessUp
##########~/.xmodmap.conf########
At the next startup, gnome asked me if I wanted to use .xmodmap.conf. I
answered "Yes". But, gnome-power-manager still didn't take into acount
the brightness keys.
Eventually, I wrote the following script and added it to gnome-session-
properties after deactivating the original line concerning gnome-power-
manager.
#########~/.sleep-gnome-power-manager.sh#########
#! /bin/bash
sleep 3
gnome-power-manager &
#########~/.sleep-gnome-power-manager.sh#########
And this solved my problem.
As I don't know whick specific package is concerned by this bug, i filed
it as a gnome-session bug.
Thanks for reading this ! :)
** Affects: xserver-xorg-input-keyboard (Ubuntu)
Importance: Undecided
Status: New
--
Title: Problem with msi X340 brightness keys on Maverick
https://bugs.launchpad.net/bugs/645612
You received this bug notification because you are a member of Ubuntu-X, which
is subscribed to xserver-xorg-input-keyboard in ubuntu.
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
