Comment 5 for bug 1739468

Revision history for this message
Simon Arlott (sa.me.uk) wrote :

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,\0\0\0\210\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 <unfinished ...>

There is only one indicator-multiload process running.

The tray icon doesn't appear to be working properly (it's always square with coloured vertical bars):
[pid 7301] 11:19:10.544076 sendmsg(8, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\3\1\1\"\0\0\0\212\274\10\0N\0\0\0\10\1g\0\1s\0\0\4\1s\0&\0\0\0org.freedesktop.DBus.Error.InvalidArgs\0\0\5\1u\0\276\267\6\0\6\1s\0\5\0\0\0:1.25\0\0\0\35\0\0\0No such property 'IconPixmap'\0", iov_len=130}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 130

Turning off all the graphs does not fix the registration warnings.