** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521728/+files/grep_3.7-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: "grep_3.7-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521729/+files/grep_3.7-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
http
Add upstream NEWS file diff.
One change that upstream felt relevant enough to point out, outside of bug
fixes, was a change to a Windows only option.
** Attachment removed: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files
A quick guess would be the problem is glibc upstream commit
13c51549e2077f2f3bf84e8fd0b46d8b0c615912, combined with upstream commit
a26918cfda4bc4b9dad8aae1496e3ef7cbb63d96 setting
__ASSUME_TIME64_SYSCALLS based on the *build* time kernel (not runtime
kernel), and since our build farm runs a kernel
> The local systemd-resolved fails to resolve the name so client
applications return failures. Most notably it shows up in web browsers
but also for apt package updates.
still not following you on why it's causing systemd-resolved to fail to
resolve the name.
the new socket graveyard helps avoid
One possibility that's starting to grow on me is adjusting grep to go
back to using the built-in regex instead of getting it from glibc. This
causes some size bloat (+80k on amd64) but that might be tolerable.
Proof of concept:
https://launchpad.net/~dbungert/+archive/ubuntu/grep-lp-1940999
--
** Changed in: systemd (Ubuntu Groovy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1923485
Title:
unable to reconize Asgard NVME with sh
since the patch to fix this relies on conservative_rename(), which isn't
present in bionic, as well as this bug being mostly an annoyance that
can be ignored, i'm marking as wont-fix for bionic
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Won't Fix
--
You received this bug
ill be useful in the future. However,
> before forwarding, maybe we should get the fix right here first :)
OK, when we have agreement on the fix I will forward.
> > +Last-Update: Aug-24-2021
> This should use ISO format according to the spec please
> (https://dep.debian.net/deps/dep3/
included in impish in version 248.3-1ubuntu4
** Changed in: systemd (Ubuntu Impish)
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/bu
decided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received t
included in impish in version 248.3-1ubuntu4
** Changed in: systemd (Ubuntu Impish)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Hirsute)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned)
** Changed in: systemd (Ubuntu Bionic)
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/1934147
Title:
systemd leaks abandoned sessio
included in impish in version 248.3-1ubuntu4
** Changed in: systemd (Ubuntu Impish)
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/bug
** Changed in: grep (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940999
Title:
FTBFS against glibc 2.34
Status in grep package in
** Attachment added: "grep_3.7-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520321/+files/grep_3.7-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
http
** Patch added: "upstream-ChangeLog.diff"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520323/+files/upstream-ChangeLog.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https
This summary file is the differences to the debian directories between
3.6-1 and 3.7
** Attachment added: "changes.summary"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520322/+files/changes.summary
--
You received this bug notification because you are a member of
To address this I propose picking up the new version of grep.
** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files/grep_3.7-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a
> we should be careful to ignore NICs with randomly generated MACs (see
bug 1936972).
ugh nics with LAA?
yeah, it can be hard to 'uniquely' identify a nic, especially since it's
so common to clone macs for bonds, bridges, vlans, and in some cases
even duplicate hw devices with the same nic (e.g.
Public bug reported:
The package grep failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .
The failure is in automated test, as follows:
stack-overflow: failed test: grep never printed "stack
Public bug reported:
'test-regex' fails when building grep against glibc 2.34.
Per commentary from grep upstream at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069,
the test failure can be attributed to skew between the glibc built-in regex and
the one that is found in the grep source code.
** Description changed:
[impact]
when talking to upstream nameservers, systemd-resolved limits its
advertised max packet size as 512 in its edns0 opt. However, one of the
primary benefits of edns0 is to allow using packet sizes larger than
512, which is the pre-edns0 max packet size.
> The server answers and then resolved sends an ICMP Destination Unreachable
> (Port Unreachable) response!
> This breaks name lookups frequently.
I'm unclear on how/why you are connecting these two statements...can you
explain why it's breaking name lookups?
** Changed in: systemd (Ubuntu)
systemd/udevd appears to be working exactly as advertised, using the
phys_port_name when it's provided by the device's kernel driver; should
this be marked invalid for systemd, or is there actually some change
needed there?
--
You received this bug notification because you are a member of Ubuntu
> When will we upload the changes to -proposed?
i'll upload this week, so hopefully it can be released next week. The
focal point release is this week, so review of the upload may be
delayed, but hopefully not much.
--
You received this bug notification because you are a member of Ubuntu
Touch s
(Ubuntu Bionic)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: systemd (Ubuntu Focal)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: systemd (Ubuntu Hirsute)
Importance: Low
t; In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
> This build will be used for official systemd-245.4-4ubuntu3.12 package
?
not that specific build, no, but I do queue up patches there before
uploading so this should be fixed in the next upload for focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Can you check the systemd build in this ppa to see if it fixes the leak for you?
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
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
Thank you Brian.
I will follow up with the close upon migration.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1939750
Title:
Please merge 7.74.0-1.3
Status in curl package
** Changed in: systemd (Ubuntu Impish)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Hirsute)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Groovy)
Assigne
Public bug reported:
Debian version 7.74.0-1.3 cherry-picks a fix for a command line API
breakage that would be unexpected in a minor version release.
Please help merge.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
https://github.com/curl/curl/issues/6321
** Affects: curl (Ubuntu)
ing.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: systemd (Ubuntu Bionic)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: systemd (Ubuntu Focal)
Importance: Medium
Assignee: Dan
> The "default bionic install" uses only netplan yaml and
/etc/systemd/network/ is empty.
yes, but netplan creates .network config files named in a deterministic
way so you know what the name of the networkd file it creates will be. I
don't think netplan currently has a mechanism to include keep-
> Now I need to have IP and gateway in two files - /etc/netplan/01-netcfg.yaml
> and
> /etc/systemd/network/10-netplan-ens160.network
to clarify, don't do that, you should create a systemd-networkd 'drop-
in' instead of copying/modifying the file.
For example, if the networkd config filename for
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Undecided
** Changed in: systemd (Ubuntu Bionic)
Importance: Low => Undecided
--
You received this bug notification because
For clarity, I explicitly added SRU release targets and marked them as
either invalid (for bionic, since the file doesn't exist there) or wont-
fix (as explained in the description).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
g against Debian to remove the file.
** Affects: procps (Ubuntu)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: procps (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Affects: procps (Ubuntu Focal)
Importance: Unde
With any SRU, it's important not to break existing users, so we can't
rely on users upgrading the kernel along with systemd; it needs to
continue to work without breaking if they upgrade systemd, but choose
not to upgrade the kernel.
In focal since it's only adding new entries, there should be no
For hirsute, what about existing users, should the patch retain the old
matches? Like this:
--- a/hwdb.d/60-sensor.hwdb
+++ b/hwdb.d/60-sensor.hwdb
@@ -288,9 +288,11 @@ sensor:modalias:platform:HID-SENSOR-2000
ACCEL_LOCATION=base
sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnLat
> There are more details regarding this issue and may be commit refs at
> https://github.com/systemd/systemd/issues/17012
I'm aware of that as noted in my updates to the description, but that
doesn't actually fix this inside unprivileged containers, which is the
only place I can reproduce this.
Rasmus are you able to test with the systemd build from this ppa to see if it
fixes the problem for you:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
> so is there something else not working in focal?
as noted in the [scope] sru template section this is fixed by upstream
commit f6f4f5fe5395a57f10dd446c7266c53f0673eaac which isn't in focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "10-test.yaml"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5514117/+files/10-test.yaml
** Description changed:
[impact]
number of statically defined addresses for an interface in systemd-
networkd is limited
[test case]
No
Deepika, Frank, is this happening for you inside an unprivileged
container, or some other environment?
I'm able to reproduce this in a container, but it appears still broken
with upstream systemd, so I'm confused by Frank's comment 2. Also, it
isn't intermittent at all for me, so maybe you're see
** Description changed:
[impact]
number of statically defined addresses for an interface in systemd-
networkd is limited
[test case]
Note: this only occurs in a container; this is not reproducable in a VM
or bare metal.
Configure netplan with the attached yaml file (TBD:
ntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: systemd (Ubun
> https://github.com/home-assistant/operating-system/issues/896
yes the upstream commit to fix this does look like what would cause
this, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
** Changed in: systemd (Ubuntu)
Status: Invalid => 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/1800836
Title:
systemd-networkd doesn't process IPv6 RA proper
> Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.
can you attach journalctl output from a full boot reproducing the
problem? I used your exact ntp config and it works fine for me, though
the systemd-time-wait-sync.service does of course stay 'activating'
I opened bug 1938058 for the problem of moving systemd-time-sync-
wait.service into the systemd-timesyncd package, leaving this bug just
for looking at your (possible) problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
Public bug reported:
[impact]
systemd-time-wait-sync service never completes when systemd-timesyncd
package is not installed
[test case]
remove the systemd-timesyncd package and enable the systemd-time-wait-
sync service, and reboot. Check status of the service to see it's stuck
in 'activating'
> because configuration in /lib/modprobe.d/ overrides configuration in
/etc/modprobe.d/
well, not quite.
kmod reads files from the dirs in this order:
/run/modprobe.d/
/etc/modprobe.d/
/lib/modprobe.d/
any duplicate files, with the exact same name in multiple directories,
will ignore the same-na
multiple patches shouldn't ever be cat'ed into a single file; that is
awful. One patch file per actual patch.
This fails because quilt allows fuzz, while dpkg-source doesn't, and it
shouldn't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
This is almost certainly because you don't have the systemd-timesyncd
package installed, or you don't have the systemd-timesyncd service
enabled.
On a very quick glance, it seems the systemd-time-wait-sync service
should have been bundled into the systemd-timesyncd package when it was
split from t
erties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6
Router Solicitation client
```
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => New
** Chan
buntu Bionic)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you
This fix was reverted for Bionic and Focal, so please note that this bug
does still exist in those releases and will not be fixed.
--
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/b
** Patch added: "lp1937117-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512599/+files/lp1937117-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Attached debdiffs for b/f.
Note that Bionic only needs a revert of the patch for the original bug,
but Focal requires the patch revert plus an additional small patch to
restore the previous behavior, due to other patches added for bug
1664844.
--
You received this bug notification because you ar
** Patch added: "lp1937117-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512598/+files/lp1937117-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Note that the *proper* way to place eth0 into a bridge while also being
under systemd-networkd management is to create a .netdev for the bridge
and assign eth0 to it, e.g.:
$ cat 10-br0.netdev
[NetDev]
Name=br0
Kind=bridge
cat 10-netplan-eth0.network
[Match]
Name=eth0
[Network]
DHCP=ipv4
LinkL
> This backport to 18.04 LTS broke all our OpenStack compute nodes
I've opened bug 1937117 to revert this fix, however keep in mind your
networkd configuration is incorrect and should be fixed as you will have
problems later if you continue to mix systemd-networkd management of
interface(s) as wel
ce: Undecided
Status: Invalid
** Affects: systemd (Ubuntu Bionic)
Importance: Critical
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: systemd (Ubuntu Focal)
Importance: Critical
Assignee: Dan Streetman (ddstreet)
Status: In Progres
something appears to have stopped or restarted your dbus service, which
will cause widespread problems on the system; you'll need to attach more
complete logs for any further debug
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
can you provide steps to reproduce the problem?
--
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/1930738
Title:
network configuration failed on reboot
Status in systemd pac
** Changed in: systemd (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
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/1934981
Title:
systemctl suspend-then-hibernate
thanks, marking verified
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
you need to use the --user parameter when you want to list user
services, e.g.
$ systemctl list-units --user --type=service
by default, only system services will be listed.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a mem
** Description changed:
+ [impact]
+
+ systemd may leak sessions, leaving empty cgroups around as well as
+ abandoned session scopes.
+
+ [test case]
+
+ on a system where the user has a ssh key that allows noninteractive
+ login to localhost, and also has noninteractive sudo, run:
+
+ $ for i
** Bug watch added: github.com/systemd/systemd/issues #20198
https://github.com/systemd/systemd/issues/20198
** Also affects: systemd via
https://github.com/systemd/systemd/issues/20198
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
ubuntu@test-ppc-b:~$ dpkg -l|grep gzip
ii gzip 1.6-5ubuntu1
ppc64el GNU compression utilities
ubuntu@test-ppc-b:~$ sudo systemctl daemon-reload
ubuntu@test-ppc-b:~$ sudo systemctl start test-localegen.service
ubuntu@test-ppc-b:~$ s
ubuntu@lp1931578-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
ubuntu@lp1931578-f:~$ networkctl status ens8 | grep Activation
Activation Policy: down
ubuntu@lp1931578-f:~$ networkctl status ens8
ubuntu@lp1931578-g:~$ dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
ubuntu@lp1931578-g:~$ networkctl status ens8 | grep Activation
Activation Policy: down
ubuntu@lp1931578-g:~$ networkctl
ubuntu@lp1931578-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
ubuntu@lp1931578-h:~$ networkctl status ens8 | grep Activation
Activation Policy: down
ubuntu@lp1931578-h:~$ networkctl status ens8 | grep Required
ubuntu@lp19
marking as verified for focal based on above feedback
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
root@lp1858210-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
root@lp1858210-f:~# timedatectl list-timezones | grep Eastern
root@lp1858210-f:~#
root@lp1858210-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.8 amd64
root@lp1858210-g:~# dpkg -l systemd | grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
root@lp1858210-g:~# timedatectl list-timezones | grep Eastern
root@lp1858210-g:~#
root@lp1858210-g:~# dpkg -l systemd | grep systemd
ii systemd246.6-1ubuntu1.5 a
root@lp1858210-h:~# dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
root@lp1858210-h:~# timedatectl list-timezones | grep Eastern
root@lp1858210-h:~#
root@lp1858210-h:~# dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.2 amd64
> Upgraded to systemd 245.4-4ubuntu3.8 on ThinkPad P17, but this issue
is still exist.
you may be seeing some other problem, you should open a new bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
ubuntu@lp1928200-f:~$ cat /etc/binfmt.d/TestFormat.conf
:TestFormat:M::XX::/bin/true:F
ubuntu@lp1928200-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.6 amd64system and service manager
reboot to pick up change...
reboot again to show issue...
[ OK ] Reached target
root@lp1894622-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
root@lp1894622-f:~# man systemd-resolve
No manual entry for systemd-resolve
root@lp1894622-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.8 amd64
root@lp1894622-g:~# dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
root@lp1894622-g:~# man systemd-resolve | head -1
No manual entry for systemd-resolve
root@lp1894622-g:~# dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.5 am
root@lp1894622-h:~# dpkg -l systemd| grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
root@lp1894622-h:~# man systemd-resolve | head -1
No manual entry for systemd-resolve
root@lp1894622-h:~# dpkg -l systemd| grep systemd
ii systemd247.3-3ubuntu3.2
> that was the atime
yep, really no way around updating the atime, as systemd of course needs
to access the file to check if the content is the same or not
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
> Unfortunately the ppc maas seems down right now
product engineering has access to PPC systems in maas?!? sigh...that
sure would be nice for sustaining engineering to have access to also :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
+ [impact]
+
+ suspend-then-hibernate not possible using systemctl
+
+ [test case]
+
+ configure a system to allow suspend-then-hibernate but not hybrid-sleep,
+ e.g. by editing /etc/systemd/sleep.conf to set
+ AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Assignee: Dan Streetman (ddstreet)
Status
** Description changed:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
see original description for ipv6ra-re
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
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.
ht
** Description changed:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
- see original description
+ see origina
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
> If I understand correctly the fix will go in the latest Bionic
packages?
I think it's very unlikely that the very recent, and rather large,
patchset will get backported back to the relatively old and much
different codebase in bionic. I haven't looked at it in detail yet
though.
--
You receive
I have this queued up for hirsute, with a test build here:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
it seems to fix the issue for me, please let me know if it doesn't work
for you, I plan to upload systemd either this week or early next week
--
You received this bug notification b
Other than the obvious approach of enabling systemd-userdb for Ubuntu,
which is a much larger discussion/decision, I think there are really
only 2 ways to address this:
1) Include drop-in conf files for systemd-logind and systemd-udevd to remove
the networking sandbox
2) add configuration documen
** Also affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1934393
Title:
systemd-logind network access
ok it looks like this *might* be upstream bug 16156, which unfortunately
was just very recently fixed, so backporting that to bionic may be
difficult.
I'll mark the bug and take a look but even if it is possible to backport
the fix, it will likely take a while.
** Changed in: systemd (Ubuntu)
marking wontfix for groovy, as a backport of this size is unlikely to
happen before groovy reaches end of life this month.
** Changed in: systemd (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Bion
it looks like you're seeing this problem inside an lxc/lxd container,
not on bare metal, is that correct?
--
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/1928733
Title:
Sta
301 - 400 of 3372 matches
Mail list logo
