I got a quite strange issue with tumbleweed. After I join it to my MS active directory via Yast2 GUI it is completely broken and won’t boot anymore.
- Freshly installed Tumbleweed with KDE inside VM - next, next, done.
- set hostname via hostnamectl
- configure NTP
- join my windows active directory domain via Yast2 (successfully)
Next reboot the system won’t boot. It is stuck at the boot screen.
I was able to reproduce it several times, EFI boot, BIOS boot, in a VM on my KVM hypervisor, in a VM on my desktop (VBox). Every time the same result.
Any ideas ?
cheers
Michael
When you say stuck at the boot screen, can you be more specific about what you’re observing? After the GRUB boot screen, you see the plymouth boot splash screen? If you press the ‘Esc’ key at this time, do you observe the initial boot messages displayed? Can you get to another VT and login successfully?
Hi Deano,
thanks for your reply and happy new year! 
When I say stuck at boot, I mean the black screen with the “Tumbleweed” Logo and the spinning circle.
I have deleted the machine account in my AD and reverted the snapshot of my test VM to a clean state and tried again. When I press ESC it looks like that:
I could swear the last time I pressed ESC it looked different… some error with “AppAmor”
Another detail I have noticed: right after the domain join, I cannot reboot via GUI. I have seen this a couple of times now during my tests. When I click on “reboot” in the start menu, the screen gets black and there is this timer counting down, but the “restart now” button is missing. When the timer is finished, I am back at the desktop. Have to reboot via terminal. If it helps, I can revert the VM again and take a screenshot.
cheers
Michael
I downloaded a brand new Tumbleweed ISO, compared the file hash, created a new VM → Same issue.
I am not sure if my windows domain can be the issue - other than the Tumbleweed VMs all other machines run fine. I even got some non Windows Members (e.g. TrueNAS with AD Integration)
But even if my windows domain WAS the issue, I think Tumblewees should not just break completely, should it? 
As I can reproduce the issue over an over, even on different hypervisors I think this might be a bug in Tumbleweed?
Can I do anything to help fix this? Support logs? Do tests?
cheers
Michael
P.S.: here is a screenshot of the reboot issue I mentioned:
