I also tested this with my profile and a fresh profile and the issue
remains the same. I also downloaded Firefox direct from Mozilla and the
issue remains the same, so it's not an Ubuntu bug, it's just the way
Mozilla has coded Firefox to select the default print DPI resolution -
grabbing the
Public bug reported:
Binary package hint: xen-utils-3.2
Distro: Ubuntu 8.04.1
Package: xen-utils-3.2.0-0ubuntu10
Arch: AMD64
The xendomains init script appears to have two errors that spew out on
boot (although it does not stop guests from starting).
As of version 3.2.0-0ubuntu10 Lines 186 and
** Changed in: initramfs-tools (Ubuntu)
Status: New = Invalid
--
Initramfs does not start raid array on boot
https://bugs.launchpad.net/bugs/212755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Tom,
I don't get that problem.. have you installed virtualbox-ose-modules-
generic ?
-c
P.S the command 'uname -a' will tell you your running kernel.
--
Missing VirtualBox Kernel Drivers for 2.6.24-15 kernel
https://bugs.launchpad.net/bugs/212624
You received this bug notification because
No worries :)
-c
--
Missing VirtualBox Kernel Drivers for 2.6.24-15 kernel
https://bugs.launchpad.net/bugs/212624
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
My problem is solved - it was my own stupid fault.
I replaced /etc/mdadm/mdadm.conf with an earlier copy, which had a
different array configuration in it. This meant that the initramfs
couldn't find the new array, because it wasn't in the config!
Whoops. Sorry Linux.
I suggest blackiwid check
..and package for x86 (which does work with m-a if you want to build it
yourself).
-c
** Attachment added:
virtualbox-ose-modules-2.6.24-16-generic_1.5.6-dfsg-6ubuntu1+2.6.24-16.30_i386.deb
Kernel upgraded again, so here are some updates modules.
AMD64 build doesn't work with module-assistant (some problem with
assembler I think) so built manually - let me know if it doesn't work
for you. Works for me :)
-c
** Attachment added:
A symlink should do the trick. I installed 32bit Ubuntu under virtualbox
and have built a package you can try, attached.
-c
** Attachment added:
virtualbox-ose-modules-2.6.24-15-generic_1.5.6-dfsg-4ubuntu2+2.6.24-15.26_i386.deb
No worries, I just happened to stumble across your post :)
Once the dev releases the official package, you should be able to remove
the one you installed from me and install the official one - or this
should automatically happen when you upgrade to a new kernel (or we
might find ourselves back
Public bug reported:
Greetings,
My Father's system has 3 hard drives in Linux software raid level 5, with LVM
root on top.
Under Hardy x86_64 kernel 2.6.24-12-generic, this was working perfectly but
subsequent updates (namely 2.6.22-14-generic and 2.6.24-15-generic) have broken
this.
The
I'm sure it's just a matter of time before the vbox dev updates this,
but in the mean time if you need to get up and running you can do this:
#Become root
sudo su -
#Install module assistant and build deps
apt-get install module-assistant
m-a prepare
#Get the virtualbox source and tell
Whoops, that third 'm-a' command should be :
m-a install virtualbox-ose
not:
m-a build virtualbox-ose
-c
--
Missing VirtualBox Kernel Drivers for 2.6.24-15 kernel
https://bugs.launchpad.net/bugs/212624
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Frederick: You're right, cheers.
--
umount: mount disagrees with the fstab
https://bugs.launchpad.net/bugs/99437
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have applied your patch Frederick and it does let users umount a drive
specified in fstab by UUID (thanks), however it still throws up an error saying:
Cannot eject volume
But it *does* indeed unmount, for which I'm grateful :) Just wanted to
let you know.
-c
--
umount: mount disagrees with
15 matches
Mail list logo
