Patch in question in Upstream is here [0].
[0]
https://github.com/systemd/systemd/commit/b5d3138f9177bbc3505f42ba073d08d4f90b4888
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
[ Impact ]
On systems where Intel SGX is available, access to a specific devide
node (/dev/sgx_vepc) must be enforced, with a specific permission (0660)
and group (sgx).
This allows KVM-based virtual machines to use such feature (the SGX
"enclaves") in a proper fashion.
@vorlon,
Upon installing the jammy-proposed version of the isc-dhcp-client on a
Jammy instance (4.4.1-2.3ubuntu2.2), I am no longer able to reproduce
the reported issue; running `dhclient` does not get the
resolv.conf/stub-resolv.conf files overwritten.
As of the reported regression, I did not
Hi, Lukas.
Thank you very much for the reply, here. I tested the isc-dhcp-client
in the mentioned PPA on a Kinetic uvt-kvm-based VM, and with it in
place, I no longer see the stub-resolv.conf being overwritten whenever I
run `sudo dhclient`. Indeed, I now see a `resolved-enter` enter-hook
Public bug reported:
[Issue]
On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if
dhclient is executed.
While debugging this, I found the reference on LP#1889068 [0] of the
move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit-
hooks.d/, and this new
Hi. Input from a customer:
[ . . . ]
I just tested a "do-release-upgrade" from bionic to focal and did not get any
errors.
I installed 18.04, installed the nvidia-driver-418 and enabled i386 arch. I
then enable the
bionic-proposed repo and did an update/dist-upgrade, rebooted, and did a
Hi, all.
I obtained feedback from one Canonical customer (with a Support Case
opened just for that), that hit the very same bug and, when testing the
package sitting in -proposed, didn't reproduce the issue anymore.
>From his own words:
"I wasn't able to recreate the auditd problem with the
Changed the status to New, since I was still able to reproduce the issue
on Bionic, using the "patched" network-manager version.
** Changed in: network-manager (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hi, all. I'm afraid I'll need to reopen this bug.
I was able to reproduce the issue on Bionic, using network-manager
1.10.6-2ubuntu1.2. However, when testing this on Eoan, using network-
manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour.
The steps one takes to reproduce the issue,
Public bug reported:
[Impact]
The pgrep -f and pkill -f commands are unable to find processes strings in
processes which are beyond the 4096th character. This often happens with Java
command lines with long classpaths on the command line.
[Test Case]
A quick test to reproduce this is to vi a
10 matches
Mail list logo
