Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered

[jimav]

The following message is continuously logged to /var/log/syslog (every few seconds):

Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; resetting instead
Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered

It's hard to find anything in syslog because thousands of these messages intermingle with everything else

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 20 10:28:49 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-12-13 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Those messages appear to be from 'gnome-shell-extension-appindicator' so reassigning there.

[Launchpad Janitor (janitor)]

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

[Simon Arlott (sa.me.uk)]

This code in gnome-shell-extension-appindicator-17.10.3 doesn't make sense, because the "reset" function doesn't do anything:

    _ensureItemRegistered: function(service, bus_name, obj_path) {
        let id = this._getItemId(bus_name, obj_path);

        if (this._items[id]) {
            //delete the old one and add the new indicator
            Util.Logger.warn("Attempting to re-register "+id+"; resetting instead");
            this._items[id].reset();
        }

        this._registerItem(service, bus_name, obj_path)
    },

The result is that _ensureItemRegistered outputs a warning and then _registerItem also outputs a warning (because it's already registered).

RegisterStatusNotifierItemAsync is being called twice every 10 seconds since gnome-shell started:

Apr 22 19:40:08 rincewind gnome-shell[7086]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.88/org/ayatana/NotificationItem/Keybase1
Apr 22 19:40:08 rincewind gnome-shell[7086]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.62/org/ayatana/NotificationItem/multiload
Apr 22 19:40:08 rincewind gnome-shell[7086]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.119/org/ayatana/NotificationItem/software_update_available
Apr 22 19:40:08 rincewind gnome-shell[7086]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.78/org/ayatana/NotificationItem/indicator_cpufreq
Apr 22 19:40:08 rincewind gnome-shell[7086]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.104/StatusNotifierItem
Apr 22 19:40:11 rincewind gnome-shell[7086]: [AppIndicatorSupport-WARN] Attempting to re-register :1.62/org/ayatana/NotificationItem/multiload; resetting instead
Apr 22 19:40:11 rincewind gnome-shell[7086]: [AppIndicatorSupport-WARN] Item :1.62/org/ayatana/NotificationItem/multiload is already registered
Apr 22 19:40:11 rincewind gnome-shell[7086]: [AppIndicatorSupport-WARN] Attempting to re-register :1.62/org/ayatana/NotificationItem/multiload; resetting instead
Apr 22 19:40:11 rincewind gnome-shell[7086]: [AppIndicatorSupport-WARN] Item :1.62/org/ayatana/NotificationItem/multiload is already registered

The indicator-multiload-0.4 update interval is set to 10 seconds. If I change this then it affects the frequency of the warnings.

It's registering twice every 10 seconds:
[pid 7301] 11:19:10.530942 sendmsg(8, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\1\0\1,\0\0\0\206\274\10\0\206\0\0\0\10\1g\0\1s\0\0\1\1o\0\26\0\0\0/StatusNotifierWatcher\0\0\3\1s\0\32\0\0\0RegisterStatusNotifierItem\0\0\0\0\0\0\2\1s\0\35\0\0\0org.kde.StatusNotifierWatcher\0\0\0\6\1s\0\5\0\0\0:1.25\0\0\0'\0\0\0/org/ayatana/NotificationItem/multiload\0", iov_len=196}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 196
[pid 7301] 11:19:10.531245 sendmsg(8, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\4\1\1\0\0\0\0\207\274\10\0c\0\0\0\1\1o\0'\0\0\0/org/ayatana/NotificationItem/multiload\0\3\1s\0\7\0\0\0NewIcon\0\2\1s\0\32\0\0\0org.kde.StatusNotifierItem\0\0\0\0\0\0", iov_len=120}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 120
[pid 7301] 11:19:10.531395 sendmsg(8, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\1\0\1,\...

[Jerry Quinn (jlquinn)]

This is pretty bad. I see 8-10 messages per second in /var/log/syslog. That makes it difficult to see anything else, potentially causing a security issue.

[kenjo (ken-kenjo)]

I could get the messages to stop by selecting quit on some cpu/network monitoring icon at the top right.

once that thing stopped showing up I no longer get the messages. Not sure what the extension was called. Can't turn on off extensions anymore and I don't see anything in the gnome-tweaks program that sounds like cpu/network monitoring so I have no idea what it was.

GNOME shell is such a disaster totally messed up design.

[Angel D. Segarra (angel-segarra)]

This problem is compounded by the fact that rsyslog is duplicating journal logging. Getting huge log files.

[laluz (laluz)]

gnome-shell[11642]: [AppIndicatorSupport-WARN] Item :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1 is already registered
gnome-shell[11642]: [AppIndicatorSupport-WARN] Attempting to re-register :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1; resetting instead

is repeating every minute in syslog.
Description: Ubuntu 18.04.1 LTS

[Phil Hanson (philhanson)]

I see this when I try to install Microstack snap on Bionic

[Hans Deragon (deragon)]

@kenjo (ken-kenjo) found the solution for me. The error shows up every second in syslog. However, when I quit the Gnome shell extension 'System Load Indicator 0.4', it stops.

[Jamie Browning (nzdev)]

Why is this low importance when anyone who has this issue should be quiting the application rendering it useless, seems pretty high to me. What else could possibly trump this?

[Marco Trevisan (Treviño) (3v1n0)]

This has been fixed upstream v32 version and released in ubuntu with version 32-1