The explicit /bin/systemd-tmpfiles is invoked in the postinst script for
systemd.
Interestingly, it's identical to systemd 229_4ubuntu16 postinst script,
so it was not introduced in 4ubuntu17.
I suspect this issue has been present for a while, but the daily run of
systemd-tmpfiles-clean job resto
I'm an idiot. Of course strace doesn't trace forks by default.
I did a full strace -f (including custom build of strace to stop
truncating arguments) and found more info.
The culprit seems to be /bin/systemd-tmpfiles
During install of the package this is called like so:
/bin/systemd-tmpfiles --
Installing systemd 229_4ubuntu17 also installs the same version of
libsystemd0 and libpam-systemd, so possibly could be those packages, but
as noted, an strace of 'apt install systemd' didn't indictate anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The source package: https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu17
and the diff:
http://launchpadlibrarian.net/306522149/systemd_229-4ubuntu16_229-4ubuntu17.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Xenial, sorry, ubuntu:x is lxd shortcut for xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687015
Title:
229_4ubuntu17 removes group write permissions from /var/log
To manage notifications
Public bug reported:
Steps to reproduce (time senstive, once lxd image is updated with
4ubuntu17, I expect this won't work)
lxc launch ubuntu:x test
lxc exec test -- ls -ld /var/log # shows 775 perms
lxc exec test -- apt update
lxc exec test -- apt-cache policy systemd
lxc exec test -- apt insta
Some more info:
lxd is writing the the hostname into cloud init metadata file before
boot, so the data is on disk before networks starts up. Whether cloud-
init can access this early I am unsure.
Also, I double checked this on yakkety, and the problem remains.
Thanks
--
You received this bug n
** Description changed:
-
- When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the
initial dhcp is always the hostname 'ubuntu', and this is recorded in the
dnsmasq's dhcp leases file.
+ When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the
+ initial dhcp is
Public bug reported:
When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the
initial dhcp is always the hostname 'ubuntu', and this is recorded in the
dnsmasq's dhcp leases file.
Presumably the dhcp is done before the container's hostname is set. A
restart or dhcp renew seems
Looks like a fix is in progress upstream: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=766419#23
** Bug watch added: Debian Bug tracker #766419
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766419
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
FWIW, installing to single btrfs disk, and then rebalancing/converting
to RAID, worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382242
Title:
ubiquity crashes when installing to btrfs ar
Same problem with whole disk partitions.
Gonna try installing to one disk and rebalancing after install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382242
Title:
ubiquity crashes when installing
Public bug reported:
Installing to a pre created/scanned btrfs whole disk array crashes
Created with
sudo mkfs.btrfs -L raid0 -m raid1 -d raid0 /dev/sd{c,d,e,f}
/dev/sdc is chosen as /, not formated
Only other specified partion was /boot on completely different drive,
sda1
Filesystem mounted
This is an issue in trusty, and affects squid-deb-proxy as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205086
Title:
lxc-net dnsmasq --strict-order breaks dns for lxc non-recursive
namese
Peter's fix works for me, until it's updated anyway
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038429
Title:
update-software-center crashed with order (MRO) for bases
SafeConfigParser, object
Currently, I can't reproduce. The original issue was found using a guest
account using DejaDup. Repeating on my machine (11.10), ubuntu-sso-client logs
in fine in Guest and my user accounts, with 2 factor required on my SSO
account. Will try on Precise shortly.
Currently, the API has no support
** Changed in: canonical-identity-provider
Assignee: (unassigned) => Simon Davy (bloodearnest)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/957436
Title:
Ubuntu SSO client can
17 matches
Mail list logo
