I forgot to mention that this problem behavior is only present on Tumbleweed installed on real hardware ... the problem is not seen on Tumbleweed as a VirtualBox guest.