After much digging, I believe the bug comes from the indicator processes shutting down themselves because the panel is not fast enough to connect to them. This can be workaround with two environment variables:
- INDICATOR_SERVICE_SHUTDOWN_TIMEOUT: the time before the process shutdown itself in milliseconds. Default value is 500 milliseconds, but the system multiplies it by two at startup.
- INDICATOR_ALLOW_NO_WATCHERS: if this environment variable is set the indicator processes won't shut down themselves automatically.
Can you try this?
- Create a file named /etc/X11/Xsession.d/72indicators-no-shutdown, with the following content:
export INDICATOR_ALLOW_NO_WATCHERS=1
- Restart your session and see if you still experience the bug.
After much digging, I believe the bug comes from the indicator processes shutting down themselves because the panel is not fast enough to connect to them. This can be workaround with two environment variables:
- INDICATOR_ SERVICE_ SHUTDOWN_ TIMEOUT: the time before the process shutdown itself in milliseconds. Default value is 500 milliseconds, but the system multiplies it by two at startup.
- INDICATOR_ ALLOW_NO_ WATCHERS: if this environment variable is set the indicator processes won't shut down themselves automatically.
Can you try this? Xsession. d/72indicators- no-shutdown, with the following content: ALLOW_NO_ WATCHERS= 1
- Create a file named /etc/X11/
export INDICATOR_
- Restart your session and see if you still experience the bug.