too many entries in journalctl

Asked by Rosika Schreck

Info: version 0.4 using in Linux/Lubuntu 18.04 LTS, 64 bit

Looking through my system-logs in journalctl I noticed that indicator-multiload writes a huge amount of data into it.
Per second 4 entries!
Like so: [...] indicator-appli[1947]: Application already exists, re-requesting properties.

Is there a way of stopping this behaviour? My log-file is becoming overcrowded.

Thanks in advance and greetings.
Rosika

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu indicator-application Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Rosika Schreck (rosika) said :
#2

Hello,

my problem still persists.
Yet I cannot add additional information.

Thanks

Am 10.10.19 um 12:09 schrieb Launchpad Janitor:
> Your question #684207 on System Load Indicator changed:
> https://answers.launchpad.net/indicator-multiload/+question/684207
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

This seems to have the same cause as bug #1798333 but then this should not be reported against the project "System Load Indicator", but for Ubuntu's "indicator-application" package.

Revision history for this message
Rosika Schreck (rosika) said :
#4

Hi Manfred,

thanks a lot for pointing this out.

I´ve just created a new entry on https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1798333 .

Greetings.
Rosika

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

You should click the pencil icon besides "This bug affects 1 person. Does this bug affect you?" in the bug report to document that you are affected by this bug. This will automatically set the bug's status from "new" to "confirmed".

Can you help with this problem?

Provide an answer of your own, or ask Rosika Schreck for more information if necessary.

To post a message you must log in.