Comment 66 for bug 1081307
Revision history for this message
| Doug Coulter (dcfusor) wrote Re: [Bug 1081307] Update Released | #66 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Sadly, while this did fix the build bug (as did the -proposed), I still
have a major bug - VB is totally unusable on 12.04 with any guest I have
(all of which work on every other machine here). Partway through booting,
say, 32 bit winxp - linux crashes and restarts.
(all my appliances are windows/32)
These are 32 bit appliances trying to run on a 12.04 that is 64 bit, i5, 8
gigs ram, SSD and spinners. They do run fine on 32 bit 12.04's that were
upgraded from 10.04, but not on this fresh build that required 64 bit to
get past the UEFI mobo - 32 bit ubuntu would not install, so I went 64, as
recommended on this box.
These machines also run fine on an upgraded 10.04/64 bit other machine.
My bug report was assigned to this bug as a dupe, but it isn't a dupe and
doesn't belong on this thread. How do I report this as a bug of its own?
It is NOT the same one.
This only appears to happen on a fresh install of 12.04 - not on ones
upgraded from 10.04. So there's something important that is different
between a fresh install and an upgrade.
Yes, despite it being hard on 12.04, I added my user to all the right
groups (think, get mate so you can still have a bit of control over your
machine).
On Wed, May 8, 2013 at 10:45 AM, Scott Kitterman <email address hidden>wrote:
> The verification of this Stable Release Update has completed
> successfully and the package has now been released to -updates.
> Subsequently, the Ubuntu Stable Release Updates Team is being
> unsubscribed and will not receive messages about this bug report. In
> the event that you encounter a regression using the package from
> -updates please report a new bug using ubuntu-bug and tag the bug report
> regression-update so we can easily find any regresssions.
>
> --
> 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 Released
> 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!