After not using tumbleweed for ca. 2 weeks, started it again in Virtualbox. Went OK as usual. Then discoverer came up with updates, let that run, and restarted. Got errors on when X11 should start, leaving me stranded at the CLI. Tried startx and that gave me:
bad display name xxxx.yyyy.zzz:0 in list command
bad display name xxxx.yyyy.zzz:0 in add command
I did define the FQDN on a manually fixed IP address, but it seems there is a spelling mistake compared to what is normally use in my LAN settings. I treid to run yast but couldn’t find my way in it.
Anyway, the recommendation to run display manger sddm also fails: it hangs after saying
Failed to read display numer from pipe
Display server stopped
Attempt 1 starting the Display server on vt 2 failed.
I desparately need to recover this installation as I have made a lot of updates to certein files and no backup (I know…). I can reacht the file at the CLI, but I wn’t try to get them out of the Vbox before I’m sure the whole setup is lost.
Remove xf86-video-vmware and clear content of xorg.conf (if existant).
sudo zypper rm xf86-video-vmware
This happened to all openSUSE VB installations here. Even fresh installations were affected. There was also a bugreport about that issue.
Great, that did the trick. Tx a lot for your quick response.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.