If conky (up to v. 1.8.1) is built with xdamage support (--enable-xdamage, which is set with USE="+X" in Gentoo), then conky in own "normal" window* eats up to 100% of CPU core (together with X process) in non-reparenting WMs (Xmonad, dwm, awesome). Building it without support for Xdamage X11 extension fixes the problem, but current USE set doesn't permit it. Please add IUSE="noxdamage" for users to be capable to use Conky in described way. Patch attached [*] in conkyrc: own_window yes own_window_type normal Reproducible: Always Relevant links Xmonad bug report: http://code.google.com/p/xmonad/issues/detail?id=193#c3 Conky bug report: http://sourceforge.net/tracker/index.php?func=detail&aid=1662692&group_id=143975&atid=757308
Created attachment 249853 [details, diff] Patch against app-admin/conky-1.8.1adding IUSE="noxdamage"
This bug is completely reproducible and well on my «x86» system (mostly stable branch of the portage tree, but x11-wm/awesome-3.4.8 ).
Can you please confirm that using "alignment none" doesn't work? i.e., conky -a none
Yes, `alignment none` doesn't help here. > Can you please confirm that using "alignment none" doesn't work? > > i.e., conky -a none >
I don't think I will add an use flag for this, this would be just a workaround. @Brenden: Is there a way to fix this in conky?
It is not fix as such, but workaround sufficient for me: with `own_window_type desktop` conky window is managed by awesome just as normal one, but doesn't eat CPU like mad.
Seems to be fixed in app-admin/conky-1.10.8-r2
Thanks for the feedback!