Discuss the 5.2.16 release
Discuss the 5.2.16 release
Discuss the 5.2.16 release here.
You can download the release here.
Mainly a regression-fix release for 5.2.14.
You can download the release here.
Mainly a regression-fix release for 5.2.14.
-
- Posts: 228
- Joined: 1. Jan 2017, 09:16
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu 16.04 x64, W7
Re: Discuss the 5.2.16 release
michael - you've pasted the 5.2.14 link in there instead.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Discuss the 5.2.16 release
I've corrected the link in the quote below.
michael wrote:Discuss the 5.2.16 release here.
You can download the release here.
Mainly a regression-fix release for 5.2.14.
Re: Discuss the 5.2.16 release
Thanks - fixed in my message.
-
- Volunteer
- Posts: 1003
- Joined: 5. Sep 2008, 14:40
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Solaris, Linux, Windows, OS/2, MacOSX, FreeBSD
- Contact:
Re: Discuss the 5.2.16 release
whilst obviously you can't officially support debian sid, i thought i'd just let you know that due to its dependency on libcurl3, vbox 5.2.16 won't even install on debian sid/buster amd64 but 5.2.14 works fine.
running dpkg -I against the two packages seems to show dependency on libcurl3-gnutls (>= 7.16.2) for 5.2.14, but libcurl3 (>= 7.16.2) for 5.2.16
seems like an error to depend on the non gnutls version - wouldn't that break the update check or whatever you're using curl for?
running dpkg -I against the two packages seems to show dependency on libcurl3-gnutls (>= 7.16.2) for 5.2.14, but libcurl3 (>= 7.16.2) for 5.2.16
seems like an error to depend on the non gnutls version - wouldn't that break the update check or whatever you're using curl for?
Re: Discuss the 5.2.16 release
Please try the Ubuntu 18.04 package. Ubuntu 18.04 is based on Buster/Sid, so is a better match than Debian Stretch. And Ubuntu 18.04 uses libcurl4.
Re: Discuss the 5.2.16 release
Could you please elaborate on why the non-gnutls version should break the update check? My understanding, including from reading what the libcurl authors write, is that the choice of openssl/gnutls is an implementation detail, but you may well know something I do not.
-
- Posts: 21
- Joined: 24. Jan 2018, 11:12
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: WinXP and lots of Linuxes
Re: Discuss the 5.2.16 release
While the 5.2.14 release solved all the audio issues i had with all clients on Windows 7 & 10 hosts,
a sporadic slightly crackling in sound has reappeared with the 5.2.16 release.
In all other aspects the update is fine with me.
a sporadic slightly crackling in sound has reappeared with the 5.2.16 release.
In all other aspects the update is fine with me.
-
- Volunteer
- Posts: 1003
- Joined: 5. Sep 2008, 14:40
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: Solaris, Linux, Windows, OS/2, MacOSX, FreeBSD
- Contact:
Re: Discuss the 5.2.16 release
i mistakenly assumed the libcurl3-gnutls version is the only one that supports crypto, not that the libcurl3 version supports openssl
i wouldn't recommend installing the ubuntu 18.04 package for buster users, it seems to have completely broken my systemd setup!!!!!
i wouldn't recommend installing the ubuntu 18.04 package for buster users, it seems to have completely broken my systemd setup!!!!!
Last edited by sej7278 on 18. Jul 2018, 15:24, edited 1 time in total.
-
- Posts: 5
- Joined: 22. Jul 2018, 01:31
Re: Discuss the 5.2.16 release
Host Windows home 10 64bit v1803
Guest: Windows 7 64bit sp1
Problem: I have audio issues from any type of audio source, streaming, video clips, mp3, etc.
Description of problem:
1) Using HD Intel audio Perfect audio for the first 11minutes followed by progressive popping and scratching at first followed by incoherent audio that flutters like a misaligned film projector. The stream or video or mp3 needs to be paused for a few second then it returns to normal until another 11 minutes passes by to start the distortion all over again.
2) Using AC'97 Audio Every 20 to 30 seconds the audio skips and mutes for a few second then resumes back to normal for intervals of another 20-30 seconds then repeats the same problem.
Start of the problem:
At the same time I updated Windows from v1607 to v1803 also Updated Virtualbox from v5.1.22 to v5.2.16
I should have installed one at the time to pinpoint which was the culprit, but no.
Solutions tried:
I tried 5.2.x revision 123579, didn't change conditions.
Same problems coming from a Linux Mint Guest.
Changing from 48'000 audio to 44'000 audio didn't fix or change anything.
I would like to reinstall v5.1.22 but I can't launch any hosts. (too noob to know how to roll back VB versions)
Please help
Guest: Windows 7 64bit sp1
Problem: I have audio issues from any type of audio source, streaming, video clips, mp3, etc.
Description of problem:
1) Using HD Intel audio Perfect audio for the first 11minutes followed by progressive popping and scratching at first followed by incoherent audio that flutters like a misaligned film projector. The stream or video or mp3 needs to be paused for a few second then it returns to normal until another 11 minutes passes by to start the distortion all over again.
2) Using AC'97 Audio Every 20 to 30 seconds the audio skips and mutes for a few second then resumes back to normal for intervals of another 20-30 seconds then repeats the same problem.
Start of the problem:
At the same time I updated Windows from v1607 to v1803 also Updated Virtualbox from v5.1.22 to v5.2.16
I should have installed one at the time to pinpoint which was the culprit, but no.
Solutions tried:
I tried 5.2.x revision 123579, didn't change conditions.
Same problems coming from a Linux Mint Guest.
Changing from 48'000 audio to 44'000 audio didn't fix or change anything.
I would like to reinstall v5.1.22 but I can't launch any hosts. (too noob to know how to roll back VB versions)
Please help
Re: Discuss the 5.2.16 release
Have met with CPU load issue...
Host has 6-cores CPU (+6 HT-cores enabled).
Guest has 4-cores assigned.
When guest shows 100% CPU load for all 4 cores, host shows 100% load for 2 cores only.
Before the VBox update CPU load was correlated: i.e. 100% load for 4 cores on guest - 100% load for 4 cores on host.
(Previous version was 5.2.10)
Host has 6-cores CPU (+6 HT-cores enabled).
Guest has 4-cores assigned.
When guest shows 100% CPU load for all 4 cores, host shows 100% load for 2 cores only.
Before the VBox update CPU load was correlated: i.e. 100% load for 4 cores on guest - 100% load for 4 cores on host.
(Previous version was 5.2.10)
-
- Posts: 5
- Joined: 20. Jul 2018, 19:34
Re: Discuss the 5.2.16 release
So why don't you just provide buster on your debian repo?michael wrote:Please try the Ubuntu 18.04 package. Ubuntu 18.04 is based on Buster/Sid, so is a better match than Debian Stretch. And Ubuntu 18.04 uses libcurl4.
Re: Discuss the 5.2.16 release
1) Buster is not yet released and we do not yet support it.
2) Every additional build we provide has overhead. If the Ubuntu 18.04 build works with Buster, what's the problem? People were using the Debian 8 build with it up until now.
2) Every additional build we provide has overhead. If the Ubuntu 18.04 build works with Buster, what's the problem? People were using the Debian 8 build with it up until now.
-
- Posts: 5
- Joined: 20. Jul 2018, 19:34
Re: Discuss the 5.2.16 release
For 1) True, I understand that.michael wrote:1) Buster is not yet released and we do not yet support it.
2) Every additional build we provide has overhead. If the Ubuntu 18.04 build works with Buster, what's the problem? People were using the Debian 8 build with it up until now.
For 2) There might be people being uncomfortable with introducing inconsistencies by mixing up Debian and Ubuntu packages on their systems because Ubuntu packages are known to often break other stuff on Debian, especially on Testing. That's a downside. Regarding overhead, why don't you just drop support (and manpower) for Lenny btw.? I assume there are very few people still using Lenny anyway, it's EOL since 2012-06-02.
Nevertheless, up until now, the stretch repo version used to work flawlessly (in sense of installation or upgrade) so what's the problem with building the package against libcurl4 from now on?