REGRESSION: Pommed does not see brightness-up/down key events when on an X11 VT

Bug #257377 reported by Alexander Jones on 2008-08-12
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pommed (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: pommed

MacBook Pro 3.1

Pommed uses linux/input.h, while g-p-m (which works) uses X keyboard stuff. When on an X11 VT, the key events do not pass to Pommed.

WORKAROUND: switch to a non-X VT (Ctrl+Alt+F1..6) in order to change brightness, then switch back (Alt+F7).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: ath_hal
Package: pommed 1.20~dfsg-1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/.local/bin
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pommed
Uname: Linux 2.6.26-5-generic x86_64

Alexander Jones (alex-weej) wrote :
Luke Yelavich (themuso) wrote :

I suspect this has something to do with the xorg input hotplug being enabled about a week prior to the reporting of this bug. I think those who have access to the hardware need to run hal with debug outout, but I don't know enough about hal to be sure as to whether thats the best approach.

description: updated

Why do you keep adding the "potential" tag? This *is* a regression,
there is no "potential" about it!

The name of the leds device has changed again; it it now called /sys/class/leds:smc::kbd_backlight/brightness.

I am attaching a possible patch, hoping the maintainer keeps an eye on these bugs :-)

description: updated
Alexander Jones (alex-weej) wrote :

Hi Rydberg. I've updated the description and title to more clearly describe this bug. Please attach your patch to a more relevant bug.

Well done with the patch, though. I think that needs fixing in HAL, too.

WillSmith (undertakingyou) wrote :

I to am having this behaviour. If I use the fn1 and fn2 keys in a non X VT then they work, but when in an X VT they will not work. This behaviour is also shown with the fn8-10 keys.

uname -a output: Linux will-laptop 2.6.27-7-generic #1 SMP Tue Oct 14 18:40:44 UTC 2008 i686 GNU/Linux

pommed -v output: pommed v1.21 ($Rev: 494 $) Apple laptops hotkeys handler

lsmod | grep applesmc output:applesmc 28208 0
led_class 12164 1 applesmc
input_polldev 11912 1 applesmc

This done while running 8.10 Beta i386 edition

WillSmith (undertakingyou) wrote :

I just compiled pommed from source and the same issue is exhibited.
:(

Ahh so, after spending weeks,months,years.... trying to figure this out
it ended up being a simple fix:(remember once hotplugging is disable, you need xorg.conf).

Section "ServerFlags"
     Option "AutoAddDevices" "False"
EndSection

the cause is the removal of evdev:

cat /var/log/Xorg.0.log
(II) config/hal: Adding input device applesmc
(**) applesmc: always reports core events
(**) applesmc: Device: "/dev/input/event8"
(II) applesmc: Found x and y absolute axes
(WW) applesmc: Don't know how to use device
(II) UnloadModule: "evdev" <----ignoreABI seemed to not work for me
(EE) PreInit returned NULL for "applesmc"
(EE) config/hal: NewInputDeviceRequest failed

Now to see how to have hotplugging and Xorg know what to do with applesmc:
maybe some kind of eye candy mechanism!!

Víctor Jiménez (capitangolo) wrote :

Wow, I confirm it works here.

Thanks jmattock78!

Cool,
Now the question is, is how to do this while having hotplug
enabled?
This way we can take advantage of the new features, as well as find a workaround until applesmc
is fully workable in xorg, in some way or another.
The option ignoreABI changes errors into warnings, but doesn't seem to be directed
to evdev. I think the first thing is to locate the xorg.conf commands
then go from there.

regards;

Steve Beattie (sbeattie) wrote :

This bug was reported in the Intrepid development cycle; removing regression-potential tag and marking as regression-release.

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

Other bug subscribers