** Changed in: virtualbox (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Someone here told me to update with -proposed repository- to fix the
virtualbox problem. Now I remember why I did uncheck that repo,
everytime I open Chromium, I get a black screen since it installed the
new kernel 3.13.0-44-generic #73~precise1-Ubuntu.
--
You received this bug notification
This bug was fixed in the package virtualbox - 4.1.12-dfsg-2ubuntu0.7
---
virtualbox (4.1.12-dfsg-2ubuntu0.7) precise; urgency=low
* Add support for VirtualBox host kernel modules on Linux 3.13
(LP: #1292118).
-- Corey Wright undefined+ubu...@pobox.com Sun, 14 Dec 2014
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
yes, the solution was to issue some sort of apt-add-repository
ppa:costamagnagianfranco/locutusofborg-ppa.
Anyway, I hope somebody will sponsor the patch into ubuntu archives
soon.
thanks for testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Upload is sitting in the queue now:
https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text=
** Changed in: virtualbox (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged = Invalid
** Project changed: virtualbox = null-and-void
** Changed in: null-and-void
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: virtualbox (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: virtualbox (Ubuntu Precise)
Status: New = Triaged
** Changed in: virtualbox (Ubuntu Precise)
Hello Jason, or anyone else affected,
Accepted virtualbox into precise-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/virtualbox/4.1.12-dfsg-2ubuntu0.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I'm running precise with the Trusty HWE. I just installed the latest from
proposed - virtualbox 4.1.12-dfsg-2ubuntu0.7
It seems to have loaded up find after a reboot, and I could start up a VM.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for what appears to be the solution. It installed without any
grief, and I've been using vbox for about 2 hours without any problems.
Only one comment: I looked in my package manager to find the repo you
listed. It appears to be there, but launchpad.net is in the link
address right
Please test undefined's patch I uploaded into my ppa and report back.
thanks
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When I executed the first line of your sequence below, I didn't get the
virtualbox version your second line needs. Instead, I got:
virtualbox-4.3_4.3.16-95972~Ubuntu~raring_amd64.deb
It was dated Oct. 6, and located in ~/Downloads
Did I miss something?
Bill
On 12/15/2014 12:46 AM,
yes, that's because you don't have a pristine precise sources.list (ie
no more than main, universe, multiverse, restricted from precise,
precise-updates, and precise-security; no ppas or backports).
apt-get source virtualbox=4.1.12-dfsg-2ubuntu0.6
apt-get build-dep
Hi Bill, the patch was useful to me, to upload a fixed version into my ppa.
Now if you can test the ppa and report back positive feedbacks I'll ask a
sponsor to make the fix be uploaded into the ubuntu repositories.
there is no more need to build it yourself :-)
to add the repository
sudo
No Bill, it is everything ok :)
I'll ping some ubuntu folks on monday to get the fix landed :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6:
** Bug watch removed: Virtualbox Trac #11664
http://www.virtualbox.org/ticket/11664
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6:
better late than never; didn't realize i would have to do everything
myself.
apt-get source virtualbox
cd virtualbox-4.1.12-dfsg
patch -p1 ../linux-3.13-virtualbox-host-kernel-modules.patch
apt-get install build-dep virtualbox
apt-get install devscripts fakeroot
debuild -i -us -uc
cd ..
dpkg -i
I hope I haven't been sending a lot of duplicates. All I see is a
window that pops up announcing a problem and asking if I want to
report it. There isn't enough info for me to determine whether the
problem is a repeat of an earlier report, or something new.
Bill
On 12/11/2014 03:43 AM,
fixed in utopic+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
failed to build [error: incompatible types when
** Also affects: virtualbox
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
Added HWE today, Ubuntu would not reboot.
Restored previous build, removed Virtual Box using Ubuntu Software Center
Re-installed HWE. Installation successful.
Re-installed Virtual Box using Ubuntu Software Center
Installation failed (re-building kernel?)
Removed Virtual Box using Ubuntu Software
In Progress for two months without any progress. Unassigning...
** Changed in: virtualbox (Ubuntu)
Status: In Progress = Triaged
** Changed in: virtualbox (Ubuntu)
Assignee: TJ (tj) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug also affects me. I follow the procedure suggested by jbm131.
This is the download link:
https://www.virtualbox.org/wiki/Linux_Downloads
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
After updating to the latest Ubuntu OS, this is np longer an issue foe
me and vBox works as it should
Sent from my Windows Phone From: Vinícius Alves Hax
Sent: 10/6/2014 1:11 PM
To: scratcht...@gmail.com
Subject: [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6:
virtualbox kernel
Updated the hardware support stack in 12.04 as requested by update manager.
Rebooted. Tried to start virtualbox.
This failed Kernel driver not installed (rc=-1908)
Followed the instruction to do
/etc/init.d/vboxdrv setup
which failed as file does not exist.
So following various posts to resolve
** Changed in: virtualbox (Ubuntu)
Status: Triaged = In Progress
** Changed in: virtualbox (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: regression-release
--
You received this bug notification because you are a member
= SUMMARY =
this patch addresses the overarching virtualbox host linux kernel module source
code and not the specific problem of integrating it into the dkms package/setup
(which is left as an exercise to the reader). i demonstrate how to use the
below patch with the virtual-source package
The attachment virtualbox-source-vs-linux-headers-generic-lts-
trusty.patch seems to be a patch. If it isn't, please remove the
patch flag from the attachment, remove the patch tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by
Really strange?
No change in setup at all. I get duplicate answers on wifi but it's ok on cable
ethernet.
Only for VM machines in virtualbox,- not for the host Ubuntu.
This has something to do with the new kernel ... I have no idea?
--
You received this bug notification because you are a
Hi again
Something came up.
I did fix it as described above,- but:
I use wireless network to my Ubuntu,- and bridged network setup in the
virtualbox options for the VM hosts.
When I ping something from the terminal, now I get duplicate answers?
Very strange, and it must be in connection with
wow, thanks to all, I am really surprised about so much solutions.
Anyway, have choosen this and now it works again:
You need to physically download and install the latest version (after
doing a basic removal of the old version - don't do a complete removal).
Trying to keep the software updated
While one can work around this bug easily with third-party
PPA's/packages, it is not considered Fix Released until an updated
version of virtualbox is in the repo.
** Changed in: virtualbox (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a
I finally got my VMs working... someone in Oracle needs to know that the
PPA information they have is wrong (an error in one of the files Ubuntu
looks to for setup information).
You need to physically download and install the latest version (after
doing a basic removal of the old version - don't
Removing the old 4.1.x virtualbox package will not remove your virtual
images or your user's configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms
Hi Daniel
I did not know that, but it saved me many hours of work :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
Yep, after removing 'virtualbox-dkms' and installing the new version
(from Oracle) means I can run my VMs again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292118
Title:
virtualbox-dkms
Tried different solutions in forums without any luck.
I solved it by removing Virtualbox via softwarecenter and then using
autoremove.
Then I downloaded and installed a new Virtualbox directly from Oracle
after installing dkms.
Then everything worked again,- and my VM's was in place,-
40 matches
Mail list logo