indicator-multiload shows a no-icon icon after a screen lock or suspend in 16.10

Bug #1636518 reported by fk
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
System Load Indicator
New
Undecided
Unassigned

Bug Description

After a screen-lock or suspend, the icon on the unity panel for indicator-multiload turns into a no-icon icon and does not show any information anymore. If clicked on the icon, everything seems to be working fine on the opening menu. Quitting the indicator and launching it again solves the problem. (This is on version 0.4 from the official repos.)

Revision history for this message
fk (kamisli) wrote :
Revision history for this message
Michael Hofmann (mh21) 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

Revision history for this message
fk (kamisli) wrote : Re: [Bug 1636518] Re: indicator-multiload shows a no-icon icon after a screen lock or suspend in 16.10

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
>

Revision history for this message
fk (kamisli) wrote :

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

Revision history for this message
fk (kamisli) wrote :

Anyone ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.