Package Details: pommed-light 1.51lw-2

Git Clone URL: (read-only, click to copy)
Package Base: pommed-light
Description: Handles the hotkeys of Apple MacBook (Pro) laptops - lightweight edition
Upstream URL:
Licenses: GPL2
Conflicts: pommed
Submitter: srl
Maintainer: None
Last Packager: crvv
Votes: 15
Popularity: 0.000000
First Submitted: 2012-04-14 09:52 (UTC)
Last Updated: 2018-04-01 11:24 (UTC)

Latest Comments

brentward commented on 2021-02-11 07:00 (UTC)

@tyjak, I had the same error. I was able to resolve it by manually applying a patch referenced here which was to resolve the same error: This is the patch:

Essentially I just changed offending structs to external and I was able to compile the package. From there I just manually followed the install steps in the PKGBUILD.

I will submit my changes to the source. Hopefully we can get it merged and get the package installing again. In the mean time you can pull the up source repo and make the changes to the two files

tyjak commented on 2020-07-26 08:02 (UTC) (edited on 2020-07-26 08:02 (UTC) by tyjak)

Can't install on my macbook air I've got a an error on compilation :

gcc -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now  pommed.o cd_eject.o evdev.o conffile.o audio.o evloop.o power.o beep.o video.o sysfs_backlight.o mactel/x1600_backlight.o mactel/gma950_backlight.o mactel/nv8600mgt_backlight.o mactel/kbd_backlight.o mactel/acpi.o  -pthread -lrt  -lasound  -laudiofile  -lconfuse  -lpci  -lz  -o pommed
/usr/bin/ld : mactel/x1600_backlight.o:(.bss+0x0) : définitions multiples de « lcd_bck_info »; sysfs_backlight.o:(.bss+0x0) : défini pour la première fois ici
/usr/bin/ld : mactel/nv8600mgt_backlight.o:(.bss+0x0) : définitions multiples de « lcd_bck_info »; sysfs_backlight.o:(.bss+0x0) : défini pour la première fois ici
collect2: erreur: ld a retourné le statut de sortie 1
make[1]: *** [<commande interne> : pommed] Erreur 1
make[1] : on quitte le répertoire « /home/david/.cache/yay/pommed-light/src/pommed-light-1.51lw/pommed »
make: *** [Makefile:8 : pommed] Erreur 2
==> ERREUR : Une erreur s’est produite dans build().
erreur lors de la construction : %!s(func() string=0x55c73a31bbb0)

yakshaver commented on 2017-10-20 04:31 (UTC)

This still isn't working for me, so I ended up writing this: It doesn't take care of handling keys, so you'll have to bind it yourself.

yakshaver commented on 2017-10-16 10:10 (UTC)

This at least got pommed to run for me: It seems that the issue is that the new version of confuse does not include sudo ln -s /usr/lib/ /usr/lib/

yakshaver commented on 2017-10-16 09:46 (UTC)

@glowck The fix you mentuioned didn't see to work for me.

joshirio commented on 2017-08-20 08:07 (UTC) (edited on 2017-08-20 08:07 (UTC) by joshirio)

After recent updates it stopped working. If you get the following error on "systemctl status pommed.service": "/usr/bin/pommed: error while loading shared libraries: cannot open shared object" then just rebuild and install pommed-light again and it will work.

temach commented on 2017-06-14 18:10 (UTC)

There is a macro in pommed.h M_VERSION that is hard coded to 1.45lw. So yes, they just forgot to update the version number that is printed. Code is new version.

yakshaver commented on 2017-02-23 04:19 (UTC)

This seems to be installing an old version for me. I'm not really sure how, because it says that it is download v1.50, but when I run the program I get I: pommed v1.45lw Apple laptops hotkeys handler I: Copyright (C) 2006-2011 Julien BLACHE <> I: Configuration file not found, using defaults Maybe someone forgot to update a version number?

srl commented on 2014-03-19 17:28 (UTC)

@dieelt: yes of course. Updated to 1.47lw.

dieelt commented on 2014-03-19 10:33 (UTC)

Would it be possible to tag the latest master and update the package to include the those changes? I notice that support for additional models, including mine :), have been included in the master-branch.

srl commented on 2013-06-03 13:22 (UTC)

@JKAbrams: fixed, thanks.

JKAbrams commented on 2013-06-03 12:46 (UTC)

Needs fixing re /bin /sbin

srl commented on 2013-05-27 14:16 (UTC)

@rekoil: I'm bytbox on #archlinux

rekoil commented on 2013-05-27 14:15 (UTC)

@srl: Are you on any IRC channels at the moment?

srl commented on 2013-05-27 13:01 (UTC)

@rekoil: it should work no matter how quickly your system boots. I don't have an SSD, but I think at least two other users do, so that's likely not the issue. Do your logs indicate that systemd/kernel is still discovering devices after pommed has started and failed? Try changing, in pommed.service, the last line from to (and then reinstall the service with systemctl disable pommed; systemctl enable pommed; or something like that).

rekoil commented on 2013-05-27 11:45 (UTC)

I'll clarify, the SLiM implication came from my feeling that SLiM just works very differently than most login managers. It's probably not that hehe.

rekoil commented on 2013-05-27 11:09 (UTC)

@srl: Do you have a Mac with an SSD? I'm thinking that either my system boots too quickly, or perhaps SLiM is causing the problem? All I know is that Arch is _perfect_ right now except for pommed :( For the record I have a MacBook Air 13.3" (5,2) with a 2.0 GHz Intel i7, 8 Gb of RAM and a 256 Gb Samsung SSD.

rekoil commented on 2013-05-27 11:02 (UTC)

Since I don't know anything about systemd I didn't really know how to solve this properly so my solution so far is to run wait for 10 seconds before pommed... :P

srl commented on 2013-05-07 11:10 (UTC)

Hmmm... that would mean sysfs isn't being mounted yet. I'm really not sure how that could happen; my understanding was that /sys, /proc et al would get mounted before systemd started starting services. Sorry I can't be more of a help.

rekoil commented on 2013-05-07 06:38 (UTC)

I should have mentioned this before, but pommed loads fine after a complete boot. It is only _during_ boot which the problem arises. Which means I can't automate it. Specifying that I want pommed to run with debug information in systemd it says (right after the line about sysfs backlight probe) it is missing a file, presumably this is the backlight not yet being available this early in the boot.

srl commented on 2013-05-06 23:47 (UTC)

lspci output? Also, try commands like ls /sys/class/backlight find -L /sys/class | grep backlight We're looking for the group of files that can be used to get maximum and minimum brightness, and to set the brightness. In all likelihood, it would work to just add a "case MACHINE_MACBOOKAIR_5:" line at sysfs_backlight.c:431, if you want to be hacky.

rekoil commented on 2013-05-06 23:36 (UTC)

Sorry to bother again, but I am still having a bit of trouble with this package, namely getting it to run at boot. Perhaps I am doing something wrong but I enabled it with systemctl (systemctl enable pommed.service) and my expectation then is that it should load at boot, and it appears to do so, but maybe it's loading too early because it's failing on "sysfs backlight probe", ( and as a result the daemon crashes. Any ideas?

rekoil commented on 2013-05-02 21:06 (UTC)

Brilliant, thanks!

srl commented on 2013-05-02 21:05 (UTC)

Done. (I got my version numbers confused - the new release is 1.45lw.)

srl commented on 2013-05-02 18:08 (UTC)

I actually have to do another point release of pommed today anyway - I'll update to 1.46lw as soon as I'm done.

rekoil commented on 2013-05-02 16:39 (UTC)

Please update to 1.45lw. The new version contains configuration files for MacBookAir5,1 and MacBookAir5,2.

ssmy commented on 2013-02-17 20:40 (UTC)

Backlight control keys are working fine here on Macbook 2,1. All is good.

nostalgix commented on 2012-12-28 14:46 (UTC)

Seems that the backlight-control-keys don't seem to work anymore since the last update.

srl commented on 2012-08-18 02:51 (UTC)

Updated with systemd support, for anyone switching early.