** Changed in: shadow (Ubuntu Bionic)
Status: New => In Progress
** Changed in: shadow (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.lau
Public bug reported:
Currently doing something like:
sudo usermod -a -G snap_microk8s dbeamonte
on a Ubuntu Core system will fail with
usermod: /etc/group.15965: Read-only file system
This is because the existing usermod patches to detect
the extrausers file do not cover this case. Att
** Patch added: "Proposed (untested) patch"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557911/+files/shadow-lp1959375.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
h
** Patch added: "debdiff for the PPA jammy test upload"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557912/+files/shadow_4.8.1-2ubuntu2~ppa1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
My apologizes that this totally was not on my radar. I applied the patch
(thank you!) and moved the code from bzr to git, added a gbp.conf and
pushed to GH for now (but maybe this really should go to salsa instead).
I hope I will be able to release a new .16 release with these changes
(and the most
We created a test PR that uses this core18 snap build in
https://github.com/snapcore/snapd/pull/11015 - we are still running
tests but it seems the error is still there :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syste
Thanks Lukas for providing this revert of
f0831ed2a03fcef582660be1c3b1a9f3e267e656. Using
https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap I can
no longer reproduce the isue.
To make it easier to reproduce what I did:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch
Just for the record, I also did another run with:
https://storage.googleapis.com/snapd-spread-
tests/snaps/core18_20211102_amd64.snap and that also fails right away:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$ g
Fwiw, the patch debian/lp1934147/0001-core-add-a-new-unit-method-
catchup.patch is part of a fairly large patchset
(https://github.com/systemd/systemd/pull/9200/commits) so maybe
something is missing there?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
About the question about Focal/hirsute/uc20 - we have not observed the
issue there.
--
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/1949089
Title:
systemd randomly fails to
I spend a bit of quality time with this bug today and it seems there is (also?)
a kernel dimension to it. I ran the following:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$ git diff
diff --git a/overlord/devicesta
@Dan Thanks, this find about BindsTo is super interesting! It's not
something that snapd writes out, it's curious where this comes from.
--
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
I spend a bit more time bisecting the various core18 snaps to see at
what revision the failure started to become reproducible. Interestingly
I found that it started with r2208 AFAICT. It's all a bit annoying
because it's a race so I don't trust it 100% but the previous r2206 got
2 good runs in a ro
** Attachment added: "cloud-init logs for the "bad" run"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542025/+files/cloud-init-bad-core18-r2208.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Attachment added: "cloud-init logs for the "good" run"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542024/+files/cloud-init-good-core18-r2206.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
I attached the /run/cloud-init and /var/log/cloud-init logs of the
good/bad run - I looked over the diff via "diff -u <(cut -f 4- -d:
/tmp/cloud-init-good-core18-r2206/cloud-init.log) <(cut -f 4- -d:
/tmp/cloud-init-bad-core18-r2208/cloud-init.log)" but couldn't see
anything standing out there (but
Fwiw, it looks like the latest core18 edge build that includes
https://launchpad.net/ubuntu/+source/cloud-init/21.4-0ubuntu1~18.04.1
make the problem go away. It seems https://bugs.launchpad.net/cloud-
init/+bug/1946003 is what caused it.
The old code had a udev rule that would call into the cloud
This also affects "functionfs" that uses
"uid=2000,gid=2000,no_disconnect=1,rmode=0550,fmode=0660 ".
--
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/2012563
Title:
unsuppo
** Changed in: snapd
Status: Fix Committed => Fix Released
--
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/1943077
Title:
snapd fails to autopkgtest on mksquashfs, w
Fwiw, the code has landed in the upstream git repository in
https://gitlab.com/apparmor/apparmor/-/merge_requests/858
--
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/1994146
@Brian Once the archive is frozen this is not entirely trivial anymore
as the command-not-found indexfile is stored in the now frozen archive
mirror.
It seems the easiest way to fix is:
* uploading a higher version in the -updates pocket should fix the problem
automatically, the database code
(C
Fwiw, mysql-8.0 is also affected:
$ dpkg -c libmysqlclient21_8.0.23-3_amd64.deb|grep buildd
drwxr-xr-x buildd/buildd 0 2021-02-11 10:32 ./
[many more]
And some more:
$ dpkg -c libqt5xdg3_3.6.0-1ubuntu2_amd64.deb |grep buildd
-rw-r--r-- buildd/buildd 268440 2021-02-11 21:58
./usr/lib/x86_64
** Package changed: snapd (Ubuntu) => systemd (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/1920107
Title:
Failed messages of sd-umoun show with reboot/shutdown
@rbalint Thanks for this heads up. Unfortunately we are not ready for
cgroups v2. Snapd is working on v2 systems but a lot of the
functionality is not ported. AIUI it requires quite a bit of work on our
side and the two are quite different :/
--
You received this bug notification because you are
@rbalint Do you have a timeline when you plan this? The changes required
make this most likely something we can only tackle during the 21.10
cycle :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.
After discussing this we decided that we will leave cgroups v1 support
for 21.04 because the snapd team will not be able to port all features
to v2 in time. But early in the 21.10 cycle v1 is turned off and snapd
needs to be ported to full v2 support.
--
You received this bug notification because
** Project changed: snappy => snapd
--
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 address changes
on
** Project changed: snappy => snapd
--
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/1712312
Title:
Cannot add secondary group to user
Status in snapd:
Triaged
Status in s
** Project changed: snappy => snapd
--
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/1650688
Title:
timedatectl set-timezone fails on UC16
Status in snapd:
Triaged
Status
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1503680
Title:
dhclient for eth0 does never exit and retries dhcp foerever
Status in s
** Project changed: snappy => snapd
--
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/1965328
Title:
transient scope could not be started error in bionic lxd container
Statu
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
Status in snapd:
** Project changed: snappy => snapd
--
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/1593407
Title:
Guest session cannot run snaps
Status in Light Display Manager:
Confir
** Description changed:
In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
where if a service, started earlier than devices are processed by udev,
does `systemctl daemon-reload`, the system shuts down. This is due to
devices for mounted filesystem temporarily taken dead, w
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 co
** 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 daemon-re
** 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" t
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 b
** 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
t
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 com
** 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 packa
** 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 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 hangin
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"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245665/+files/fix-systemc
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 added:
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 Ubun
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 daemon-relo
** 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
+ sys
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 receiv
** 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 ra
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
http://autopkg
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
'org.freedesktop.sys
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 be
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
https://github.com/systemd/syst
** 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, whi
** 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 subsc
** 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:
[
** 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"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1659534/+attachment/5248602/+files/shadow_4
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 subscr
** 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 Prog
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 i
** 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 ar
** 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
| james@panlong
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 p
** 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 binar
** 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.
ht
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 f
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
--
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 ra
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:
P
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:
Plea
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 Support-system-image-r
** 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
Sta
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 i
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
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/sn
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:
/snap/bi
*** 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 "w
@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
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 pulse
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:
Pref
** Bug watch added: PulseAudio #749
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749
** Also affects: pulseaudio via
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
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 L
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 r
** 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 ex
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
+
** 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 fro
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: Fix Released => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you
** Changed in: systemd (Ubuntu Focal)
Importance: Critical => High
** Patch added: "debdiff for 20.04 with the proposed fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5318599/+files/systemd_244-3ubuntu2.debdiff
--
You received this bug notification because
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
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 || true";
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 packag
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 do
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 in
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)
Impor
** 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 notificati
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-
seeds/+git/ubuntu/commit/?id=2c2f14307069e1554eaba0b3882e8fb41a2c4877
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 ad
1 - 100 of 360 matches
Mail list logo
