** Summary changed:
- one autopkgtest failure since 219-5ubuntu1
+ plymouth starts too late since 219-5ubuntu1
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (
Fixed in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=0b433ba6d . This will do
fine for vivid.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (
Asked upstream at http://lists.freedesktop.org/archives/systemd-
devel/2015-April/030074.html
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks for confirming. Tentatively closing for now. If anyone still sees
this, please yell.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Hello Simon,
(In reply to Simon McVittie from comment #3)
> (Also, is there any reason to prefer NFS /usr that doesn't apply equally to
> preferring NFS rootfs?)
I'm not sure if root on NFS was ever attempted/supported. You'd
basically need half an OS in your initramfs then? :-)
> The fewer cons
(In reply to Simon McVittie from comment #6)
> How's this? I made the stop command be "echo" instead of "true" so that it
> leaves a hint in systemctl status if someone tries to stop it by hand.
Ah, good one.
> Unfortunately, "systemctl restart dbus" (which was never supported either)
> will now
(In reply to Michael Biebl from comment #1)
> ExecStop=/bin/true was my first idea, but Martin rightfully pointed out,
> that this doesn't influence KillMode, i.e. we need KillMode=none.
> With that KillMode setting, I think we can actually drop ExecStop=/bin/true,
> so what remains is
>
> KillMod
Will have a thorough look after the holidays, a dependency chain like
this might explain it?
getty@.service → systemd-user-sessions.service → remote-fs.target →
network-online.target
Incidentally that affects desktops as well, lightdm is now starting only
after the network is up. This should be
For the record, local users have always been able to reboot the computer
through the indicator (which then invoked logind or ConsoleKit to do the
actual reboot), or even just by hitting the power button. So this isn't
a new capability at all.
--
You received this bug notification because you are
(In reply to Lennart Poettering from comment #12)
> The best way is to fix the few services that really need dbus
> unconditionally to be around to add After=dbus.service. And all is good.
If we go with that approach, then it would IMHO be cleaner to change the
implied "After=dbus.socket" for Type
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
** This bug has been marked a duplicate of bug 953875
Encrypted swap no longer mounted at bootup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
As for what creates the "Before=network.target" for networking.service
(aka /etc/init.d/networking): this is defined in /etc/insserv.conf.
> We should definitely not be blocking network.target indefinitely on
boot waiting for the results of /etc/init.d/networking.
Agreed. Conceptually we should k
reason for the Before=network.target is to ensure
a proper shutdown order.
** Changed in: ifupdown (Ubuntu)
Assignee: Martin Pitt (pitti) => Steve Langasek (vorlon)
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu&id=07d6481d7a7a5
** 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 ifupdown in
I suppose this is the reason:
Apr 01 11:33:03 hostname systemd[1]: Failed to start LSB: AppArmor
initialization.
Apr 01 11:33:03 hostname systemd[1]: apparmor.service failed.
apparmor blocks quite a lot, so we need to fix that in a container.
--
You received this bug notification because you a
Debugged on IRC. For the record, the link in /etc/rcS.d/*networking was
missing. Hence the sysv-generator didn't create a networking.service and
didn't attempt to start it.
I just created a fresh vivid container and the link does exist, and
network is coming up fine for me. Can you reproduce this
Public bug reported:
$ sudo lxc-destroy -n adt-vivid
[sudo] password for martin:
lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev:
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev:
failed
This should be fixed in current vivid.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
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/1376717
Title:
lxc
Public bug reported:
With latest vivid's LXC, starting a vivid container now fails on
mounting the cgroups:
$ sudo lxc-create --name=v -t ubuntu -- -r vivid
$ sudo lxc-start -n v -F
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
systemd 219 running in system mode. (+PAM +AUDI
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1440501
Title:
Can not load mysql-akonadi apparmor profile
Status in akonadi package in Ubun
This is just cosmetical. We actually do want to continue upstart support
at least until the next LTS (and also for Ubuntu touch), so we can't
just rip that out wholesale yet. But it shouldn't produce that confusing
error for sure.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
**
This is just cosmetical, lightdm works anyway.
** Changed in: lightdm (Ubuntu)
Importance: Critical => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1414420
Title:
Steve Langasek [2015-04-07 14:22 -]:
> I'm not sure what you mean by this. We absolutely did block on our network
> interfaces when using upstart; just with a 2 minute timeout for any
> misconfigured interfaces.
Right, but that should only be done by services which depend on
network-online.ta
The idea is that the "Priority: required" init package is always
installed, which depends on systemd-sysv | upstart-sysv. upstart-bin is
history, that's "upstart" now (and as you already found out, upstart-
sysv now contains /sbin/init).
Any idea how "init" got missing on your system?
** Summary
Shouldn't this rather be "sudo update-rc.d networking defaults"? That
won't actually put back a removed symlink as this counts as user change
that needs to be preserved. So the question is still what made this
disappear?
** No longer affects: systemd (Ubuntu)
** Tags added: systemd-boot
--
You
Sherif, anything which actually explains what this bug report is about
is useful. Right now it's not actionable at all, I'm afraid. If you have
an installation which fails to start a display manager, I need the
information from comment #10.
--
You received this bug notification because you are a
There has been no answer to the request for information above for a
month. I'm closing this bug report as in its current form it is not
actionable. I'll reopen this once that information has been provided.
Thank you for your report!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Inva
There has been no answer to the request for information above for a
month. I'm closing this bug report as in its current form it is not
actionable. I'll reopen this once that information has been provided.
Thank you for your report!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Inva
After a boot which does the fsck, can you please do "sudo journalctl -b
> /tmp/journal.txt" and attach /tmp/journal.txt here? Perhaps that says
why it got started. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
*** This bug is a duplicate of bug 1433198 ***
https://bugs.launchpad.net/bugs/1433198
** This bug has been marked a duplicate of bug 1433198
15.04 daily images don't reach X using VirtualBox - VESA error: Cannot read
int vect
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1431107 ***
https://bugs.launchpad.net/bugs/1431107
** This bug has been marked a duplicate of bug 1431107
ordering cycles with lvm2 init script with inappropriate rc2.d links
--
You received this bug notification because you are a member of Ubuntu
Touch
There is a suspend job running, which collides with shutting down (you
can only do one or the other). Do you know what triggered the suspend?
(lid close, indicator, or you didn't request this explicitly). Can you
reproduce this situation? Does suspend normally work for you?
The kernel log only sho
Thanks for your report! Unfortunately the auto-generated stack trace is
totally useless, so I'm afraid there's not much that we can do with this
report; thus I'm closing it. Let's hope the next one looks better :-)
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received thi
The kernel log shows huge gaps in device detection, apparently the
hardware gets locked up during USB detection/enumeration?
[7.292422] input: HDA Intel HDMI HDMI/DP,pcm=7 as
/devices/pci:00/:00:03.0/sound/card0/input16
[ 10.918992] usb 1-3: device descriptor read/all, error -110
[
ged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Summary changed:
- fstab-generator creates incorrect mount units for CIFS
+ fstab-generator interprets backslashes in CIFS mounts
--
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.ne
you use them (i. e. use 1.2.3.4...).
It's best to avoid those at all and use forward slashes for CIFS mounts.
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received th
See also bug 1439109 which is about the missing networking symlink.
--
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/1430675
Title:
fails to set up a bridged network interfa
Vincent Ladeuil reported this on IRC as well, and for him the problem
was that /etc/init.d/networking was disabled. I. e. there is no
/etc/rcS.d/*networking symlink. Timo, Philip, zoolook, can you please
check this?
If you don't have such a symlink, please run
sudo update-r.cd networking remove
For the record, this is how to clean up:
sudo update-r.cd networking remove
sudo update-r.cd networking defaults
Vincent has the same problem, and he mentioned that he has an
/etc/init.d/networking.dpkg-old; that sounds like ifupdown once failed
to upgrade/configure?
** Summary changed:
- N
Sorry, I typoed. The correct commands are:
sudo update-rc.d networking remove
sudo update-rc.d networking defaults
--
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/1430675
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
** This bug is no longer a duplicate of bug 1430675
fails to set up a bridged network interface
** This bug has been marked a duplicate of bug 1439109
Network interface not coming up due to missing /et
*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
Timo confirmed as well, so confirming as a duplicate of bug 1439109.
** This bug has been marked a duplicate of bug 1439109
Network interface not coming up due to missing /etc/rcS.d/*networking
--
You
I uploaded a new ifupdown which cleans this up on upgrades, needs
release team review.
** Changed in: ifupdown (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 ifupdown in U
?bug=750360
Importance: Unknown
Status: Unknown
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Hig
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: lightdm (Ubuntu)
Status: Triaged => In Progress
** Also affects: lightdm (Ubuntu Vivid)
Importance: Low
Assignee: Martin Pitt (pitti)
Status: In Progress
--
You receive
Fixed in upstream trunk: http://bazaar.launchpad.net/~lightdm-
team/lightdm/trunk/revision/2135
** Changed in: lightdm
Status: Confirmed => Fix Released
** Changed in: lightdm (Ubuntu Vivid)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
** Changed in: systemd (Ubuntu)
Importance: Critical => Medium
--
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/1434847
Title:
does not start a display manager
Status in
Public bug reported:
Boot the current live system with systemd: Go to gfxboot, select F6,
press Esc twice, stay in gfxboot, and append init=/bin/systemd to the
command line. The live system will come up, but degraded:
● systemd-machine-id-commit.service - Commit a transient machine-id on disk
** No longer affects: linux (Ubuntu)
--
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/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in AppArmo
*** This bug is a duplicate of bug 1385817 ***
https://bugs.launchpad.net/bugs/1385817
It's invalid (for systemd at least), but not due to a crash, but due to
this:
insserv: warning: script 'bubbleupnpserver' missing LSB tags and
overrides
Marking as duplicate.
** This bug has been marked a
Well, the list of "affected" packages is pretty arbitrary and random --
on affected systems you have to fix the broken third-party init.d
script, or it's never going to work :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
** Changed in: update-notifier (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1409129
Title:
Drop usage of udev-bridge via eve
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Network interface NamePolicy= disabled on kernel command line, ignoring
+ shows confusing warning: "Network interface NamePolicy= disabled on kernel
command line, ignoring"
** Changed in: systemd (Ubuntu)
Luis, that seems to be a different bug/cause now. To confirm, what does
that show right after a clean boot:
sudo systemctl status -l networking
(Please confirm that you still don't have /run/network right after
boot).
--
You received this bug notification because you are a member of Ubuntu
To
According to the dpkg terminal log, the first package that failed was
cgmanager:
Setting up cgmanager (0.32-4ubuntu1.2) ...
Failed to get D-Bus connection: No connection to service manager.
Failed to get D-Bus connection: No connection to service manager.
invoke-rc.d: initscript cgmanager, action
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchp
Public bug reported:
These days the emulator fails to boot:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel devel
$ ubuntu-emulator run devel
[...]
Begin: Running /scripts/local-premount ... [0.190059] mmc0: new SDHC card
at address e118
done.
[0.195316] mmcblk0: mmc0:e118 SU0
$ ubuntu-emulator list
devel ubuntu=20141201,device=20141119,custom=20141201,version=1
I also just checked with devel-proposed, same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://
Reopening the kernel task here. We've carried the "temporary" udev rule
workaround for three releases now; it seems we all agree that it's wrong
(unconditional "unbreak my kernel rule") and makes things even worse
under memory pressure. Is there any better solution in sight? Thanks!
** Changed in:
Automatic fsck has been disabled in the upstream e2fsprogs a while ago
(see
http://git.whamcloud.com/tools/e2fsprogs.git/commitdiff/3daf592646). So
my suspicion is that you have kept your /home partition around for quite
a while and that one was still created with an mkfs.ext4 that enabled
automati
Jamie, Daniel, did you ever get this after the fix in bug 1302264? This
is the typical symptom of logind not working, so if you have that
situation can you please check for a logind crash /var/crash?
** Changed in: compiz
Status: Confirmed => Invalid
** Changed in: unity
Status: Con
This doesn't happen on my system, but this could be a bad interaction
between the GPT and the fstab generator. Can you please run the
following:
mkdir /tmp/fstab; /lib/systemd/system-generators/systemd-fstab-generator
/tmp/fstab x x
mkdir /tmp/gpt; sudo /lib/systemd/system-generators/systemd-gpt-
** Tags removed: verification-done-trusty verification-needed-utopic
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error me
Tom,
ah, sorry about that, I didn't know that the gpt generator also uses the
"late" argument (it wasn't here, but then again it doesn't produce
anything for me). But indeed it seems to produce a swap unit for you,
which explains this bug. Can you please re-do this with
mkdir /tmp/gpt; sudo /li
Thanks for confirming, so this is indeed the case: Your /home has a max
mount count of 35, but all other partitions have -1.
The config file is /etc/mke2fs.conf, as visible in the commit diff. It
was just typo'ed in the commit description.
This was a deliberate behaviour change, so I'm closing th
This also affects 14.04 LTS, although to a slightly lesser degree. In
14.04 we have a patch which does the modprobing for the "cpu" subsystem;
but reportedly this also affects drivers of other platforms, so let's
just backport that more generic upstream fix to cover all cases.
This can potentially
Trusty SRU uploaded to SRU review queue.
** Changed in: systemd (Ubuntu Trusty)
Status: Fix Released => In Progress
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Precise SRU uploaded to SRU review queue.
** Changed in: udev (Ubuntu Precise)
Status: Triaged => 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/1404509
Thanks for the additional data, that helps a lot. I'll forward this to
upstream now. I have an idea how to fix that, but I'd like to discuss it
upstream first.
> (Until your post yesterday, I've had sda3 commented out.)
Was that only in response to that bug? It would be weird if that bug
would st
Sorry, misunderstanding. I restored the previous tags, which seem to be
correct.
** Tags removed: verification-done
** Tags added: verification-done-trusty verification-needed-utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
Forwarded to http://lists.freedesktop.org/archives/systemd-
devel/2015-January/027314.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/1399595
Title:
systemd is activat
** Bug watch added: Debian Bug tracker #772182
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772182
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772182
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
The lxcsyslog.txt attachment might be worth a look though, there are
several cgmanager errors there. "vivid-systemd" is the name of my system
container (standard vivid plus apt install systemd-sysv).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
I suppose the user container runs upstart (from the template), as that's
still the ubuntu vivid default. But I have a feeling it's not even
getting that far; when I start with --logfile /dev/stdout --logpriority
debug it all just seems to be early setup:
$ lxc-start -n v1 --logfile /dev/stdout --l
Public bug reported:
I wanted to test the new lxc with lxcfs. A system container (with
upstart or systemd) works perfectly well now (great!), but user
containers regressed:
$ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64
$ lxc-start -n v1 -F
lxc-start: cgmanager.c: lxc_cgmanager_e
I just booted the current devel-proposed, and it works fine there:
$ snappy versions
Part Tag Installed Available Fingerprint Active
ubuntu-core edge 251- 718fc709559b0b *
I also tried this with rev 219:
sudo ubuntu-device-flash --verbose --revision=2
I installed 211 with
sudo ubuntu-device-flash --verbose --revision=211 core
--output=/tmp/snappy211.img --developer-mode --channel=ubuntu-core
/devel-proposed
booted it, then run "snappy update". There doesn't seem to be a
parameter to specify the version, so I can't upgrade to 219; it starts
I'm running the complete image on tmpfs so it shoudl be lightning fast.
Michael says that the upgrader has crashed, so I can't test an upgrade
from 211 to 251. Does it happen to work for you? Did you still see this
on current images? If so, do you get any apparmor violations or similar?
** Changed
I filed the upgrade hang as bug 1414009.
--
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/142
Title:
systemd-journal: Failed to join audit multicast group: Operation not
$ cat /proc/self/cgroup
10:blkio:/user.slice/user-1000.slice/session-c2.scope
9:memory:/user.slice/user-1000.slice/session-c2.scope
8:freezer:/user.slice/user-1000.slice/session-c2.scope
7:cpu,cpuacct:/user.slice/user-1000.slice/session-c2.scope
6:net_cls,net_prio:/user.slice/user-1000.slice/sessi
Current blockers: bug 1414055, bug 1414063, bug 1414075
--
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/1153671
Title:
Port to python3-launchpadlib
Status in apport package
t seem to be necessary, neither
for upstart nor systemd containers.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Description changed:
When a user logs in, systemd-logind should create cgroups for the user,
with the directory (i.e. /user.slice/user-
** Summary changed:
- login name=systemd cgroup is not owned by user
+ user lxc containers fail to start: login name=systemd cgroup is not owned by
user
** Summary changed:
- user lxc containers fail to start: login name=systemd cgroup is not owned by
user
+ user lxc containers fail to start u
Stéphane Graber [2015-01-25 17:15 -]:
> How are we supposed to run a systemd container on such a system then?
>
> systemd in a container will need to create sub-entries in the
> name=systemd controller.
Yes, that works fine, as the cgroup *directories* are owned by the
user. I just don't want
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1413927
Title:
user lxc containers fail to start
Ah, after a reboot the route now looks cleaner:
default via 10.0.2.2 dev bond0
10.0.2.0/24 dev bond0 proto kernel scope link src 10.0.2.16
and outgoing connections now work. Incoming connections through QEMU
port forwarding is still hanging though, i. e. I can't ssh into the VM..
--
You receive
I'm trying to reproduce this in a VM with two ethernet cards (-net user
-net nic,model=virtio -net nic,model=virtio). Like that it fails with
$ sudo ifup -a
Cannot find device "bond0"
Failed to bring up bond0.
I tried to install ifenslave, is that the package you are using/have
installed too? Wit
I can reproduce the hang with booting systemd.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Tags added: sys
Indeed under systemd I see that /etc/init.d/networking is hanging at
"waiting for bond master bond0 to be ready".
--
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/1414544
Titl
Ah, -redir only redirects to the first DHCP address (10.0.2.15). So the
trick with QEMU is to set up two redirections:
kvm -m 2048 -snapshot -drive file=/srv/vm/adt-vivid-
amd64-cloud.img,if=virtio -net
user,hostfwd=::22000-:22,hostfwd=::22001-10.0.2.16:22 -net
nic,model=virtio -net nic,model=virt
Fixed in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=355bf7059
** 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 syst
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I recommend to call dh_installinit with --no-start. This won't harm the
phone or the boot, but will prevent this failure when you try to install
the package on a machine without android. Note that on a desktop with
upstart it seems to work:
Setting up powerd (0.16+15.04.20150120-0ubuntu1) ...
powe
This fix is contained in the latest lxc in vivid now.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/135
With latest lxc and lxcfs this works now, both system and session
containers with systemd, with systemd on the host.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: lxc (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received th
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-15.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Mauricio Faria de Oliveira [2015-01-26 18:44 -]:
> Would you have any update on the process of resolving this (maybe someone/I
> can help?)
Sure, anyone who wants to look into this is welcome of course. It just
turned out to be much less trivial than I originally thought.
> or its severity (
901 - 1000 of 4146 matches
Mail list logo
