Package Details: pommed-light 1.51lw-2

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

Dependencies (6)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

srl commented on 2013-05-27 14:16

@rekoil: I'm bytbox on #archlinux

rekoil commented on 2013-05-27 14:15

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

srl commented on 2013-05-27 13:01

@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

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

@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

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

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

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

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

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?