warning "Application already exists, re-requesting properties"

Hi,

I´ve got the same problem here. I´m running Linux/Lubuntu 18.04.3 LTS, 64 bit.
There are way too many entries in journalctl.
The app which causes this is systemload-indicator.

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

Status changed to 'Confirmed' because the bug affects multiple users.

"Is there a way of stopping this behaviour?"

Try to remove/add indicators. I think it solved my issue.

Hello Moshe,
thanks for your reply.

"Try to remove/add indicators."
I tried but it doesn´t seem to work with me. Could you give me an example of how you did it?

I hope that I understand your issue correctly, If I remember, I removed the volume control indicator, added the indicator applet and ticked/unticked the sound menu option. Might be something similar. My idea was that some indicators don't exactly fit the distro. I would try removing your systemload-indicator/indicator-multiload or other indicators.

Hi Moshe and thanks for your reply,

"I would try removing your systemload-indicator/indicator-multiload [...]"
Yes, it´s multiload-indicator which provides the many log-entries.
Whenever it´s running it creates 4 entries per second (in journlactl) like so:

"Sep 23 18:27:07 rosika-Lenovo-H520e indicator-appli[1947]: Application already exists, re-requesting properties.
Sep 23 18:27:07 rosika-Lenovo-H520e indicator-appli[1947]: Application already exists, re-requesting properties.
Sep 23 18:27:07 rosika-Lenovo-H520e indicator-appli[1947]: Application already exists, re-requesting properties.
Sep 23 18:27:07 rosika-Lenovo-H520e indicator-appli[1947]: Application already exists, re-requesting properties.
[...]"

Even if I unclick every single item (cpu, RAM etc.) in the app! So in theory it shouldn´t monitor anything yet it still creates those log-entries.

Seems despite all efforts there´s not much that can be done about it.
If I remove indicator-multiload, like you suggested, I´ve got to replace it with something else, because I need some kind of monitor ;)
Conky comes to mind as it´s light on resources and doesn´t create this kind of log-entries.

Thanks a lot anyway.
Greetings.
Rosika

Hi Rosika.

I came here when I was looking for this problem.
It seems that the problem has not been solved yet.
It seems to be a compatibility issue between indicator-application-service and indicator-multiload.
I decided to suppress the output of syslog and continue to use indicator-multiload although it is not the root solution.

[Create new rsyslog filter]
> sudo leafpad /etc/rsyslog.d/05-filter.conf
# indicator-application-service(indicator-multiload) disable
if $programname startswith'indicator-appli' and $msg contains'Application already exists, re-requesting properties.' then stop

[Check rsyslog syntax]
> sudo rsyslogd -N 1
rsyslogd: version 8.32.0, config validation run (level 1), master config /etc/rsyslog.conf
rsyslogd: End of config validation run.Bye.

[Restart rsyslog]
sudo service rsyslog restart

[Check syslog with tail]
tail -F /var/log/syslog

Hi Takayuki Tokuyoshi (powtok),

thanks a lot for your suggestion.

I reproduced all the steps you provided. I created the 05-filter.conf file with the respective content.

Check rsyslog syntax: Did that as well. It worked as you described.
Restart rsyslog: Did that as a last step.
All worked.

Results:

"tail -F /var/log/syslog" -----------> O.K. That didn´t produce any ongoing output.

BUT:

"sudo journalctl -f" -------------> Alas, no change at all:

example-entry: rosika-Lenovo-H520e indicator-appli[1947]: Application already exists, re-requesting properties.

Still 4 entries per second !!

How is it in your system?
Please try the command "sudo journalctl -f" if possible.
I would be greatly interested to learn if you have those mutiple ongoing output-entries as well.

Cheers.
Rosika