Before finding this bug report I had also determined that the timeout
set in /usr/share/initramfs-tools/scripts/local-premount/resume was at
fault.
The patch above corrects the behaviour completely.
--
Usplash timeout too low in script/local_premount/resume : stop usplash
https://bugs.launchpad.
** Attachment added: "patch for AuthNetLDAP.pm"
http://librarian.launchpad.net/4887409/AuthNetLDAP.pm.diff
--
incorrect references to Apache2::Const
https://launchpad.net/bugs/66655
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Public bug reported:
Binary package hint: libapache-authnetldap-perl
This bug effects both the libapache-authnetldap-perl and libapache-
authznetldap-perl packages.
The following to files incorrectly reference the perl module 'Apache2::Const'
as just 'Apache':
/usr/share/perl5/Apache/AuthNetLDA
** Attachment added: "patch for AuthzNetLDAP.pm"
http://librarian.launchpad.net/4887411/AuthzNetLDAP.pm.diff
--
incorrect references to Apache2::Const
https://launchpad.net/bugs/66655
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
This sounds like you need to adjust the libvirtd apparmor profile.
Edit
/etc/apparmor.d/abstractions/libvirt-qemu
and add the following line:
/usr/bin/kvm-balloon rmix,
--
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification
** Tags removed: bios-outdated-1903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1118447
Title:
Race condition with network and NFS mounts causes boottime hang
To manage notifications about this b
I can confirm this bug on different hardware with completely up to date
BIOS and firmware.
The race condition we are seeing is being reported from varied sources
on different hardware over a significant period of time so I think it is
very unlikely to be effected by BIOS of firmware versions. I be
A cleaner way of mounting the nfs shares than Josep provided is
something like what I have below. It looks for whether the nfs server
responds to a ping rather than the default route and will retry 3 times
with a 3 second timeout each time. It also checks all nfs mount points
listed in /etc/fstab w
Unfortunately I'm not going to be able to test as requested in the short
term as the systems involved are in production. I will see if I can
replicate it on some virtual machines but again it could be a while
until this is possible.
While I also understand the preference for up to date BIOS it sho
Since this has not been fixed in lucid I personally believe that the
status cannot be listed as fix released. maverick is not LTS and is
therefore not suitable in many server environments where iSCSI would be
used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
10 matches
Mail list logo
