** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: Debian Bug tracker #761909
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761909
** Also affects: systemd (Debian) via
http://bugs.de
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=7b9a61f1
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** No longer affects: xorg-server (Ubuntu)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Wily's lxc contains the upstream MP, i. e. it calls /lib/apparmor
/profile-load.
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
htt
Uploaded to SRU review queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1470399
Title:
udev duplicates entries in 70-persistent-net.rules
Status in systemd package i
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu&id=2c83d8ed8e50c3
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
Till, you reported this like 20 times already.. :-)
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1429544
Title:
systemd-logind crashed with SIGABRT in
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug is no longer a duplicate of bug 1499863
systemd-logind crashed with SIGSEGV in __strlen_ia32()
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: M
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus without replying
--
You received this bug notification becau
Please only file one report per issue, using that for the keyboard
problem. This has got nothing to do with systemd, it's most probably
some (mis)configuration or misbehaviour of unity-settings-dameon.
** Summary changed:
- Waking up changes keyboard layout and turns off wifi
+ Waking up changes
Please install the "evtest" package and run "sudo evtest". Pick your
keyboard, press the two brightness keys, and copy&paste the entire
output here. Please also annotate the output so that I can see which
key press triggered which output.
Finally, please include the output of "cat /sys/class/dmi/
Please run this again and select the "Asus WMI hotkeys" device (number
10 in your previous output). I'm fairly sure the brightness keys are on
that, not on the "AT Translated Set 2 keyboard".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you. This needs to be fixed in the kernel driver then, as without
a scan code there is nothing we can do in userspace.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Brightness HotKeys not Detecte
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
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/1501773
Title:
ubiquity hook 'str' object has no a
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug is no longer a duplicate of private bug 1502626
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus wi
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
Right, there's no sign of the watchdog message in the journal (unless
you reported the bug after rebooting the VM). In this case I'm out of
ideas... We can't detect the situation in apport, and it's not a sy
This was perfectly reproducible until 225-1ubuntu4, and got fixed in
225-1ubuntu5. If you can still reproduce this crash (after a fresh
boot), please tell me how. My gut feeling is that the version number of
the recent duplicates is wrong as you probably upgraded to the latest
version (which doesn'
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus without replying
--
You received this bug notification becau
Apparently you uninstalled the apport package? That's what provides
ubuntu-bug, and it's installed by default in Xubuntu.
** Package changed: systemd (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: In Progress => Invalid
--
You received this bug notification because you are a member of
There are no logs here which would show what led to the bad state of
libpam-systemd, and after your dist-upgrade the package is now installed
fine, so we lost the evidence of what went wrong. You apparently used
"apt-get upgrade" before, which doesn't write any further logs (such as
the update mana
** Summary changed:
- package udev 225-1ubuntu5 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
+ package udev 225-1ubuntu5 failed to install/upgrade: Failed to restart
udev.service: Connection timed out
--
You received this bug notificatio
@David: Note that this *only* affects Ubuntu 15.10. Ubuntu 14.04 doesn't
even use systemd yet. You reported the bug against 15.10, so I figure
that's what you had installed at that time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
It's just a warning: the rsyslog package ships
/usr/lib/tmpfiles.d/00rsyslog.conf which also ships a config for
/var/log, so the one in var.conf is ignored.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touc
** Summary changed:
- Duplicate line for path "/var/log"
+ Duplicate line for path "/var/log" warning is shown when rsyslog is installed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Not sure what to do with this then -- I don't think we want to silence
the warning. If you write tmpfiles.d snippets they are useful to know
when something accidentally overlaps. We just know that this particular
instance is expected if you install rsyslog. Closing it as "wontfix"
won't magically m
Pretty please read the title, description, and first comments -- This
report is about showing the "starting version 219" text message during
early boot. This is purely cosmetical, has been silenced in 15.10, and
for sure does not actually break boot, logging in, etc. These effects
are much more li
> or a failure to reach the cloud image server.
The tests work on wily and vivid, so in principle they can talk to the
cloud image server or linuxcontainers.org. It might of course be that
later LXC versions got some proxy fixes or something such. However, the
tests in trusty also worked until Oct
Keeping notes: I did a local QEMU run against trusty release and trusty-
proposed:
adt-run lxc -s --- qemu /srv/vm/adt-trusty-amd64-cloud.img
adt-run --apt-pocket=proposed -U lxc -s --- qemu
/srv/vm/adt-trusty-amd64-cloud.img
They both fail for the same reason: five tests fail due to "ERROR:
Running lxc test against trusty-release in the CI production environment
still works fine (against kernel -65). I do get the hang with running
against -proposed, under otherwise the exact same circumstances.
The dist-upgrade to -proposed does the following:
The following NEW packages will be inst
To completely rule out that it's not the python3.4 regression in trusty-
proposed (bug 1500768) or the (really unrelated) udev fix in bug
1470399 I instead ran it with --apt-pocket=proposed --setup-commands
'apt-get update; apt-get -y install linux-generic' instead of the -U
/--apt-upgrade switch,
** Changed in: systemd (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1495178
Title:
Failed to set wall message, ignoring
Curiously this gets fixed by
https://github.com/systemd/systemd/commit/2cf088b . I now tried all
combinations of setting wall messages or not, timed or immediate
shutdown, and they now all work without crashes.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You re
** Summary changed:
- systemd 226-2 (debian sid) breaks lxc-attach
+ systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
** Package changed: systemd (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I suppose the recent kernel patch
UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected
paths
which got backported to trusty causes this regression. As the same code
is present in later releases, I guess that in v/w lxc has an updated
apparmor profile which allows the operation
Hello Andy, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.7-0ubuntu0.9
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Is there an apt repository for these mariadb packages somewhere, or at
least some debs?
** Bug watch added: Red Hat Bugzilla #1271832
https://bugzilla.redhat.com/show_bug.cgi?id=1271832
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1271832
Importance:
Public bug reported:
I got this crash on today's (20151014) amd64 wily desktop image while
trying to reproduce bug 1506139. I did a manual partitioning with this
layout:
Partition 1: plain ext4 boot partition mounted on /boot
Partition 2: luks-encrypted swap
Partition 3: luks-encrypted btrfs for
Processing triggers for initramfs-tools (0.120ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-4.2.0-16-generic
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: fa
I tried to reproduce this on today's ubuntu desktop amd64 image
(20151014). I think I set up partitions like you described: 1 GB /boot
on partition 1, 1 GB LUKS on partition 2 (and put swap on vda2_crypt), 8
GB LUKS on partition 3 (and put btrfs / on vda3_crypt).
Both during install and after a fe
42-usb-hid.rules got removed in vivid (or so), thus marking the floating
task invalid.
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Bryce, that rule looks fine for a trusty SRU. Please go ahead and
upload. Thanks!
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
h
> This time, sda2 has survived as a valid and operating luks partition.
Then the journal won't show the bits where it destroys it (but it's
still useful for comparison). I'd like to see a journal when it does
destroy the device. One way would be to just keep rebooting until that
happens.
However,
** Package changed: systemd (Debian) => docker (Debian)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1497420
Title:
systemd 226 (moving pid 1 into /init.scope cgroup) breaks
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
Till, I know. As I wrote, there's pretty much nothing we can really do
about this :/ Please stop filing a gazillion duplicates about this, it's
just causing a lot of unnecessary paperwork and manual duplicat
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506800
systemd-timesyncd crashed with SIGABRT in epoll_wait()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on longer kernel lockups
--
You received this bug noti
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506801
systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind c
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506801
systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind c
** Package changed: systemd (Ubuntu) => privoxy (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1507257
Title:
Failed to start Privacy enhancing HTTP Proxy.
Statu
@Scott: bug 1447807 is different.
Ben Thielsen has it exactly right: the init.d script entirely ignores
the return value of start-stup-daemon. It neither has an upstart job nor
systemd unit, so systemd and upstart call the init.d script and rely on
its exit code.
** Package changed: systemd (Ubun
Please be more specific what happens exactly, what you see (perhaps do a
photo or screenshot when it doesn't continue to boot), etc. Does the
"rescue" mode in the boot menu work?
Please also try and boot in verbose mode: In the GRUB boot menu, select
"e", then edit the "linux" line to drop "quiet"
What's the output of "sudo systemctl status NetworkManager-wait-
online.service network-online.target" for you? We do enable this unit by
default, so it should wait (this works fine here and for many other
people I've talked to).
If they are not running, but enabled, then the reason is that mediat
Esokrates: When I do this in a chroot with a proper policy-rc.d (to
suppress daemon starts, which is a must for doing things in a chroot), I
get
Setting up modemmanager (1.4.0-1) ...
invoke-rc.d: unknown initscript, /etc/init.d/modemmanager not found.
invoke-rc.d: policy-rc.d denied execution of s
Olli, Maarten, could you please test the package in vivid-proposed
instead of my PPA, so that we can officially verify this to get it into
vivid-updates? Thank you in advance!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: systemd-bugs
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bug
> mediatomb is After=network-manager.online,
It should certainly be After=network-online.target, I assume that was a
typo?
> are you saying that it *also* has to Wants= it?
Yes. After= is purely an ordering of units, it doesn't start one.
network-manager.target needs to be Wants= (or Requires=)
** No longer affects: lxc-android-config (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1451788
Title:
no modems under systemd
Status in lxc-andr
For vivid it landed in the touch overlay PPA.
** Changed in: ubuntu-touch-session (Ubuntu Vivid)
Status: New => Fix Released
** Changed in: ubuntu-touch-session (Ubuntu Wily)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubu
** Changed in: lxc-android-config (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1451788
Title:
no modems u
** Changed in: lxc-android-config (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1451790
Title:
needs syste
ce: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- systemd creashes by simple typo
+ Assertion crash with "ExecStart=- /path"
--
Yo
Right, this has been subject of countless debates, but it's not going to
change at this point any more.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
Ah, so recovery mode works, but neither the standard nor the upstart
boot entries work?
Your fstab looks as expected, but you didn't attach blkid; now you don't
need to any more, recovery mode's log shows that this part was alright.
Can you go back to the grub boot menu, "e"dit the standard Ubunt
So it looks like NM-wait-online isn't waiting long/hard enough?
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.
FTR: pull in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=7ba2711d (not
sufficient, but should also help)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/102
Ti
Please report bugs with the nvidia graphics driver separately -- for the
third time or so, this report *purely* concerns the cosmetical problem
of printing "starting version 219" at boot, but not any graphics issues.
** No longer affects: ubuntu
--
You received this bug notification because you
Sent proposed patch upstream: http://lists.freedesktop.org/archives
/systemd-devel/2015-May/031711.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1454173
Title:
Asser
I proposed a patch for this upstream:
http://lists.freedesktop.org/archives/systemd-devel/2015-May/031718.html
Iain, it would be great if you could confirm that it works for you as
well? I attach a patched amd64 /lib/systemd/systemd binary, in case
that's useful for you.
** Attachment added: "/li
We got this version in Ubuntu 15.04. The libuuid user does not exist any
more, it got renamed to uuidd. adduser creates system users without a
shell on purpose, as an additional security measure. That's not
something which we want to change.
** Changed in: util-linux (Ubuntu)
Status: New =>
I fixed this upstream:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=35b1078e
and cherry-picked into experimental branch for wily, and vivid branch
for vivid-proposed:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-vivid&id=4c9dbf885925
** Also affects: sy
First patch was nack'ed; second proposal:
http://lists.freedesktop.org/archives/systemd-devel/2015-May/031893.html
Attaching an updated /lib/systemd/systemd with those patches (amd64).
** Attachment added: "/lib/systemd/systemd with proposed fix (v2)"
https://bugs.launchpad.net/systemd/+bug/1
This was apparently reported on a system where Xorg *does* start,
according to LightdmLog.txt. There is one error which looks fishy:
мая 07 15:49:00 hostname systemd[1]: var-lock.mount: Mount on symlink /var/lock
not allowed.
мая 07 15:49:00 hostname systemd[1]: var-lock.mount failed to run 'moun
*** This bug is a duplicate of bug 1448900 ***
https://bugs.launchpad.net/bugs/1448900
** This bug has been marked a duplicate of bug 1448900
enable systemd-importd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syste
Why is one wrong and the other right? I. e. what's the actual bug that's
caused by this layout?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Thanks. If you comment out this line from fstab:
tmpfs /var/lock tmpfs defaults 0 0
do things work again?
Note that this is really broken: /var/lock must be a symlink to
/run/lock, otherwise different programs use different lock directories.
However, it's not really obvious that this is the c
I confirm that when I add such a mount, the system boots into emergency
mode. This is yet another case of mountall silently ignoring errors
instead of failing, and we don't really want to proliferate these bugs.
So I set this to "wontfix" for now. Thanks for your report!
** Changed in: systemd (Ub
Unfortunately the apt logs are fairly useless. Can you please do this:
sudo sed -i '1 s/$/x/' /var/lib/dpkg/info/udev.postinst
sudo apt-get -f install
and then copy&paste the entire output? Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug no
You reported this under upstart, so there are no logs yet to diagnose
the problem. Please boot with systemd, and describe what you see: do you
get an emergency mode root shell? If not, do you get a "login:" prompt
on the text console? If neither, please do a screenshot (with a camera).
Then boot b
sinecure, this bug does not apply to laptops, only to this pre-
production desktop box with a broken lid switch but no lid. Laptops
usually have a working lid switch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
The problem with schroot is tracked in bug 1430557. The original
reporter here already asked to close it, most other distros (all with
systemd, including Fedora, SUSE, Arch, and most importantly Debian) now
default to shared namespaces. Also, nspawn works perfectly well on
Ubuntu and people are usi
Ah, seems man 1 hostname and man 5 hostname contradict here..
** Changed in: systemd (Ubuntu)
Importance: Wishlist => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad
/etc/hostname is not specified to accept comments, lowering severity.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
signee: (unassigned) => Martin Pitt (pitti)
** No longer affects: network-manager (Ubuntu)
** No longer affects: network-manager (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubun
Adding "nofail" to the /etc/fstab entry for /mnt/windows will make the
system boot again for you, if you expect breakage there and having
/mnt/windows is not essential for your system.
All mounts with "auto" but not "nofail" are considered essential for the
system to boot, as everything else would
** Tags added: systemd-boot
** Summary changed:
- While sbuilding in LXC, systemd loops attempting to umount the underlay
+ LXC with r/w sys and udev keeps trying to unmount bind mounts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This is the command line I'm using for test iteration. It's not that
simple, so I want to keep it here in case I ever need it again.
This builds systemd from git, copies it into a "test" container, starts
it, runs the bind mount/umount, and shows the debug log:
schroot -r -c session:schroot-wily-
Refined command line to also verify that the tentative device *does*
move to "dead" once the last reference gets unmounted:
schroot -r -c session:schroot-wily-systemd -- make -j4 && sudo rm -f
/srv/lxc/test/rootfs/lib/systemd/systemd && sudo cp systemd
/srv/lxc/test/rootfs/lib/systemd/systemd && c
New set of proposed patches:
http://lists.freedesktop.org/archives/systemd-devel/2015-May/032030.html
http://lists.freedesktop.org/archives/systemd-devel/2015-May/032024.html
Attached /lib/systemd/systemd with these applied (amd64), for testing.
** Attachment added: "/lib/systemd/systemd with pro
I fixed this upstream:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=139e5336286
This depends on a couple of previous patches, so not that easy to
cherry-pick. If this is urgent/necessary for vivid, I'd apply the
original patch http://lists.freedesktop.org/archives/systemd-
devel/2015-May
I got http://cgit.freedesktop.org/systemd/systemd/commit/?id=2005219
upstream, which is about as far as they want to go. It's not a supported
configuration to have a r/w /sys in a container and run udev. This can't
work. So if you want to manually unmount bind mounts (the second patch),
please drop
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start at boot if ListenAddress is set, because network
interface
ation script returned error exit status 1
** Affects: util-linux (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Changed in: util-linux (Ubuntu)
Status: New => In Progress
** Changed in: util-linux (Ubuntu)
Importance: Undecided
I can't see anything relevant in util-linux, and there are similar
errors for unrelated packages (procps, and udev).
There is one difference in the recent sysvinit which might be related:
Package: sysvinit-utils
+Essential: yes
This was half a merge error, the original justification ("Drop
Esse
After some more back and forth we fixed the remaining issues as well
now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=fcd8b26
http://cgit.freedesktop.org/systemd/systemd/commit/?id=394763f6 (followup
fix for the former)
--
You received this bug notification because you are a mem
u Vivid)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/102
Title:
LXC with r/w sys and udev keeps trying to un
So that was not it, debootstrap is still failing.
** Changed in: sysvinit (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
I recently hit ENOSPC which turned out to be the result of various
syslogs from the current and previous boots totalling up to 30G.
They were filled with messages like
Apr 15 11:22:35 vivid systemd[1]: Unit
var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4
smfmd sounds like a third-party package with a broken init.d script:
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop between service smfpd and procps if started
insserv: loop involving serv
** Changed in: sysvinit (Ubuntu)
Milestone: None => ubuntu-15.05
** Changed in: sysvinit (Ubuntu)
Importance: High => Critical
** Also affects: sysvinit (Ubuntu Wily)
Importance: Critical
Assignee: Martin Pitt (pitti)
Status: In Progress
--
You received th
201 - 300 of 4146 matches
Mail list logo
