Yes, I either have a different bug, or this isn't the real fix. I've tried
every combo in the thread above, and on a new install of 12.04, no go - I
did get as far as getting an error free install of VB, but then every
windows virtual machine crashes - and crashes linux itself - halfway
through a boot - right at that "booting windows" screen, before the login.
On Mon, Apr 15, 2013 at 12:10 PM, Ads20000 <email address hidden>wrote:
> When will this fix be released for precise? (considering it is an
> important and old bug)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch should support this but best to make sure (not all
> 12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions
>
Yes, I either have a different bug, or this isn't the real fix. I've tried
every combo in the thread above, and on a new install of 12.04, no go - I
did get as far as getting an error free install of VB, but then every
windows virtual machine crashes - and crashes linux itself - halfway
through a boot - right at that "booting windows" screen, before the login.
On Mon, Apr 15, 2013 at 12:10 PM, Ads20000 <email address hidden>wrote:
> When will this fix be released for precise? (considering it is an /bugs.launchpad .net/bugs/ 1081307 dfsg-2ubuntu0. 2: virtualbox kernel module dfsg-2ubuntu0. 2 ature: Ubuntu 3.2.0-32.51-generic 3.2.30 dules: nvidia ture: all dfsg-2ubuntu0. 2 dfsg-2ubuntu0. 2: virtualbox kernel module /www.virtualbox .org/changeset/ 41660/vbox dfsg-2ubuntu0. 3 upload to precise-proposed. /bugs.launchpad .net/ubuntu/ +source/ virtualbox/ +bug/1081307/ +subscriptions
> important and old bug)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https:/
>
> Title:
> virtualbox-dkms 4.1.12-
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-
> ProcVersionSign
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitec
> PackageVersion: 4.1.12-
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https:/
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch should support this but best to make sure (not all
> 12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
> https:/
>
--
Why guess when you can know. Measure!