MacBook brightness cannot be changed in KDE (works in GNOME)

Bug #140652 reported by Martin Böhm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
Triaged
Medium
Luka Renko

Bug Description

In a fully updated Kubuntu Gutsy desktop (with both ubuntu-desktop and kubuntu-desktop), the brightness of an Apple MacBook (black, non-pro) laptop display cannot be changed in KDE. However, the brightness can be modified in Ubuntu (GNOME) using the same Function keys.

Tags: macbook
Revision history for this message
Luke12 (luca-venturini) wrote :

There is the same exact bug also on a Dell Inspiron 6400. Function keys for brightness do function in Gnome but not KDE.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

My Dell Inspiron 6400 is working perfectly here, so I have no idea what's wrong with the previous person's laptop.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Out of curiosity though - which video card are you using?

Revision history for this message
Luka Renko (lure) wrote :

Thanks for your report. Can you provide the following data:

1. Exact HW
cat /var/lib/acpi-support/system-product-name

2. Does these two command (if run from Konsole) change brightness properly on your laptop?

dcop `dcop | grep power-manager` power-manager brightnessUp

dcop `dcop | grep power-manager` power-manager brightnessDown

3. Does your laptop return same keycodes from brightness up (212) and down (101) as documented on
https://wiki.ubuntu.com/KubuntuLaptopKeycodes page? If not, what does it report and what does "lshal -m" report when key is pressed?

Changed in kubuntu-meta:
assignee: nobody → lure
status: New → Incomplete
Revision history for this message
Martin Böhm (martin.bohm) wrote :

martin@blackbook:~/processing/miniprojects/desktop-effects-kde$ cat /var/lib/acpi-support/system-product-name
MacBook2,1

dcop calls change brightness just fine.

Key Events:

KeyPress event, serial 32, synthetic NO, window 0x4200001,
    root 0x59, subw 0x0, time 4250875430, (420,433), root:(640,648),
    state 0x0, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 32, synthetic NO, window 0x4200001,
    root 0x59, subw 0x0, time 4250875542, (420,433), root:(640,648),
    state 0x0, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 32, synthetic NO, window 0x4200001,
    root 0x59, subw 0x0, time 4250875910, (420,433), root:(640,648),
    state 0x0, keycode 212 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 32, synthetic NO, window 0x4200001,
    root 0x59, subw 0x0, time 4250875910, (420,433), root:(640,648),
    state 0x0, keycode 212 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Which seems okay.

lshal -m:
23:40:45.265: usb_device_5ac_21b_noserial_if0_logicaldev_input condition ButtonPressed = brightness-down
23:40:45.929: usb_device_5ac_21b_noserial_if0_logicaldev_input condition ButtonPressed = brightness-up

Revision history for this message
Luka Renko (lure) wrote :

Thanks for testing and reporting back. I will mark this bug as duplicate of bug 145337 which has multiple users reporting same problem.

Changed in kdeutils:
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Tommy_CZ (t-kijas) wrote :

I think I have the same problem, brightness etc. works in Unity but not in KDE4.9 (and 4.8.4). What can I do with it?

Revision history for this message
Tommy_CZ (t-kijas) wrote :

I have macbook Air 2012.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.