Also: the suggested workaround didnt actually work for me. on 15.10 /
wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces:
So why isnt br* already listed by default in the file /etc/resolvconf
/interface-order ? There are many other entries for everything else. And
presumably it should do no harm / detriment.
Should that not be the fix here?
br* bridge interfaces are a common class of network devices and are
being
Public bug reported:
Right.
Well this bug is something I stumbled into today. It turns out that:
Whenever I have invalid /etc/fstab entries, the system fails to start
with systemd.
This can be seen in the debian bug tracker as bug #765586:
Public bug reported:
This isn't supposed to happen...
id@emachines-e520:~$ sudo sh -x /etc/init.d/procps reload
+ PATH=/sbin:/bin
+ SYSCTL=/sbin/sysctl
+ test -x /sbin/sysctl
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r
Hello. This seems to affect me too, on 14.10, docker 1.5.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1423047
Title:
Apport throws Invalid process ID exception and no
5 matches
Mail list logo
