Most of you probably are aware of this, but for people who are freaking out because their VMs don't work and don't know what to do:
Open a terminal. Open Synaptic Package Manager by issuing the command: gksudo synaptic Search by name for "virtualbox-ose-modules". Take note of the latest version you have installed (2.6.24-16, for example). Close Synaptic Package Manager. Issue the command: sudo gedit /boot/grub/menu.lst Scroll to the bottom where your menu list entries are defined. Copy/paste the menu entry block for the kernel version that matches your VirtualBox modules version to the top of the menu entry list. This will cause the GRUB boot loader to load the old kernel by default, which will match your VirtualBox modules version, which will cause VirtualBox to work normally again. Reboot to load the old kernel version. Test VirtualBox. Funny this hasn't been confirmed, and even stranger there aren't more cries about this...is no one using VirtualBox? It blows VMWare away as far as I'm concerned. The repository maintainers need to add this to their "list of things to pay attention to" for sure. ** Attachment added: "Where for art thou, O vbox modules" http://launchpadlibrarian.net/15061842/Where%20for%20art%20thou%2C%20O%20vbox%20modules -- no virtualbox-ose-modules package for latest kernel (2.6.24-18) https://bugs.launchpad.net/bugs/237471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
