Release v2.1.0

New modules

The new hass_lovelace module uses a specified homeassistant lovelace dashboard to generate a widget. There's some room for improvement, but this provides a much simpler way to "create" a widget since you can do it through home assistant. You can pin a sensor value to the module from the widget.

Module changes

• tray: Added new popover mode as an alternative to the revealer mode.
• clock: Events now use indicators matching the cpu, memory, and disk modules.
• network: Added indicator when using a VPN.
• mpris: Only show handles for sliders on hover.

Removed modules

hass_dashboard has been removed in favor of hass_lovelace, since they effectively do the same thing, but the lovelace module is easier to configure.

Debugging

New IPC commands

Added new ipc commands for tracemalloc and objcount to help diagnose memory leaks.

New script

pybar-memsnap was added to automate analysis of the new ipc commands.

Fixed leaky modules

The Home Assistant and memory modules previously had bad memory leaks causing about a 2MB/min increase. These are now fixed.

Changed respawn logic

The process is now fully reloaded after adding monitors (debounced to 5 seconds). This is the same as clicking on Reload in the context menu.

Added documentation

One of the goals of 2.0 was to not require documentation for normal use, but there are some gaps that can't easily be covered otherwise. Docs have been added for development info and modules that require extra setup.

Downloads

• pybar-arch.zip - Arch Linux build
• pybar-ubuntu.zip - Ubuntu build

Full Changelog: v2.0.0...v2.1.0

Release v2.0.0

Initial Release

Downloads

• pybar-arch.zip - Arch Linux build
• pybar-ubuntu.zip - Ubuntu build

Full Changelog: v0.9.0...v2.0.0

Release v2.0.0-testing

Fixed typo in package name

Release appimage-testing

Added module directories to datas in appimage spec file

Release v0.9.0-1

This is a test release using github actions.

v0.9.0

This is the initial release of pybar that I'm starting at version 0.9.0. It feels appropriate since I consider it mostly feature complete at this point without any major bugs, but there are still a few sharp corners I'd like to smooth out.

The included executable was generated and tested on Arch Linux. There seems to be some wonkyness with how pyinstaller-generated executables work across different systems (mostly related to subprocess and ssl), so I would only recommend using this on Arch. There's also a CI built executable that seems to work better on Ubuntu, but I didn't test it much.