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
@satish-txt Please refer to comment #8 [0]. A new LP Bug must be
submitted for that error. AFAIU, the error does not affect the problem
we solved with this version of `rasdaemon`.
[0]
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1888423/comments/8
--
You received this bug
Hi.
A customer provided us the feedback from Hirsute's testing. Formally,
on their own words:
"The issue with the Samsung drives is no longer seen with this version,
I'm able to access the drive's registers without issues."
I'm moving on with the verification tagging. Thanks!
** Tags
Greetings!
Aside from Andrew's last request, I see that a very similar issue was
discussed on LP# 1881109 [0] but, at that time, tests with a later
kernel didn't reproduce the issue.
You're running 5.4.0-71 there. Have you been able to reproduce this
using either 5.4.0-73 or 5.4.0-74 (the
Tests on Bionic/Train:
.. While running ceph* packages on 14.2.11-0ubuntu0.19.10.1~cloud4:
$ ceph-kvstore-tool
ceph-kvstore-tool: command not found
.. Upgraded to 14.2.18-0ubuntu0.19.10.1~cloud1 in train-proposed:
$ sudo dpkg -l | grep ceph
ii ceph
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
Adding a minor mention in the LP Bug, as we had a customer being
affected by the issue while installing 20.04.1 on a z14, atop of z/VM
6.4, using unformatted 3390-M9s.
The workaround provided by Herr Heimes on LP Bug #1878596, Comment #21,
has proven to be a workaround for the issue.
I believe
Public bug reported:
[Request]
To be able to call makedumpfile at the from the initramfs, instead of doing so
after rootfs is active/mounted.
[Justification]
Systems with too much memory will demand higher amounts of memory for the
crashkernel parameter, as well as having less systemd units up
Public bug reported:
[Description]
On attempting to install Ubuntu 20.04 at a server using the Intel VROC (Virtual
RAID on CPU) [0] technology, upon selecting the md-XXX device to partition, the
installer fails and loops the user back to device selection.
The errors seen in the subiquity-debug
Tested the collection of sosreport on O7K Units (Nova, Cinder,
Neutron-*), everything working smoothly. Will test with Microstack
soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862830
Title:
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
Bugs, which is
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,
A kernel bump request will soon be sent to debian-installer, to kick the
image re-creation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848236
Title:
Add installer support for iwlmvm adapters
Public bug reported:
[Environment]
Ubuntu 18.04 amd64
sssd + libwbclient0 + libwblclient-sssd (any version)
[Issue]
The libwbclient-sssd package provides a libwbclient.so.0.14.0 library which
enables winbind queries (i.e. wbinfo) to use sssd as a framework.
However, when libwbclient-sssd
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
Public bug reported:
When attempting to load the sss.so module, on a Bionic box running
samba-* on 4.7 and sssd-* 1.16.1, one sees the following in syslog:
winbindd[13099]: load_module_absolute_path: Module
'/usr/lib/x86_64-linux-gnu/samba/idmap/sss.so' loaded
winbindd[13099]: Failed to
17 matches
Mail list logo
