
BUGS
====

- debian run-parts -
There is a small problem with the debian run-parts program used for the
script system. Usually pbbuttonsd set a timeout for the PMCS script to
run. If this timeout was exceeded pbbuttonsd would terminate the script
and ideally all its childs. But this will only work if all child
processes share the same process group. Unfortunately the program
run-parts creates a new process group for each running child script so
that pbbuttonsd can't terminate this scripts.

Pbbuttonsd will work as usual after a script error but the faulty script
might remain in memory. To be save run-parts needs to be patched. Remove
the function call setsid() from the source (There is only one) and
recompile. A bug-report was sent to debian.

This problem will only occour if your script don't work correctly. Check
pbbuttonsd lock file if some of your scripts have been killed by the
server and in this case check those scripts for errors.

- framebuffer with no backlight controller support -
If the framebuffer didn't support the LCD backlight, reading the current
brightness level would result in an error. This error switch pbbuttonsd
in a special emergency mode and it tries to sustain basic support and
inform all clients that LCD brightness is not available. Nevertheless
pbbuttonsd could be configured to switch of the framebuffer display but
the result might not as expected. Depending on how good the framebuffer
driver controlls the LCD backlight this basic support may show some
strange side effects. This could be a sleeping machine with still
illuminated LCD showing nice color patterns or the backlight won't be
switched off at all (also it seems so and the display is dark). Sometimes
it helps calling 'pbbcmd config lcdbacklight 0' before triggering sleep
but there is no guarantee.

The behaviour wouldn't change if the kernel was configured not
to support the LCD backlight. 

I have no solution for this problems other than to fix the
framebuffer driver that it supports the LCD backlight and provides a
backlight controller.

If you have such a machine where the LCD and mostly suspend-to-RAM also
is not well supported, configure pbbuttonsd carefully and don't expect
any behaviour for sure. Check it carefully and if in doubt, disable the
feature. Don't use 'suspend-to-RAM' and 'blank screen' in this case.
                           --- Be warned ---

- since pbbuttons have been ported to glib, memory failures will cause
  immediate program termination without a chance to clean up properly.
  
- Failing to install one or more sighandlers is only worth a warning
  rather than an error message. I think this won't be a problem at all
  because sigaction() has no real reason to fail.
  
---

If you find other bugs or problems regarding pbbuttons, please email me.

