http://bugzilla.opensuse.org/show_bug.cgi?id=1094762 http://bugzilla.opensuse.org/show_bug.cgi?id=1094762#c82 --- Comment #82 from andreas bittner <abittner@opensuse.org> --- yes it is a testing system. side note: my other production system that was in the unrebooted state, i had the idea to reboot it eventually via reboot -f (reboot alone did nothing) but it never came back since :( so I need to visit on site and see where it hangs or what went wrong. my other production site has some mdraid and data that i dont dare yet to reboot maybe until we find out more about this bug. or would it be safe to manually fire up the systemd main (which exactly?) process somehow and re-execute all the processes from the zypper dup stage that wanted to interact with systemd? it is totally unclear to me what I can do about my hanging pending production system where this bug happened during dup. what is a possible workaround even now that the situation happened? -- You are receiving this mail because: You are on the CC list for the bug.