On Tuesday, 9 October 2018 05:00:58 CDT Simon Lees wrote:
Which desktop? they mostly all have different code to handle this.
Sorry, KDE. Also, it first happened while I was having cascading problems with the panel, nm-applet, bluetooth (an apparently unsupported Broadcom BCM20702A0), and at least one other plasmoid. I have voluminous logs from which I might be able to sort something out. However, it also happened after a Tumbleweed update (I think 20181002), so I wanted to check to see if it was a common problem. That would so much simpler. But having happened once, it continues despite having rebooted. Now I can remove a borked systray and replace it with a working one, but any attempt to configure (just open the dialog and hit cancel) borks it all over again. I am now on 20181004, same thing. -- Tom Hardy <rhardy702@gmail.com> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org