And the output of "ip monitor eth0": http://paste.ubuntu.com/25686711/
...
2: eth0inet 192.168.1.130/24 brd 192.168.1.255 scope global secondary
dynamic eth0
valid_lft 120sec preferred_lft 120sec
local 192.168.1.130 table local proto kernel scope host src 192.168.1.129
Deleted 2:
Fwiw, my current suspicion is that adding the new IP from the dhcp as a
secondary IP is buggy. Secondary IPs will get removed when the kernel
removes the primary IP (see kernels __inet_del_ifa() code).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Or "net.ipv4.conf.all.promote_secondaries=1" in
/etc/sysctl.d/50-ipv4.conf (or similar).
--
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/1721223
Title:
Networkd fail to
As a workaround for now, it looks like with: "echo 1 >
/proc/sys/net/ipv4/conf/all/promote_secondaries" on the device the
problem goes away.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The output if dhclient is running with the same scenario:
http://paste.ubuntu.com/25686791/
--
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/1721223
Title:
Networkd fail to
With ip monitor all: http://paste.ubuntu.com/25686763/
--
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/1721223
Title:
Networkd fail to set ip address between leases if ip
I spend a bit of time debugging this with xnox. Here some of the
results:
# How to reproduce:
I setup a isc-dhcp-server with a fixed IP for my test rpi2 set to default/max
lifetime of 120sec. The rpi2 was connected to the network with the
isc-dhcp-server but unmodified otherwise. Once the pi2
Some more data point are the output of "ip addr":
http://paste.ubuntu.com/25685527/
The interessting part if:
...
3: eth0: mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether b8:27:eb:85:3f:94 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.116/24
Xnox pointed out that the above net.ipv4.conf.all.promote_secondaries=1
is actually a default of systemd (added in
https://github.com/systemd/systemd/commit/ad8bc9ea508740074cead005aa3cfd1ba10a5dac).
This looks like we will enable it for everybody via a systemd SRU.
--
You received this bug
** Also affects: glibc (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Artful)
Importance: High
Status: Fix Released
** Also affects: libseccomp (Ubuntu
Fwiw, this is longer working on zesty and newer:
"""
#include
#include
int main(int argc, char **argv) {
int sys_num = seccomp_syscall_resolve_name("socket");
printf("%d ", sys_num);
}
"""
returns -101 now. I think I know what is going on and will provide a patch
shortly.
--
You
So to summarize: in zesty, artful `scmp_sys_resolver -a x86 socket` will
return: `-101`. The syscalls are still there in the kernel and libc its
just that libseccomp reports a pseudo number again (which it did not in
xenial).
The reason why we are seeing negative syscall numbers from libseccomp
Fwiw, I reported a RFE upstream to warn if networkd is used and
promote_secondaries is unset
(https://github.com/systemd/systemd/issues/7163)
** Bug watch added: github.com/systemd/systemd/issues #7163
https://github.com/systemd/systemd/issues/7163
--
You received this bug notification
We merged https://github.com/snapcore/snapd/pull/4306 which fixes this.
--
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/1734038
Title:
utils don't understand «include
Fwiw, this is fixed upstream now with
https://github.com/systemd/systemd/pull/7167
--
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/1721223
Title:
Networkd fail to set ip
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: initramfs-tools-ubuntu-core (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [TEST CASE]
+ * this will be tested by the snappy team
+ * without this
** Changed in: snappy
Status: Triaged => Fix Released
** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
Status: Triaged => Confirmed
** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools-ubuntu-core (Ubuntu
The shadow package needs to grow support for extrausers group handling.
** Changed in: snappy
Status: New => Triaged
** Changed in: snappy
Importance: Undecided => High
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt ||
https://github.com/snapcore/snapd/pull/5226 <- contians a PR for this
now.
--
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/1771858
Title:
/snap/bin not in default PATH for
I pushed a slightly modified version of this to https://github.com
/shadow-maint/shadow/pull/119
** Bug watch added: Debian Bug tracker #833256
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833256
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Fwiw, I looked at the code of "su.c" from util-linux (because
debian/ubuntu may switch to it, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=833256) and it looks like the bug is not present
there. The su-common.c:modify_environment() code will first
setenv_path() from login.defs and then
** Patch added: "systemd_237-3ubuntu10.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5157097/+files/systemd_237-3ubuntu10.2.debdiff
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
The 16.04 version of systemd had a patch to support the read-only etc.
For core18 we will also need this change because core18 is still not on
a fully writable etc.
I will attach a debdiff against the current bionic version of systemd.
** Affects: systemd (Ubuntu)
Any chance this can be fixed for 18.04.1 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1776218
Title:
New style hook support not robust on removal
Status in apt package
Yes, I will work on this!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1623125
Title:
fixrtc script does not catch "Last mount time: n/a" string
Status in
I uploaded updates for zesty and artful now as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1623125
Title:
fixrtc script does not catch "Last mount time:
It is like ogra said - the snapd team does not care about zesty/artful,
but if it makes the SRU easier we are happy to push to zesty/artful as
well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Package changed: snapd (Ubuntu) => ureadahead (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1743080
Title:
ureadahead exit code 5 not installed
Status in
Public bug reported:
There was a recent change in apparmor
(https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb) that
breaks snapd. The fix is simply to add the
++AssumedApparmorLabel=unconfined line to the service file so that
activation works again.
Attached is a debdiff with a
** Patch added: "possible fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1749000/+attachment/5054183/+files/systemd_237-1ubuntu4.debdiff
** Patch removed: "possible fix"
** Patch added: "Proposed fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1749000/+attachment/5054232/+files/systemd_237-1ubuntu4.debdiff
** Patch removed: "possible fix"
** Changed in: snapd
Status: New => 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/1709536
Title:
snapd 2.26.14 on ubuntu-core won't start in
Public bug reported:
The current version of libuuid is using getrandom() without the
GRND_NONBLOCK flag. This means that in early boot the boot is blocked
until the crng is initialized to "level=1" which on virtual machines may
take some time.
Upstream fixed this in
Thanks for your careful review Robie! As far as security is concerned, upstream
comments on this in edc1c90cb972fdca1f66be5a8e2b0706bd2a4949:
"""
Note that we do not use random numbers for security sensitive things
like keys or so. It's used for random based UUIDs etc.
"""
I looked at the
The above image was build by manually adding the patched util-linux
libuuid.so to the initramfs. The kernel (snap) build system does not use
-proposed so the initrd had to be updated this way to test this on core.
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks for your bugreport. The output of "ps afx" when this hangs would
be great to get an idea why the dpkg process blocks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hey Alex first, sorry for the trouble you have! We do run ~2800 tests
which each branch merged or release. This includes an automatic upgrade
test. Unfortunately the hang is not reproducible for everyone it seems,
neither our automatic tests nor I in a VM have managed to trigger this
hang. But we
We found the root cause now and work on a fix. sorry for the trouble -
Note that this is a "cosmic" specific issue. I'm exploring workarounds
now to unblock you.
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
What we see in the ps output is that for some reason it seems like
systemctl prompts for a password. Which is unusual because apt/dpkg runs
as root so there should be no need for this. Any further hints for us?
Are these desktop or server installs?
--
You received this bug notification because
This is being worked on in https://github.com/snapcore/snapd/pull/5736
--
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/1771858
Title:
/snap/bin not in default PATH for
Public bug reported:
The new command-not-found in bionic supports hints from the package now.
To make command-not-found suggest "python3" on top if a user types
"python" (when that is not installed) the attached debdiff is needed.
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Public bug reported:
The new command-not-found extractor uses hints from the binary packages.
The attached fix adds renaming for python2.7-minimal -> python2.7. We
probably want the same for python3.6,3.7.
** Affects: python2.7 (Ubuntu)
Importance: Undecided
Status: New
** Patch
This got fixed in the cosmic seeds in https://git.launchpad.net/~ubuntu-
core-dev/ubuntu-
seeds/+git/ubuntu/commit/?id=764ab69745c53d8009b7cf9317df1fd9e26bbca2
and in bionic with https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
** Changed in: snapd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
snapd didn't initialize all the seeded snaps
This is now fixed upstream: https://github.com/shadow-
maint/shadow/pull/119 - so the next shadow release should have it. This
makes me also wonder if we should simply cherry pick it for disco.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
as seen in bug 1492327, adduser now works for creating users in the
extrausers db but when it tries to update the GECOS field at the end of
adding a user (interactively and noninteractively) chfn falls over ...
chfn needs similar patches to the other shadow
The bionic version of this systemd update was used on an Ubuntu 18.04
system that ran the full spread test suite (>300 tests). There are
hundreds of mount units created, started, stopped and a bunch of system
services created and removed and tons of daemon-reloads. No systemd
related issues where
** Also affects: shadow (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: shadow (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
** Description changed:
$PATH isn't sourced from /etc/environment, instead the version in
/etc/login.defs is used. (The example below comes from a precise install.)
| james@panlong:~$ echo $PATH
| /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
|
This is "fixed" in disco - the "su" binary does no longer comes from
"shadow" here but from util-linux. And there this bug does not exist.
** Changed in: shadow (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This updated debdiff for xenial ran a full autopkgtest run of snapd on
16.04 without errors.
** Patch added: "Slightly more updated debdiff for xenial with PR#11121"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5249168/+files/systemd_229-4ubuntu21.19.debdiff
--
This is now uploaded (together with #1816753) to xenial-proposed and is
currently in the UNAPPROVED 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/1819728
Title:
The xenial version was also run on i386 with the full snapd testsuite
without issues.
--
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/1819728
Title:
Please backport "fix
** Description changed:
+ TEST CASE:
+
$PATH isn't sourced from /etc/environment, instead the version in
/etc/login.defs is used. (The example below comes from a precise install.)
| james@panlong:~$ echo $PATH
| /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
This is tested via spread in https://github.com/snapcore/snapd/pull/6667
--
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/1778936
Title:
please re-add
We validated the fix via spread in
https://github.com/snapcore/snapd/pull/6595 (both xenial and bionic).
--
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/1819728
Title:
This is now uploaded again into the unapproved 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/1778936
Title:
please re-add Support-system-image-read-only-etc.patch
The previous upload was superseded by a security upload so it never made
it into the archive.
** Patch added: "Updated debdiff with the current SRU upload"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5246027/+files/systemd_237-3ubuntu10.16.debdiff
--
You
The xenial crash turns out to be
https://github.com/systemd/systemd/issues/10716 - there is a fix in git,
I will look into backport this. We will also need a binoic update with
that and a cosmic update.
** Bug watch added: github.com/systemd/systemd/issues #10716
** Description changed:
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-
reload and other commands #8803".
To reproduce its enough to run:
for i in $(seq 50); do
- systemctl
** Patch added: "debdiff with a port of the fix in PR#8803 for bionic"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245782/+files/systemd_237-3ubuntu10.15.1.debdiff
** Summary changed:
- Please backport "fix race between daemon-reload and other commands #8803"
I ran the snapd autopkgtest against a bionic systemd deb build with this
and noticed no regressions.
--
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/1819728
Title:
Please
** Patch added: "Full debdiff for xenial systemd SRU (with correct changelog)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245818/+files/systemd_229-4ubuntu21.18.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This is now uploaded to the ppa:snappy-dev/edge
--
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/1819728
Title:
Please backport "fix race between daemon-reload and other
The xenial build of the updated systemd was tested using a full spread
run with no regressions and a new test was added in
https://github.com/snapcore/snapd/pull/6595 to test that the regression
is fixed
This test shows that core/edge is fixed but core/beta which does not yet
has the fix is
** Description changed:
[Impact]
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-reload
and other commands #8803".
[TEST CASE]
To reproduce its enough to run:
for i in $(seq 50); do
The xenial version of this is NOT ready yet, a second run produced a
CRASH at startup on UC16 with the updated systemd.
** Patch removed: "debdiff with a port of the fix in PR#8803 for xenial"
** Description changed:
- On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
- twice. This race is fixed in systemd upstream: "fix race between daemon-
- reload and other commands #8803".
+ [Impact]
+ On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
This version fixes a subtle bug added by me when de-conflicting the
diff.
** Patch removed: "Full debdiff for xenial systemd SRU (with correct changelog)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245818/+files/systemd_229-4ubuntu21.18.debdiff
** Patch
The version for xenial link in comment #9 did successfully run a full
spread run with UC16. This includes the regression test that systemctl
start is not hanging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I uploaded both the xenial and bionic version to -proposed now.
--
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/1819728
Title:
Please backport "fix race between
** Description changed:
[Impact]
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-reload
and other commands #8803".
+
+ Note that this is a general problem in systemd with daemon-reload and
+
** Patch added: "updated debdiff with updated PR#11121"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5247198/+files/systemd_237-3ubuntu10.17.debdiff
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
** Description changed:
Public bug reported:
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-
reload and other commands #8803".
To reproduce its enough to run:
for i in $(seq 50); do
systemctl daemon-reload &
systemctl
This change is already in the systemd in cosmic+
--
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/1819728
Title:
Please backport "fix race between daemon-reload and other
** Patch added: "Slightly more updated debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5246548/+files/fix-race-daemon-reload-8803.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "debdiff with a port of the fix in PR#11121 to xenial"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5246546/+files/systemd_229-4ubuntu21.19.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I managed to capture the crash in xenial while running the ADT tests for
python-systemd.
** Attachment added: "Crashfile"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5246417/+files/systemd-229-4ubuntu21.18.crash.retraced
--
You received this bug notification
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
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/1819728
Title:
Please backport "fix
Unfortunately we need to pull the xenial update. We see failure like
this:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/i386/p/python-
systemd/20190314_173156_e1077@/log.gz
on various autopkgtest runs. E.g. for
This is the fix for disco
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248602/+files/shadow_4.5-1.1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248603/+files/shadow_4.5-1.1ubuntu2.debdiff
** Patch removed: "debdiff for disco"
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248605/+files/shadow_4.2-3.1ubuntu5.4.debdiff
** Description changed:
+ TEST CASE:
+ - run userdel --extrausers foo on a ubuntu core system
+
+ REGRESSION POTENTIAL:
+ - low, this
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248606/+files/shadow_4.5-1ubuntu1.debdiff
** Changed in: shadow (Ubuntu Xenial)
Status: New => In Progress
** Changed in: shadow (Ubuntu Bionic)
Status: New => In
SRUs for xenial,bionic are uploaded and in the unapproved queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1659534
Title:
userdel doesn't supports extrausers
Status
** Also affects: shadow (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: shadow (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1814355
Title:
snapd remove /usr/local/bin
** Tags removed: verification-done verification-needed-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1659534
Title:
userdel
I can reproduce the autopkgtest failure with:
autopkgtest -sU --apt-pocket proposed python-systemd_234-2build1.dsc --
qemu ~/VM/ubuntu-16.04-32.img
on a local qemu. When it pulls in the systemd from -proposed I see:
...
Failed to execute operation: Failed to activate service
The PR to re-enable the generator:
https://github.com/snapcore/snapd/pull/7031 and updates the test.
--
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/1771858
Title:
When we disabled the generator in snapd we added a regression test
(tests/main/snap-system-env):
https://github.com/snapcore/snapd/pull/6470/files
With the current systemd (not the one in -proposed) I get:
```
grep error: pattern not found, got:
LANG=C.UTF-8
** Also affects: shadow (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support
I uploaded shadow_4.5-1.1ubuntu3_source.changes to eoan. We need to SRU
this to xenial/bionic to have it in UC16/UC18.
** Also affects: shadow (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You
I uploaded SRUs for xenial,bionic,disco now.
** Description changed:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
+
+ [Impact]
+ On ubuntu-core systems we want to be able to manage "extrausers" in the same
The real issue is:
"""
Configurando udev (229-4ubuntu21.21) ...
addgroup: El grupo `input' ya existe como grupo del sistema. Saliendo.
update-initramfs: deferring update (trigger activated)
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing
Enabling "module-switch-on-connect" makes the problem appear again. So
it seems like its this module.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1631161
Title:
Fwiw, commenting out
load-module module-switch-on-port-available
load-module module-switch-on-connect
makes the problem go away for me. I now get "line out" consistently.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
*** This bug is a duplicate of bug 1631161 ***
https://bugs.launchpad.net/bugs/1631161
Public bug reported:
On my freshly installed eoan system I have two output devices:
- HDMI/DisplayPort 2 - GK208 ...
- Line Out - Family 17h ...
When I login into the system pulseaudio always select the
@vanvugt issue 494 seems similar but not close enough, I also tried the
"comment out module-x11-publish" in /usr/bin/start-pulseaudio-x11 but it
had no effect for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
201 - 300 of 349 matches
Mail list logo