Public bug reported:
This happens when updating the system using the "Software Updater".
$ lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libaprutil1-ldap:amd64 1.5.3-1
ProcVersionSignature: Ubuntu
autofs does not need and should not have a strong require for ypbind
(or, even statd)
However, when configured to autostart NFS mounts or to use NIS (!) then
of course it depends on those services.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
autofs does not need and should not have a strong require for ypbind
(or, even statd)
However, when configured to autostart NFS mounts or to use NIS (!) then
of course it depends on those services.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
autofs should depend on statd in upstart
Run:
start statd
to verify
It looks like this is a bug in statd... which is just plain wrong :)
With upstart do you have to teach other services about your service?
eg autofs needs statd. statd says start on (started portmap or mounting
TYPE=nfs)
autofs should depend on statd in upstart
Run:
start statd
to verify
It looks like this is a bug in statd... which is just plain wrong :)
With upstart do you have to teach other services about your service?
eg autofs needs statd. statd says start on (started portmap or mounting
TYPE=nfs)
Public bug reported:
Binary package hint: initramfs-tools
upgrading 9.04 to 9.10
initrd fails with /scripts/init-top/brltty: 19: grep: not found
see:
http://www.mail-archive.com/linux-...@uni-koeln.de/msg02954.html
also countless forum discussions.
it turns out that /usr/sbin/mkinitramfs has
** Patch added: fix BUSYBOXDIR settings
http://launchpadlibrarian.net/47060918/mkinitramfs.patch
--
mkinitramfs doesn't use busybox-initramfs and builds unuseable initrd
https://bugs.launchpad.net/bugs/573282
You received this bug notification because you are a member of Ubuntu
Bugs, which
I reported this on #ubuntu-arm (or similar) whilst compiling arm code
for ubuntu/maemo/mer on the open build service; and someone specifically
requested that I tag it 'arm' when I reported it.
The problem only manifests itself using qemu arm emulation ... OTOH I
guess this is fairly important to
actually this still broke... but less often
so I hit it with a bigger stick:
DEFAULT_ARG_SIZE=(64u * 1024u)
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On a qemu chroot with Ubuntu 9.04 installed:
find /usr -print0 | xargs -0r pwd
produces:
Error loading /bin/pwd
Error loading /bin/pwd
Error loading /bin/pwd
Error loading /bin/pwd
/bin/pwd: ignoring non-option arguments
/usr/src/packages/BUILD/xargs
(pwd is just a
confirmed that reconfiguring xargs with
DEFAULT_ARG_SIZE=(127u * 1024u)
instead of the default: (128u * 1024u)
fixes the problem.
patch to debian/rules :
--- rules.orig 2009-05-05 15:44:19.0 +
+++ rules 2009-05-05 10:54:23.0 +
@@ -36,7 +36,7 @@
I upgraded 8.04 to 8.10 and this affected me.
[EMAIL PROTECTED]:~$ sudo locale-gen en_GB.UTF-8
Generating locales...
en_GB.UTF-8... up-to-date
Generation complete.
[EMAIL PROTECTED]:~$ sudo dpkg-reconfigure locales
perl: warning: Setting
I see this bug upgrading from 8.04 to 8.10
--
Upgrading from dapper to edgy causes locales to stop working during installation
https://bugs.launchpad.net/bugs/63687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I just upgraded to Intrepid.
Hibernate failed in Hardy and I wanted to see if it was fixed.
It wasn't.
It turns out I'd added more RAM and nothing noticed that swap was smaller than
RAM.
I used gparted to resize the swap. That went smoothly. I did
swapoff/resize/swapon from inside gparted.
14 matches
Mail list logo
