How does this affect policykit-1-gnome? You just added the task without
giving any explanation. Also, that package is structurally entirely
different from policykit-1 itself, so this can't possibly have a similar
problem. Hence, if you see a bug with pk-gnome, please file a separate
report about it
At first sight I thought this was a duplicate of bug 1504897, but that
doesn't seem to be it. If lxc-net.service fails, then the problem is
something else.
** Project changed: lxc => lxc (Ubuntu)
** Summary changed:
- Upgrade to Ubuntu 15.10 Broken
+ Upgrade to Ubuntu 15.10 Broken: lxc-net.servi
This looks like a bug in vim's debian/rules:
doko | the indep and arch targets are run in parallel
pitti | ah, it never sets DH_OPTIONS=-a or -s, just -i
** Package changed: pkg-create-dbgsym (Ubuntu) => vim (Ubuntu)
** Changed in: vim (Ubuntu)
Assignee: Martin Pitt (pitti) =>
Steve Langasek [2015-10-22 18:11 -]:
> > * If we really want to dump, we could investigate into sendfile. I'm not
> > * entirely sure that it works with data coming in via stdin, but it's
> > * worth a try as we would avoid the kernel -> userspace copy.
>
> This is an interesting suggest
The "Failed to reset devices.list" is known and mostly harmless
(prohibited by LXC's apparmor profile).
** Package changed: systemd (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https
Do you have a chance to replace this in /lib/systemd/system/systemd-
update-utmp-runlevel.service:
ExecStart=/usr/bin/strace -fvvs1024 -o /run/update-utmp.trace
/lib/systemd/systemd-update-utmp runlevel
and add this line
Environment=SYSTEMD_LOG_LEVEL=debug
? Then please boot and attach the jour
You can also do these modifications in a running instance, then
systemctl daemon-reload
systemctl restart systemd-update-utmp-runlevel
to avoid the reboot (might be difficult with nova boot)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
** Changed in: upstart (Ubuntu)
Importance: Critical => Medium
** Changed in: upstart (Ubuntu)
Status: Triaged => In Progress
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: init-system-helpers (Ubuntu)
Status: Tria
work-manager (Ubuntu) => wpasupplicant (Ubuntu)
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed => In Progress
** Changed in: wpasupplicant (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Also affects: wpasupplicant (Ubuntu Xenial)
Importance: High
** Changed in: policykit-1 (Ubuntu 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 policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1447654
Title:
install
** Project changed: apport => apport (Ubuntu)
--
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/1510091
Title:
ubuntu-bug in wily fails to open a bug page when reporting bugs
> Oct 26 14:05:27 juju-wily-lxc-template strace[7043]: This program
should be invoked by init only.
Meh, sorry. Can you please try
ExecStart=/usr/bin/strace -Dfvvs1024 -o /run/update-utmp.trace
/lib/systemd/systemd-update-utmp runlevel
instead (i. e. adding the -D option)? Also, after that ple
Can you please modify /usr/lib/python3/dist-packages/apport/ui.py after
"def open_url(self, url):" to add this as the first command:
print(' opening URL: %s' % url)
then run ubuntu-bug again, and see which URL it tries to open?
If you run "xdg-open http://www.launchpad.net"; in a term
That sounds like the sddm display manger crashes on startup. Please boot
back with the default systemd option, wait until the graphical system
stops trying to start (blinking text cursor), then press Ctrl+Alt+F2.
You should see a "login:" prompt where you can log in instead. In this
text mode, run
Wrt. suspend there is no structural change between 15.04 and 15.10, in
both cases you were already using a direct kernel sleep without pm-utils
when you use the "K" menu.
This sounds like some kernel/driver bug which one of the pm-utils quirks
is working around. Can you please "cd /usr/lib/pm-util
Do you still have the system in that state? I'm afraid the logs are
rather useless -- According to DpkgHistoryLog.txt you started the
upgrade on 2015-10-23 22:34:14, but JournalErrors.txt is from the
following day, and does not contain useful info. DpkgTerminalLog.txt
does not have timestamps, so
** No longer affects: util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498162
Title:
unable to make backup link of `./usr/sbin/uuidd' before installi
** Changed in: apport (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: apport (Ubuntu Xenial)
Assignee: Marc Deslauriers (mdeslaur) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Wrong package; fixed in xenial in
https://launchpad.net/ubuntu/+source/wpa/2.4-0ubuntu4
** Package changed: wpasupplicant (Ubuntu Xenial) => wpa (Ubuntu Xenial)
** Changed in: wpa (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
Published new upstream release https://launchpad.net/apport/trunk/2.19.2
which includes the fix.
** Changed in: apport
Status: In Progress => Fix Committed
** Changed in: apport
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
@Mathieu: Is enabling "AutoEnable" something we want to do and is
generally safe?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570
Title:
BLE pairing fail
Status in b
I'm running wily LXC on wily (or now xenial) pretty much every day, so
this isn't very straightforward to reproduce. lxc's own autopkgtests
also do that, and they run in the cloud in a wily instance, pretty
similar to your's.
I tried a wily cloud image, created an LXC container, and started it,
wh
I tried that user-data (minus the extra packages: and
ssh_authorized_keys: as they are irrelevant) on the current wily cloud
image with QEMU, and I get:
[ 13.799851] cloud-init[1010]: Cloud-init v. 0.7.7 running 'modules:config'
at Wed, 28 Oct 2015 08:11:33 +. Up 13.12 seconds.
[ 14.18982
I read up on juju-local, and tried this in a clean wily amd64 cloud
image:
sudo apt install -y juju-local
juju init
juju switch local
juju bootstrap
I'm not entirely sure what I'm supposed to do now; there is a "juju
machine add" command, but this doesn't accept custom user data. But it
sounds l
Cheryl Jennings [2015-10-28 13:59 -]:
> 2 - However, I thought adding in After=cloud-config.target would ensure
> that it wouldn't start until after cloud-init completes?
Not really, I'm afraid. TL;DR: this doesn't work that way, is prone to
deadlocks, and rather hard to understand.
Long-wind
mplate, i.
e. that container never stops.
+ (Note: Martin Pitt could not reproduce this yet with these steps)
** Description changed:
Frequently, when creating an lxc container on wily (either through --to
lxc:#, or using the local provider on wily), the template never stops
and errors out
erate with
juju destroy-service ubuntu
juju destroy-machine 1
sudo lxc-destroy -n juju-wily-lxc-template
→ then you can re-run "deploy".
At some point this should hang on the creation of juju-wily-lxc-template, i.
e. that container never stops.
(Note: Martin Pitt could not re
@Jason: What seb128 was asking is that you said "related issue is bug
1508697", but 1508697 is *this* bug. I. e comment #1 refers to itself.
I haven't investigated this much yet, but it seems two things are
competing here:
* /usr/lib/tmpfiles.d/dbus.conf will create the /var/lib/dbus/machine-
i
Ah, thanks Simon. As you currently seem to manage bluez
(https://code.launchpad.net/~bluetooth/bluez/bluez5-upgrade), can you do
this change too?
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ub
Simon McVittie [2015-10-29 11:55 -]:
> > systemd doesn't inself create /etc/machine-id when missing, which it
> should.
>
> I think the solution to "my system-imaging setup isn't working" is to
> get that bug (presumably a systemd bug?) fixed - this one is rather
> minor by comparison. Do you
Thanks. Reassigning to the kernel then.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Ah, thanks! This looks like
https://github.com/systemd/systemd/issues/1505, a bug that's rather hard
to track down. I haven't seen it actually affecting version 225 as the
functionality that triggers this isn't used anywhere in the distro; but
you might have some third-party package installed which
I tried that command (on current xenial, you didn't specify an Ubuntu
release/package version), and it works fine:
$ machinectl pull-raw
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
Download of
https://cloud-images.ubuntu.com/trusty/current/trusty-server-
This is another instance of a libdevmapper upgrade problem:
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.90-2ubuntu1_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.90-2ubuntu1) over
(2:1.02.77-6ubuntu2) ...
Preparing to unpack .../libudev1_219-7ubuntu6_amd64.deb ...
Unpacking lib
e-id not created if missing
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should
be created if missing, but is unsure why this doesn't
You want/need to set the "noauto" option in fstab; otherwise you say
"this must be mounted for the system to boot", and that's what it times
out on. Also, please do not set "uhelper=udisks2" in fstab, that's
quite wrong. If you use udisks to mount the external USB then you don't
need the fstab ent
Changed in: rsyslog (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 rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1484027
Title:
systemd-tmpfiles-clean warns a
** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Vivid)
** No longer affects: systemd (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
Can you please enable this PPA and check whether boot is now working?
https://launchpad.net/~pitti/+archive/ubuntu/sru-test
This patch has worked for me, it definitively fixes the boot failure
with the exact same symptoms that you see; but I can't reproduce it on
225, just on (unpatched) 227; but
** Changed in: gobject-introspection (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1511047
Title:
package
Naz Ahmed [2015-10-31 8:30 -]:
> Applied the patch successfully but failed to reboot with the same
> symptoms, created journal1.txt please find attached herewith. On second
> attempt systemd worked fine.
It's expected that you need a reboot before things will actually work.
(If in doubt, do t
eploy".
At some point this should hang on the creation of juju-wily-lxc-template, i.
e. that container never stops.
(Note: Martin Pitt could not reproduce this yet with these steps)
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscrip
So obviously one of the quirks in /usr/lib/pm-utils/sleep.d works around
this kernel bug. We need to find out which. Can you please move the
files in that directory to some other place one by one and do a "sudo
pm-suspend" / resume cycle until it starts failing? That's the "magic"
hook then. Which
@stef: OK, I unduplicated your bug 1492850, let's continue the debugging
there.
** Summary changed:
- No wifi connection after suspend with systemd
+ No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
--
You received this bug notification because you are a member of
This is applied in the xenial version now.
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/145000
** Changed in: software-properties (Ubuntu)
Status: Triaged => Invalid
** Changed in: software-properties (Ubuntu Utopic)
Status: Triaged => Invalid
** Changed in: ubuntu-translations
Status: Triaged => Fix Released
--
You received this bug notification because you are a me
This bug only affected utopic, which is EOL now, so closing.
** Changed in: systemd (Ubuntu Utopic)
Status: Triaged => Won't Fix
** Changed in: null-and-void
Status: New => Invalid
** Changed in: systemd-shim (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigne
g
> this bitesize-bugfix (there) should enter "wily-updates"
It's 8 days now, so ready to be released; the SRU team should do that
soon (but they might avoid releasing updates on Fridays).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www
Will have to wait, as wily has libmicrohttpd in universe.
--
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/1480952
Title:
Enable journal-remote
Status in systemd package in
FTR, I tried the above lxc patch locally, and it does not resolve the
reboot bug in a xenial container. I. e. "sudo reboot" in such a
container still fails during very early boot due to a cgroup setup
error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Specifically, the output is
Rebooting.
systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK
+SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID
-ELFUTILS +KMOD -IDN)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to Ubuntu
Public bug reported:
Even after fixing bug 1497420 rebooting containers with systemd >= 226
(i. e. with supporting unified cgroups) does not work. Build a standard
xenial container (using the ubuntu template; e. g. "adt-build-lxc ubuntu
xenial"), start it:
sudo lxc-start -n adt-xenial -F
then
I'm setting this to high as this breaks autopkgtesting on armhf quite
badly.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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.n
That did not fix reboot yet. I filed bug 1514690 as it's a different
root cause apparenlty.
@Serge: there's nothing that should "stick around", it's a reboot after
all and everything including pid 1 gets restarted. It just seems that
the second boot can't create the init.scope cgroup as the "outsi
FTR, same behaviour with Serge's lxcfs "testing" branch with cgfs.
--
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/1514690
Title:
rebooting container with systemd >= 226 fails
Presumably you don't have dbus installed in your container.
--
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/1477130
Title:
timedatectl fails inside container
Status in sys
Thanks for your report! Let's discuss/fix that on the upstream side to
get the relevant developers.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of
Sponsored the patch for xenial. Let's give this some maturing there
first.
** 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 Ubuntu.
https
This got fixed/worked around upstream in
https://github.com/systemd/systemd/commit/1e603a482f57edb and will be in
228.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You receive
Many thanks Serge for figuring that out!
--
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/1514690
Title:
rebooting container with systemd >= 226 fails to create /lxc/adt-
xeni
This bug was fixed in the package gpgme1.0 - 1.6.0-1
Sponsored for Jackson Doak (noskcaj)
---
gpgme1.0 (1.6.0-1) unstable; urgency=medium
* New upstream release.
-- Daniel Kahn Gillmor Thu, 17 Sep 2015
03:40:48 -0400
** Changed in: gpgme1.0 (Ubuntu)
Status: New => Fix Re
Package got sponsored already, unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of real mounts.
Stat
2015-09-22 22:28:47 ERROR juju.service.systemd service.go:145 dbus
enable request failed for service "juju-db-ubuntu-local": Unit name
/var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service is
not valid.
What is juju trying to do here? Indeed this isn't an unit *name*, it's a
path to
** Changed in: systemd (Ubuntu)
Status: Confirmed => 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/1512323
Title:
devices on devel-proposed/ubuntu do n
Thanks Steve for pointing out /proc/cpu/alignment! Yesterday I tried to
reproduce this on an armhf box without success, but with "echo 4 >
/proc/cpu/alignment" this reproduces perfectly well. I'll forward your
patch upstream.
--
You received this bug notification because you are a member of Ubu
** Tags removed: verification-needed
** Tags added: verification-done
--
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
I cleaned this up a bit and forwarded to
https://github.com/systemd/systemd/pull/1911 .
Without this patch, about a third of the unit tests fail with SIGBUS.
With this fix, only ./test-dhcp{,6}-client still SIGBUS, apparently not
due to siphash24. I'll take a look at this as well.
--
You receive
It's still in siphash, due to a similar problem with the out argument:
0x2a02a9e8 in siphash24_finalize (out=0x2a065229 "", state=0xbefff970) at
src/basic/siphash24.c:182
182 *(le64_t*)out = htole64(state->v0 ^ state->v1 ^ state->v2 ^
state->v3);
I'll follow up on the upstream PR.
I fixed the unaligned out parameter now in the upstream PR. 228 is
around the corner, so the simplest way would be to let this land
upstream and get fixed through a new upstream version, but if this turns
out to cause further blocking crashes I can also cherry-pick it.
--
You received this bug no
Bug 1516265 is not a regression, it looks like a local misconfiguration.
I followed up there.
Can folks who are affected by this please check if this update fixes
resuming, so that we can release this fix?
** Tags removed: verification-failed
--
You received this bug notification because you ar
Most likely this failed in the addgroup call. Can you please open a
terminal, run
sudo addgroup --quiet --system netdev
and copy&paste the result here?
** Tags added: bot-stop-nagging
** Changed in: wpa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Public bug reported:
In ScalingStack ppc64el instances, console-setup.service fails:
$ sudo systemctl status -l console-setup.service
● console-setup.service - Set console keymap
Loaded: loaded (/lib/systemd/system/console-setup.service; static; vendor
preset: enabled)
Active: failed (Resu
> the only place where an unaligned 'out' argument is passed to
siphash24_finalize() in practice is the test case
No, also in networkd. Anyway, fixed upstream in
https://github.com/systemd/systemd/commit/dbe81cbd2a9 . A more robust
fix for the main issue now landed as well (avoiding the malloc, wh
No, this was more subtle, its the setting of duid->en.id in
https://github.com/systemd/systemd/commit/dbe81cbd2a9#diff-
893ccaa839a00a7a16a80dbc02631270L54 . This was caught by the two DHCP
test cases. That struct uses ((attribute __packed__)) unions with an
uint32_t preceeding the "id" field, and
ot;rb")))'
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a m
FTR, this was moved to init-system-helpers in bug 1442228. Can't say I'm
happy about this, but that's what it is right now.
--
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/151
Ah, right. Can you try again with
sudo addgroup --system netdev; echo $?
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1516265
Title:
package wpasupplicant 2.4-0ubuntu3
When using the old-style /etc/udev/rules.d/70-persistent-net.rules
schema this is an unavoidable race condition. Our udev package has a
patch to try and make the best of it
(http://anonscm.debian.org/gitweb/?p=pkg-
systemd/systemd.git;a=blob;f=debian/patches/Revert-udev-network-device-
renaming-imm
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=0a815a26024
** 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.
htt
+ systemd: TypeError in networkd test
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1516009
I cannot reproduce this. In both current 15.10 and current Xenial "sudo
shutdown -P 9:35" worked fine. Can you please:
- run "sudo systemd-analyze set-log-level debug"
- start "sudo journalctl -f" in one terminal
- in another terminal, run that command, check the exit code ("echo $?") and
cop
signee: (unassigned) => Martin Pitt (pitti)
--
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/1517426
Title:
[trusty] lxc: lxc now depends on lxcfs which is only in backports
I mitigated this by adding this beauty to the worker.conf's setup
commands:
sed -i '/^deb.*-backports/d' /etc/apt/sources.list `ls
/etc/apt/sources.list.d/*2>/dev/null || true`
A more elegant fix would be to tell apt-get source to somehow respect
the apt pinning, i. e. get the source from the
** Information type changed from Private to Public
--
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/1499863
Title:
systemd-logind crashed with SIGSEGV in __strlen_ia32()
St
If you think this is a bug in systemd-backlight, the questions in
comment #5 still apply.
** 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 Ubuntu.
htt
Can you please be more specific what exactly happens here?
$ cat /proc/sys/net/ipv4/conf/tun0/forwarding
1
$ sudo systemctl start systemd-networkd
$ cat /proc/sys/net/ipv4/conf/tun0/forwarding
1
Is that the setting you mean? How to reproduce the disabling of
forwarding? Apparently it's more tha
Ah, thanks for confirming. This indeed applies to interfaces which
networkd configures; man systemd.network documents this quite clearly.
> Having the bridge setup tool, modify the configuration of all
potential outgoing interface to allow forwarding seems completely wrong
to me
Full ack. Such sc
Raising priority; on second thought this is actually interfering with
configuration. Forwarded to
https://github.com/systemd/systemd/issues/1411 , I'd like to change this
upstream if at all possible.
** Changed in: systemd (Ubuntu)
Importance: Wishlist => Medium
--
You received this bug notif
Upstream reply/justification for current behaviour:
https://github.com/systemd/systemd/issues/1411#issuecomment-144338862
** Changed in: systemd (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Fixed in trunk r3013.
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: apport (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https:/
Adjusting bug title after IRC discussion, see upstream issue summary. We
need something like http://paste.ubuntu.com/12625613/ .
** Summary changed:
- networkd: Don't reset forwarding unless told to do so in config
+ Provide script to enable IP forwarding
--
You received this bug notification b
** Also affects: apport (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification becau
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
** 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
It is much simpler to just set
/proc/sys/net/ipv{4,6}/conf/all/forwarding to 1, as that updates all
conf/iface/forwarding and /proc/sys/net/ipv4/ip_forward. I. e. we just
need
for f in /proc/sys/net/ipv*/conf/all/forwarding; do
echo 1 > $f
done
--
You received this bug notification because y
Public bug reported:
consolekit has been dead upstream for a long time. Ubuntu moved to
logind in saucy (13.10), and we don't support consolekit any more. There
are a few packages which still depend on it, most notably openssh, lxdm,
and lxsession{,-logout}. For Ubuntu 16.04 we really should get r
This approach doesn't work after all, see
https://github.com/systemd/systemd/issues/1411#issuecomment-144975442
So changing back to the original title.
** Summary changed:
- Provide script to enable IP forwarding
+ networkd: Don't reset forwarding unless told to do so in config
--
You receive
With just the default apparmor profile from above I get these AA
violations in dmesg:
[889413.230615] type=1400 audit(1443963008.728:498): apparmor="DENIED"
operation="mount" info="failed flags match" error=-13
profile="lxc-container-adt" name="/sys/fs/cgroup/" pid=6897 comm="systemd"
flags="ro
Public bug reported:
This spawned from
https://plus.google.com/u/0/+MartinPitti/posts/JE8be51XRZy : lxc's
autopkgtests currently fail on armhf/ppc64el where we run autopkgtests
in an LXC container
(http://autopkgtest.ubuntu.com/packages/l/lxc/wily/armhf/). This isn't a
bug in LXC itself, but I sta
Stèphane asked me to try with this, and it doesn't help:
lxc.mount.entry = proc dev/.lxc/proc proc create=dir,optional 0 0
lxc.mount.entry = sys dev/.lxc/sys sysfs create=dir,optional 0 0
I also tried with a completely unconfined LXC profile, that still fails
-- it just hangs eternally after
This is trivially reproducible on an amd64 desktop (I'm running wily,
the production machines run vivid) with
adt-build-lxc ubuntu wily
echo "lxc.aa_profile = unconfined" | tee -a /var/lib/lxc/adt-wily/config
adt-run lxc --- lxc -s adt-wily
so setting to "triaged".
** Changed in: auto-pack
101 - 200 of 4146 matches
Mail list logo
