Bugzilla Bug 86566

According to pbbuttonsd has some support for x86 laptops.An variable LAPTOP
needs to be passed to configure to specify the architecture, and some parts of
the /etc/pbbuttons.conf need to be commented out to reflect that
powermanagement isn't supported yet.

Reproducible: Always
Steps to Reproduce:

Which x86 laptop would it work with ? Those kind of things normally vary
between manufacturers...

The only thing pbbuttonsd really handles for x86 is mapping key bindings to
actually do things, like volume management with volume keys.

I'm using it on my dell inspiron 9200 at the moment to do change the volume,
combined with gtkpbbuttonsd (which also seems to work fine on x86) to display
the volume in my xsession. My volume keys aren't hardware based, but have
keycodes associated with them, so using pbbuttons makes sense in my case. If a
laptop has hardware-based volume keys, then it wouldn't be so useful. For
example, my brightness keys are hardwared-based, and don't have keycodes, so I
don't think I'll be able to use pbbuttonsd to manage the brightness.

Created an attachment (id=54401) [edit]
diff of the ebuild i used to build on x86

The method I used to determine the architecture is a bit hackish, so I'm sure
there's a cleaner way of determining it.

the right way to do this is

local myconf

use x86 && myconf="LAPTOP=i386"
use ppc && myconf=LAPTOP=i386"

econf ${myconf}

or something like that
The keywords guarantee that it wont be built on other arches anyway.

Created an attachment (id=54823) [edit]
pbbuttonsd-0.6.7.ebuild

An ebuild for pbbuttonsd which makes use of the suggestion by Oliver for
determining the arch, instead of the messy way I had previously.

alright, marking it ~x86 on behalf of the ghost x86 team