@ xoristzatziki (simsonbike-bugs) wrote 1 hour ago:
> Otherwise we should somehow change the "Support lifespan" there in order not to direct people to
> loose confidence for LTS versions and UBUNTU itself.
Slow down a little, and think about what you are saying:
Multiverse = Unsupported, Closed-Source and Patent-Encumbered Software
That sort of tone in your post, will NOT make it more likely to get fixed, but just annoy people who might be able get it done.
It's not even clear who needs to fix it or what the problem is. It's third party software. If you absolutely needs it to work NOW. There are 3 perfectly acceptable solutions already outlined in this thread:
1. go to the core non-HWE 4.4.0-109 kernel by using advanced GRUB menu
2. got to the core non-HWE 4.4.0-109 kernal by permanently removing the HWE kernel from your machine
3. Boot from 4.10.0 using the "advanced menu" in GRUB (that's what I am currently doing)
4. install VB 5.2 from third party binary or ppa
This could be a long time getting fixed, because it's complicated, involves multiple vendors and the whole spectre mess caused it all, which is probably more important than VB. So you should choose your options from above and get on with it.
Personally I am currently using 3, and will choose 2 or 4 if situation persists for more than a few weeks.
@ xoristzatziki (simsonbike-bugs) wrote 1 hour ago:
> Otherwise we should somehow change the "Support lifespan" there in order not to direct people to
> loose confidence for LTS versions and UBUNTU itself.
Slow down a little, and think about what you are saying:
$ apt-cache show virtualbox
Package: virtualbox dfsg-0ubuntu1. 16.04.2
Architecture: amd64
Version: 5.0.40-
Priority: optional
Section: multiverse/misc
Multiverse = Unsupported, Closed-Source and Patent-Encumbered Software
That sort of tone in your post, will NOT make it more likely to get fixed, but just annoy people who might be able get it done.
It's not even clear who needs to fix it or what the problem is. It's third party software. If you absolutely needs it to work NOW. There are 3 perfectly acceptable solutions already outlined in this thread:
1. go to the core non-HWE 4.4.0-109 kernel by using advanced GRUB menu
2. got to the core non-HWE 4.4.0-109 kernal by permanently removing the HWE kernel from your machine
3. Boot from 4.10.0 using the "advanced menu" in GRUB (that's what I am currently doing)
4. install VB 5.2 from third party binary or ppa
This could be a long time getting fixed, because it's complicated, involves multiple vendors and the whole spectre mess caused it all, which is probably more important than VB. So you should choose your options from above and get on with it.
Personally I am currently using 3, and will choose 2 or 4 if situation persists for more than a few weeks.
Respect