Bug 445095 - can change backlight with sony vaio vgn-sz61wn
Summary: can change backlight with sony vaio vgn-sz61wn
Status: RESOLVED DUPLICATE of bug 456713
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Beta 5
Hardware: PC SUSE Other
: P3 - Medium : Enhancement (vote)
Target Milestone: ---
Assignee: Lubos Lunak
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-14 13:40 UTC by Balint Nafradi
Modified: 2008-12-12 15:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Balint Nafradi 2008-11-14 13:40:54 UTC 
The Fn+(F5;F6) combination dos'nt work.
after 
xrandr --output LVDS --set BACKLIGHT_CONTROL native
the 
xbacklight -set n command works but not the Fn+(F5;F6) combination.
Comment 1 Timo Hoenig 2008-11-16 14:20:44 UTC 
Balint, can you please post the output of

$ lshal -m 

when pressing the brightness keys?

Also:  Do you use GNOME or KDE?
Comment 2 Balint Nafradi 2008-11-17 12:29:53 UTC 
(In reply to comment #1 from Timo Hoenig)
> Balint, can you please post the output of
> 
> $ lshal -m 
> 
> when pressing the brightness keys?
> 
> Also:  Do you use GNOME or KDE?
> 

I'm using KDE

the output of lshal-l:
Fn+F5:
^@13:28:13.612: computer_logicaldev_input_0 condition ButtonPressed = brightness-down

Fn+F6:
13:28:29.402: computer_logicaldev_input_0 condition ButtonPressed = brightness-up
^@

Fn+F5 again:
13:28:55.758: computer_logicaldev_input_0 condition ButtonPressed = brightness-down
^@

Fn+F6 again:
13:29:25.511: computer_logicaldev_input_0 condition ButtonPressed = brightness-up
^@
Comment 3 Timo Hoenig 2008-11-17 12:31:51 UTC 
Ah, alright, so this is an KDE issue.  Reassigning.
Comment 4 Lubos Lunak 2008-12-12 15:12:11 UTC 

*** This bug has been marked as a duplicate of bug 456713 ***