Comment 4 for bug 1636518

Hi Michael,

thank you for your answer.

As you suggested, I checked the folder where you said the icons are
written to. First of all, there are 3 folders with different <random>
values at /var/run/user/<uid>/multiload-icons-<random>/ (is that normal
?) In one of these folders/icon, indicator-multiload-graphs-0.png and
1.png get updated every second even though right now the unity panel
shows the no-icon icon. In the other two folders, the .png files'
modified times are from yesterday.

When I start the indicator from command line, I do not get any error
messages -- actually no messages at all, until I Ctrl+x. I have also
noticed that once I started the indicator from command line and the
indicator one the unity panel works fine now, the folder which used to
be updated fine (even though the indicator was not showing anything
useful on unity panel) is deleted and a new folder with different random
value was created, which now is updated and the updated png files are
seen on the unity panel.

Perhaps, after screen lock or suspend, the indicator is trying to access
an incorrect folder ?

Thanks for your time.
-fatih

On 10/25/2016 05:51 PM, Michael Hofmann wrote:
> Hi fk,
>
> this is weird. The icons are written to /var/run/user/<uid>/multiload-
> icons-<random>/icons, could you check whether they are still updated
> after suspend? When you start the indicator from the command line
> (indicator-multiload), do you see any error messages?
>
> Cheers
> Michael
>