Looking into it a bit more, it might be a GTK+ bug, but luckily it's easy enough to just fix it in libindicator.
Looking into it a bit more, it might be a GTK+ bug, but luckily it's easy enough to just fix it in libindicator.