Hello, one question: Is everyone affected by this bug using indicator-
multiload?
I noticed just now that the frequency of the "pulsing" effect depends
directly on the rate of update of the multiload indicator.
Removing the multiload indicator here on my computer also stopped the
pulsing effect.
@ledoc
Hi Eric, same as you, I later realized that a certain delay was needed
for it to work reliably, since there'd be times when the autostart entry
would get invoked before the datetime indicator. The Exec line on my
.desktop file now reads like this:
Exec=bash -c 'sleep 1m;
Hello, a workaround that I have discovered is to disable framebuffer
objects in the Compiz OpenGL plugin:
gsettings set
org.compiz.opengl:/org/compiz/profiles/unity/plugins/opengl/
framebuffer-object false
Enter that in the terminal and it would take effect immediately; no
logout required. Of
Small update:
> Bill Filler (bfiller) wrote on 2014-09-23:
> I'm assuming evolution-calendar-factory gets loaded by indicator-datetime
> initially such that the indicator can show calendar events.
As a troubleshooting step, I tried disabling the Upstart entry for
indicator-datetime-service so
If anyone is interested in a workaround, here's something that seems to
work on my Ubuntu install.
I noticed that running /usr/lib/evolution/evolution-calendar-factory by
itself manually will cause it to perform some initializations and
terminate after a few seconds. I'm not using any
5 matches
Mail list logo
