All, On 15.4, I have had the taskbar, set to auto-hide, disappear after Xorg updates. This has occurred twice in the past month or two after xorg updates. Most recently after the xorg-server update, Thu 15 Dec 2022 02:46:26 AM CST xorg-x11-server 1.20.3-150400.38.13.1 Thu 15 Dec 2022 02:46:26 AM CST xorg-x11-server-extra 1.20.3-150400.38.13.1 The taskbar cannot be un-hidden by moving the mouse over it. The solution is simple, open kcontrol, desktop, panels and then toggle the auto-hide option off/on and then all works as it should again. I don't know if this is worth looking at, the first time it occurred, I just chocked it up to a one-time deal. But after the identical thing occurred after the most recent updates, there is something specific that triggers this behavior. The full set of updates installed when the behavior was last seen was: Thu 15 Dec 2022 02:46:23 AM CST kdebase4-runtime 17.08.3-lp154.67.93 Thu 15 Dec 2022 02:46:24 AM CST autoyast2-installation 4.4.43-150400.3.16.1 Thu 15 Dec 2022 02:46:24 AM CST libfreebl3 3.79.2-150400.3.18.1 Thu 15 Dec 2022 02:46:25 AM CST libfreebl3-hmac 3.79.2-150400.3.18.1 Thu 15 Dec 2022 02:46:25 AM CST libsodium23 1.0.18-150000.4.6.1 Thu 15 Dec 2022 02:46:25 AM CST mozilla-nss-certs 3.79.2-150400.3.18.1 Thu 15 Dec 2022 02:46:25 AM CST sudo 1.9.9-150400.4.9.1 Thu 15 Dec 2022 02:46:25 AM CST sudo-plugin-python 1.9.9-150400.4.9.1 Thu 15 Dec 2022 02:46:26 AM CST xorg-x11-server 1.20.3-150400.38.13.1 Thu 15 Dec 2022 02:46:26 AM CST xorg-x11-server-extra 1.20.3-150400.38.13.1 Thu 15 Dec 2022 02:46:26 AM CST yast2-storage-ng 4.4.41-150400.3.6.1 Thu 15 Dec 2022 02:46:27 AM CST libsodium-devel 1.0.18-150000.4.6.1 Thu 15 Dec 2022 02:46:27 AM CST libsoftokn3 3.79.2-150400.3.18.1 Thu 15 Dec 2022 02:46:28 AM CST mozilla-nss 3.79.2-150400.3.18.1 Thu 15 Dec 2022 02:46:28 AM CST yast2-security 4.4.17-150400.3.10.1 Thu 15 Dec 2022 02:46:29 AM CST yast2-installation 4.4.58-150400.3.15.1 Thu 15 Dec 2022 02:46:31 AM CST libsoftokn3-hmac 3.79.2-150400.3.18.1 Not sure if kdebase4-runtime would have anything to do with it, but that is updated quite often as well -- and may have been updated when this occurred the previous time as well. Not worth a bug report since I can't isolate the problem, only the symptoms, but was worth noting here if other have seen this as well. -- David C. Rankin, J.D.,P.E.