Although my implementation is not fully complete, I have decided to share
my progress: https://github.com/v6ak/qubes-i3status-dir
It is available under a WTFPL-like license.
Regards,
Vít Šesták 'v6ak'
On Monday, January 18, 2021 at 2:39:09 PM UTC+1 Vít Šesták wrote:
> BTW, I've started the
BTW, I've started the reimplementation of qubes-i3status as a Python
wrapper around i3status. I am trying to be quite conservative – in the
default settings, there should be no visible difference except CPU load,
periodic freezes and bug fixes (battery status).
* Some indicators (battery, load
Hi Vit,
* I have many VMs in my computer.
* I use i3 with qubes-i3status
* The script qubes-i3status calls command qvm-ls --no-spinner --raw-data
--fields NAME,FLAGS quite frequently.
* The command qvm-ls --no-spinner --raw-data --fields NAME,FLAGS seems to
cause high CPU load. Unfortunately,
OK, reported, some optimization attempts included:
https://groups.google.com/g/qubes-users/c/uTi3QHuhdy8
Also, I have some temptation to reimplement qubes-i3status as a Python
wrapper around the original i3status. We would probably also resolve some
other problems. For example, I had to fix
This is some really nice tracing work. I'm sure it would be appreciated
as an issue in the qubes-issues repository so it can be tracked properly.
While I haven't gone to the same depth, I can confirm that `qubesd`
jumps to ~25% CPU regularly on my (albeit much beefier) system with i3.
This does
Hi,
I have some further info. I partially know cause and have a workaround.
There is my investigation. Some minor inaccuracies might be caused by
retrospective writing:
1. I have tried to debug using strace. (Prerequisite: sudo
qubes-dom0-install strace) After finding pid of qubesd, I ran:
