The only real concern I have is to determine if I can make Gimp run my large format Epson printers. Whatever was troubling it appeared to be a hard fault the OS was unresponsive, and I had to shut it down and restart from VMware.Īnyway, now the fun begins I get to systematically go thru my daily routines to see if Fedora will work for me. And this was a log for the successful boot, so that may be irrelevant anyway.

There were numerous warnings, but the only line saying “Critical” reported: “CRITICAL: Unable to create a DBus proxy for Gno” “Gnome”, I’m guessing, the rest of the line was off-screen in the terminal window. Gotta love a self-healing OSĪnyway, once it started, I opened a terminal window to look at the ~2500-line log.

However, either because I typed faster, or who knows what, I was finally able to get past the “setup”, and now Fedora seems to be running as intended as a virtual machine.I have re-booted it several times, and even “Yummed” in a couple of apps successfully. Generally, at the “about” screen, the system would hang, and display the error window. So I went thru several restarts getting screen captures of the “Setup” windows, attached. Maybe because Fedora startup was running a “Setup” script, or maybe because of the “F” keys being virtual on the touchbar of this Mac? Whatever, it wouldn’t happen. I was totally unable to get the hot-key sequence to open a terminal window. Installing an OS as a virtual machine always adds a layer of uncertainty.

Vmware fusion 12 mojave