Keybase at startup in Ubuntu Mate 18.04 - Startup Error & No panel icon.

Not sure if they're related, but when keybase begins on startup via env KEYBASE_AUTOSTART=1 run_keybase, I get an error appearing in journalctl ("ERRO keybase main.go:90"). There are some complains from fusermount, though /keybase does seem to mount fine. Then, once started, there is no panel icon. If I run keybase again after startup, I do get the icon. Note that journalctl shows a non-keybase error immediately before the start of keybase:

GDBus.Error:org.freedesktop.DBus.GLib.ErrorError: Method invoked for RegisterStatusNotifierHost returned FALSE but did not set error

I'm not sure what that is, but since it could be related I thought I'd mention it.

$ ps ux | grep -i keybase
user       1735  1.8  5.4 1103844 112180 ?      Ssl  14:14   0:04 /usr/bin/keybase --debug --log-file=/home/user/.cache/keybase/keybase.service.log service
user       1760  0.6  5.6 1585372 116036 ?      Ssl  14:14   0:01 /opt/keybase/Keybase
user       1774  0.0  2.1 372452 42872 ?        S    14:14   0:00 /opt/keybase/Keybase --type=zygote --no-sandbox
user       1812  0.5  6.3 1134316 128872 ?      Sl   14:14   0:01 /opt/keybase/Keybase --type=renderer --no-sandbox --service-pipe-token=5CCD6D75F271900D39CAA3AA5D4F3E6E --lang=en-US --app-path=/opt/keybase/resources/app --node-integration=true --webview-tag=true --no-sandbox --context-id=2 --enable-pinch --num-raster-threads=1 --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553 --disable-accelerated-video-decode --enable-gpu-async-worker-context --service-request-channel-token=5CCD6D75F271900D39CAA3AA5D4F3E6E --renderer-client-id=4 --shared-files=v8_natives_data:100,v8_snapshot_data:101
user       1814  1.0  7.0 1157404 143460 ?      Sl   14:14   0:02 /opt/keybase/Keybase --type=renderer --no-sandbox --service-pipe-token=AA801A46F45F9610576B33C663AAED7B --lang=en-US --app-path=/opt/keybase/resources/app --node-integration=true --webview-tag=true --no-sandbox --context-id=2 --enable-pinch --num-raster-threads=1 --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553 --disable-accelerated-video-decode --enable-gpu-async-worker-context --service-request-channel-token=AA801A46F45F9610576B33C663AAED7B --renderer-client-id=6 --shared-files=v8_natives_data:100,v8_snapshot_data:101

$ journalctl -xe

Sep 17 14:14:25 Ubuntu-18 notification-ar[1656]: GDBus.Error:org.freedesktop.DBus.GLib.ErrorError: Method invoked for RegisterStatusNotifierHost returned FALSE but did not set error
Sep 17 14:14:30 Ubuntu-18 systemd[968]: Started Keybase core service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 17 14:14:30 Ubuntu-18 systemd[968]: Reloading.
Sep 17 14:14:30 Ubuntu-18 systemd[968]: Starting Keybase core service...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has begun starting up.
Sep 17 14:14:30 Ubuntu-18 systemd[968]: Starting Keybase Filesystem service...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has begun starting up.
Sep 17 14:14:30 Ubuntu-18 systemd[968]: Started Keybase GUI.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 17 14:14:30 Ubuntu-18 sh[1749]: 2018-09-17T14:14:30.912250-07:00 ▶ [ERRO keybase main.go:90] 001 dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory
Sep 17 14:14:30 Ubuntu-18 sh[1749]: fusermount: invalid mountpoint ''
Sep 17 14:14:32 Ubuntu-18 Keybase[1760]: No installer.json file
Sep 17 14:14:32 Ubuntu-18 Keybase[1760]: Version: 2.7.0-20180912172414+049d28bddb
Sep 17 14:14:32 Ubuntu-18 dbus-daemon[1173]: [session uid=1000 pid=1173] Activating service name='org.gnome.GConf' requested by ':1.51' (uid=1000 pid=1760 comm="/opt/keybase/Keybase " label="unconfined")
Sep 17 14:14:32 Ubuntu-18 dbus-daemon[1173]: [session uid=1000 pid=1173] Successfully activated service 'org.gnome.GConf'
Sep 17 14:14:35 Ubuntu-18 systemd[968]: Started Keybase core service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 17 14:14:36 Ubuntu-18 systemd[968]: Started Keybase Filesystem service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.

Reproduce the startup path using env KEYBASE_AUTOSTART=1 run_keybase, then inspect journalctl -xe, the main.go:90 error, and the reported fusermount and DBus messages. Compare it with launching Keybase again after startup; done means startup completes without the reported error and the panel icon appears immediately.