LibreOffice can't render text in VirtualBox-5.2.22-126460-Win running Windows 10 guest

Discussions about using Windows guests in VirtualBox.
Post Reply
randomvirtualboxer
Posts: 1
Joined: 3. Jan 2019, 04:06

LibreOffice can't render text in VirtualBox-5.2.22-126460-Win running Windows 10 guest

Post by randomvirtualboxer »

Hello. I think I found a bug, but better check here first. I was running VirtualBox-5.2.6-120293-Win here in my Windows 8.1 host with a Windows 10 guest and everything was working fine, until I decided to stop ignoring update warnings and updated to VirtualBox-5.2.22-126460-Win. LibreOffice wouldn't render any text: neither UI (menus etc) nor the document's contents itself. Imagine an only icons UI, no characters anywhere, and a blank document where there should be (lots of) words.

(BTW, a second issue is noticeable: shared folders feature worked in the older version, and stopped working in the newer version. The folder was properly configured, but guest couldn't see any, and disabling it and re-setting it didn't make it work. Drag-and-drop files too.)

I solved my issue by simply reinstalling the previous working version (5.2.6), which worked perfectly, as everything is running smooth again. But I thought it could be a bug worthy of reporting (if it wasn't already). Is it?

I regret not having any screenshot, but I am really not up to re-updating just to make a nice picture, sorry.

EDIT: downgrading did not solve everything. Shared folders are still not working, and neither is drag-and-drop.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: LibreOffice can't render text in VirtualBox-5.2.22-126460-Win running Windows 10 guest

Post by socratis »

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply