ffalarms 0.2.2 mainly fixes "ffalarms does not start on SHR unstable"

Łukasz Pankowski lukpank at o2.pl
Fri May 22 01:24:00 CEST 2009

If ffalarms does not start for you displaying exception:

ValueError: Ecore_Evas_Engine_Type changed and bindings are now invalid, position 180 is now NULL!

Then ffalarms 0.2.2 is a fix for that get it from:
(only Python 2.6 version).

- fix ffalarms not starting due to ecore.evas.engines_get raising
  ValueError instead of returning True (incompatibility between
  python-ecore and ecore; thanks to skamster for reporting)

- add -E, --engine=x11|x11-16 option

- check also for software_16_x11 (new name) apart from software_x11_16
  (old name)

- fix typo in "Scheduled alarms:" on main screen (thanks to Marcel)

More information about the community mailing list