Page 1 of 1

Discuss the 6.0.10 release

PostPosted: 16. Jul 2019, 15:50
by michael
Discuss the 6.0.10 release here.
You can download the release here.
VirtualBox 6.0.10 is a new maintenance release.

VirtualBox 6.0.14 has been released. Please try that before continuing the discussion in this thread.

Known new issues/regressions
These are new and confirmed tickets about issues with 6.0.10:
  • #11577 Secure Boot doesn't allow 'vboxdrv' module to load (now works for Ubuntu and Debian 10+ hosts)
  • #18766 6.0.10 r132072 crashes Windows VM when Shared Folders are used - Fixed with 6.0.11 r132480 or later.
  • #18767 VirtualBox 6.0.10 segfaults at startup on CentOS 7.6
  • #18802 cannot do "savestate" machine - Fixed with 6.0.12.
  • #18843 VirtualBox crashes with Skype and Windows 10 guest
  • #18869 vbox_ttm.c - header file nit in include directive - Fixed with 6.0.11 r132724 or later.
  • #18917 VBox 6.0.10 GAs fail to compile on Red Hat/CentOS/OL 7.7; also Red Hat 8.1 Beta - Fixed with 6.0.13 r133264 or later.
See also:

Re: Discuss the 6.0.10 release

PostPosted: 18. Jul 2019, 14:32
by sej7278
i get a segfault when trying to install the guest additions on an existing debian stretch guest (debian buster host).

if i ignore it and reboot, the guest comes back with no way to move the mouse or use the keyboard - i'm basically stuck at the gdm screen with no way to login.

Re: Discuss the 6.0.10 release

PostPosted: 18. Jul 2019, 14:40
by michael
Could you please provide more details about the segfault? I assume it is in code on the host?

Re: Discuss the 6.0.10 release

PostPosted: 18. Jul 2019, 18:19
by sej7278
michael wrote:Could you please provide more details about the segfault? I assume it is in code on the host?

hmm, it seems to be ok now, don't you just love intermittent issues?!

it did segfault with some error code (139?) twice when trying to build the initramfs. it was VBoxLinuxAdditions.sh that segfaulted on the guest, not vbox on the host.

i wonder if it was because i'd already mounted some shared folders - as this time i just did a fresh boot and ran the installer straight away.

Re: Discuss the 6.0.10 release

PostPosted: 9. Aug 2019, 17:31
by jsnyder-ats
I have not had any issues with segfaults; however, 6.0.10 broke the mouse cursor for me. The cursor display is 2/3rds of a line below where it has an effect. This happened in an earlier release but was fixed, so it seems that this is a regression.

Re: Discuss the 6.0.10 release

PostPosted: 9. Aug 2019, 18:38
by klaus
Try the latest 6.0 guest additions from the Test build page. It contains some fixes to the Windows graphics drivers which had issues with the Windows 10 magnifier support... if it doesn't help, let us know, ideally with a screenshot.

Re: Discuss the 6.0.10 release

PostPosted: 12. Aug 2019, 15:48
by jsnyder-ats
I upgraded the VirtualBox to the latest test build, along with the guest additions. The issue is still present.

Environment:
Windows 7
VirtualBox: 6.0.11r132665
Guest Additions: VBoxGuestAdditions_6.0.11-132500.iso
Image: Ubuntu 16.04

Running any editor (gedit, Sublime, etc...), if I click into text, the cursor will place itself on the line above where I clicked and to the left by 2 characters.

Example:

Line 1
Line 2

Using 6.0.10/11, if I click directly at the end of Line 2, the cursor will place itself between the e and the space of Line 1.

This issue does not happen to me in 5.2.32.

Re: Discuss the 6.0.12 release

PostPosted: 25. Sep 2019, 15:48
by ciamaulex
Hello,

I have an issue that began with 6.0.10 and repeated with 6.0.12
Win7 32 bit guest, used since several years with all VBox versions since 5.1.x
This is used primarily as VPN access client with 10+ different VPN clients installed
Host was Win7 x64, now is Win10 x64

Starting with 6.0.10, after disconnecting VPN from certain sites, the Virtualbox window freezes (guest screen frozen as well).
this happened twice a day with NAT networking, then I switched to bridged mode and it never happened again.

After update to 6.0.12, this happened again with bridged networking.
I must kill the window from Task Manager on the host to reboot the guest.

If you need any log file, please let me know.

Best regards and thanks for the great work.

Re: Discuss the 6.0.10 release

PostPosted: 25. Sep 2019, 17:01
by socratis
ciamaulex wrote:I have an issue that began with 6.0.10 and repeated with 6.0.12
Then I'm going to move your post from the "Discuss the 6.0.12 release" to the "Discuss the 6.0.10 release" thread. Each "Discuss the X.Y.Z release" is specifically for problems new to the X.Y.Z release. Yours seems to belong in the 6.0.10 area.

ciamaulex wrote:then I switched to bridged mode and it never happened again
So, it's a sporadic one, not an easily reproducible test? That's a tough one...

ciamaulex wrote:If you need any log file, please let me know.
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 or recreate the 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

Re: Discuss the 6.0.10 release

PostPosted: 11. Oct 2019, 17:17
by ciamaulex
Hello,
the problem about frozen VM happened again today.

I wanted to give you a log from a cold boot as per your directions, but the other VM I cold boot daily did not show the issue again.
This is from another VM that was booted this morning from a saved state and ran fine for several hours until I disconnected my Cisco VPN client.
I hope it can shed some light, in any case I will post another log if the condition happens again.

Thank you

Re: Discuss the 6.0.10 release

PostPosted: 11. Oct 2019, 17:24
by ciamaulex
Oops, we're lucky today...
this VM was cold booted this morning and froze just now while trying anothe VPN connection.
Note: peeking at the last lines of the log I saw (both in this log and the previous) a line:

Audio: Device configuration of driver 'DSoundAudio' has changed

Maybe this has something to do?

Thank you