Mint 17.3 / Abort with 3D on & window on virtual screen > 1

[melgish]

Hello Internet

Host: Windows 10 (x64) + Virtual Box 5.0.14r105127
Guest: Mint 17.3 (x64) + Guest Additions 5.0.14r105127

Trying to resolve a bit of a puzzle. On the primary display, my Mint guest works fine. On any other display, something goes wrong and Mint desktop never completes loading. It freezes somewhere between showing the welcome screen and playing the welcome screen sound. Disabling 3D allows it to open, but then I'm stuck in software rendering mode.

Once loaded on the primary screen, the guest window can be moved to another monitor and seems to work just fine. Though this work-around is a bit of a pain since there's no Virtual Box option like "Always start guest on primary screen"

I'm hoping someone has already solved this issue. Any thoughts or ideas?

Thanks in advance.

[socratis]

I have to admit that this behavior is puzzling at its best. I'd like to see two VBox.logs, one for the case that it works, and one for the case that it fails.
- Start the VM.
- Observe the error.
- Shut down the VM. Not save, not pause, complete shut down. If you can't see a thing, abort the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.
Do it once again for the working case.

[melgish]

Attached are the two logs as requested.

Failure was launched / run on the secondary monitor. ACPI Shutdown didn't respond. File / Exit brought up the normal VirtualBox exit prompt, but then froze before I could choose any of the options. Log saved after machine abort.

Success was run entirely on the primary monitor, and log saved after ACPI shutdown.

[socratis]

Well, as you said at the beginning, it's a puzzle. I didn't see anything in the logs that would cause this to happen.

What I did see is that the Intel HD Graphics 5600 came up in both the logs and problems have come up a couple of times in the past when users were using the Intel Graphics. Could be that one, although still doesn't explain the preference on one monitor over the other.

The other question (and I'm shooting in the dark here), are both monitors controlled by the same graphics card?

[melgish]

I'll have to research that as the truth is I'm not sure. Both of my additional monitors are connected via USB / DisplayLink, though I did connect one via HDMI with the same result.

Thanks for looking into it. For the moment I've added some additional time to the bios/logo display to help me remember to drag it down to the primary before it crashes.

[melgish]

Just a quick follow up

I switched graphics modes of my msi laptop to use the nvidia chip instead of intel and still have the issue.

[jgonzale]

Hi all,

I have similar problems to the ones reported in this topic. In my case, I have a Mint 17.3 guest, with "3D Accelartion" active and just one Virtual Screen.

When using regular GL accelerated Cinnamon, the guest Aborts everytime I try to perform a regular Shutdown or when I want to Save the machine state.

Find attached to this post a log, where the last entries correspond to an abort when saving the machine state. Please note that usually, the Abort does not show any message, but when trying to save the log attached, VirtualBox show the error box also attached.

I hope we can solve this issue.

[melgish]

Problem remains unsolved, but here's some more information. My Mint system is/was configured for auto-login.

I've duplicated the problem using Debian 8, but the lockup only seems to occur if I login while the system is on the alternate screen. As long as it's on the primary screen when I login, it seems to work normally. Though it does freeze up about once a day, but I haven't detected a pattern.