** Changed in: gzip (Ubuntu)
Assignee: (unassigned) => dan purdy (purdydan317)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933516
Title:
gzip: error while loading shared libraries: cannot re
This bug was fixed in the package gzip - 1.6-5ubuntu1.1
---
gzip (1.6-5ubuntu1.1) bionic; urgency=medium
* d/rules: Do not use ASM (LP: #1933516)
-- Dan Streetman Thu, 24 Jun 2021 11:38:02
-0400
** Changed in: gzip (Ubuntu Bionic)
Status: Fix Committed => Fix Released
-
As per Robie's comment, I think we can safely release this as is.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933516
Title:
gzip: error while loading shared libraries: cannot restore segm
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
Thanks - I had missed the Debian bug link.
** Description changed:
[impact]
gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
[test case]
note this only fails on ppc64el
create service file /etc/systemd/system/test-localegen.service with
content:
> > gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
> Please could you expand on this? Under what circumstances are users going to
> be affected by this?
nearly all the systemd services include this setting, e.g.
$ grep -r MemoryDeny *
dbus-org.freedesktop.hostname1.serv
> I also don't understand what's going on here
the asm causes failures on some archs under certain conditions and is
disabled in debian/ubuntu as shown in the linked debian bug. There's
quite a lot of detail in the debian bug if you would like more specific
detail on why the asm shouldn't be used
> [impact]
> gzip/libgzip fails for systemd services using
MemoryDenyWriteExecute=yes
Please could you expand on this? Under what circumstances are users
going to be affected by this?
Specifically our SRU process requires: "An explanation of the bug on
users and justification for backporting the
** Description changed:
[impact]
gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
[test case]
- note this only fails on ppc64el for this test case
+ note this only fails on ppc64el
- can be reproduced with systemd localed-locale e.g.:
- https://salsa.debia
** Changed in: gzip (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933516
Title:
gzip: error while loading shared libraries: cannot restore segment
** Description changed:
[impact]
gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
[test case]
note this only fails on ppc64el for this test case
can be reproduced with systemd localed-locale e.g.:
https://salsa.debian.org/systemd-team/systemd/-/merge
11 matches
Mail list logo
