@Paul or @Tobias, would you be able to provide a bit more information on
your environment in a discourse thread at
https://discourse.ubuntu.com/c/lxd/? That would help us hash out a
reproducer. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Michael, could you provide which LXD version you are running? The LXD
snap rev you are using (27037) doesn't seem to be the latest available
and we, in theory, have fixed the issue in LXD 5.0/stable so maybe the
fix is just a refresh away.
--
You received this bug notification because you are a
Noble SRU verification:
Download the package from launchpad (not yet published in -proposed):
$ wget https://launchpad.net/ubuntu/+source/lxd-
installer/4ubuntu0.1/+build/28436117/+files/lxd-
installer_4ubuntu0.1_all.deb
$ lxc launch ubuntu-minimal-daily:24.04 u1
$ lxc file push
** Description changed:
[ Impact ]
- * If the LXD is not pre-created and/or the primary user isn't member of
- it, lxd-installer will fail to install LXD with a cryptic permission
- denied error.
+ * If the LXD group is not pre-created and/or the primary user isn't
+ member of it,
** Description changed:
[ Impact ]
* If the LXD is not pre-created and/or the primary user isn't member of
it, lxd-installer will fail to install LXD with a cryptic permission
denied error.
[ Test Plan ]
Create a test instance:
$ lxc launch ubuntu-minimal-daily:24.04 u1
** Description changed:
+ [ Impact ]
+
+ * If the LXD is not pre-created and/or the primary user isn't member of
+ it, lxd-installer will fail to install LXD with a cryptic permission
+ denied error.
+
+ [ Test Plan ]
+
+ Create a test instance:
+
+ $ lxc launch ubuntu-minimal-daily:24.04 u1
Public bug reported:
linux-image-extra-virtual currently depends on linux-image-generic which
depends on too much when you consider it's use in VMs.
linux-image-generic comes with unneeded bits like the Intel/AMD
microcodes, linux-firmware and thermald packages which are most of the
time
** Changed in: lxd (Ubuntu)
Status: Incomplete => Confirmed
** Bug watch added: github.com/canonical/lxd/issues #13420
https://github.com/canonical/lxd/issues/13420
** Also affects: lxd via
https://github.com/canonical/lxd/issues/13420
Importance: Unknown
Status: Unknown
Here's how to reproduce this in a LXD VM:
Download Ubuntu 24.04 Desktop image into ~/Downloads
Import the ISO
$ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso
24.04-desktop --type=iso
Prepare a LXD VM
$ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c
@sergiodj, it's not a proper SRU/MRE verification but this
5.9-0ubuntu0.22.04.1 is running fine on my home lab. If I run into any
problem with it, I'll report back here. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2060676 ***
https://bugs.launchpad.net/bugs/2060676
** This bug has been marked a duplicate of bug 2060676
login: remove pam_lastlog.so from config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I just tested 5.21/stable and couldn't reproduce as it properly disable
the /proc/sys/kernel/apparmor_restrict_unprivileged_userns and
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined that would
otherwise have caused those denials.
Marking as incomplete until you can reproduce with
@Bartosz it seems you were lucky with 24GB ends being with a multiple of
16KiB (ZFS uses K and G to mean KiB and GiB btw):
$ lxc config device override testvm root size=24GB
Device root overridden for testvm
$ zfs get -p volsize default/virtual-machines/testvm.block
NAME
Lena, thanks for that MRE! It passes some operational tests on my own
setup: primary/secondaries with TSIG, some with views, some zones with
inline DNSSEC signing and with RFC 7706/8806 local root zone copy.
I only tested with Jammy hosts so with 1:9.18.24-0ubuntu0.22.04.1
--
You received this
Thanks for the follow-up!
** Changed in: lxc (Ubuntu)
Status: New => 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/2060965
Title:
liblxc is missing in 24.04
To manage
> The one performance improvement (that I didn't benchmark): "Make
compression libraries dynamically loadable" (it's from January, not
April).
Should apparently make the initialization quicker. Nice to see this
coming from a reputable source (@redhat.com) ;)
--
You received this bug
Public bug reported:
If `lxd-installer` cannot figure which LXD snap channel to use, it
currently defaults to pulling from `latest/stable`. `latest/stable` is a
moving target as new LXD versions are pushed to it on a monthly basis.
`lxd-installer`'s target audience are those casually running
Marking as fix released as it was included in snapd 2.62, thanks!
** Changed in: snapd (Ubuntu)
Status: New => 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/2046379
Title:
The problem is not with a Raspberry Pi as that works fine:
ubuntu@ubuntu:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu Noble Numbat (development branch)"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
@enr0n, could you share `snap changes` as well as `snap info lxd`,
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not handled and lxd snap not
Thank you both!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053192
Title:
geoipupdate should be moved to universe
To manage notifications about this bug go to:
The telepathy-haze package is no longer shipped in the archives. It's
not in Focal which is the oldest supported release. Marking as
incomplete for autoclosing in a few days.
** Changed in: telepathy-haze (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
libgnomeprint is no longer shipped in the archive after Precise, as
such, marking as incomplete (can't mark as won't fix) for autoclose in a
few days.
** Changed in: libgnomeprint (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058303
Title:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058302
Title:
Public bug reported:
When the host uses a manually compiled LXD where binaries were not
stripped, the `lxd-agent` can be ~31MiB big. This binary is copied
inside the VM guest when the VM boots up. This copy operation can fail
as the tmpfs in the VM is mounted with `size=25MiB`.
This binary is
Public bug reported:
This was originally reported at https://github.com/lxc/incus/issues/484
which is recopied here (s/incus/lxd/):
On Red Hat based VMs using SELinux, we seem to be occasionally hitting
lxd-agent startup issues due to systemd not being able to execute the
agent binary.
This is
Thanks Dan, that prompted me to also call out that's something that
manifests only on distro upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd-agent-setup cannot be started
** Summary changed:
- lxd-agent-setup cannot be started
+ lxd-agent-setup cannot be started after a distro upgrade to 24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
https://github.com/canonical/cloud-init/pull/4970 contains a proposed
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055219
Title:
`zpool status` called even if not installed in a container
Public bug reported:
It seems that cloud-init tries to use `zpool status ` whenever
`/dev/zfs` exists. This can causes some bogus warnings if the zpool
command it not available despite that `/dev/zfs` existing.
Here is how to reproduce:
```
lxc launch ubuntu-daily:22.04 v1 --vm
sleep 30
lxc
The workaround from #71 worked almost perfectly out of the box, I've
only seen 1-2 windows staying under the dock. I probably simply need
bump the delay a bit from the default value.
Thanks a lot @popov895. @ballogy, thanks for working on this with
upstream!
--
You received this bug
@enr0n, yes, I did restart systemd-networkd after creating
/etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf.
If you want to reproduce, the steps outlined in the bug descriptions
should provide you with a simple reproducer.
--
You received this bug notification because you are a
@enr0n, the proposal to add:
bridges:
br0:
interfaces: [vlan1]
To the network config defeats the purpose. The goal is to not have to do
double configuration. The bridge is define in LXD, the vlan1 only in
netplan.
The other proposed fix of `KeepMaster=true` snippet in
I got the initial assessment wrong, thanks Heinrich for clearing up that
confusion :)
Here is what happened here:
On Jammy, lxd-agent-loader (0.5) is configured to start lxd-agent.service when
the multi-user.target was reached coupled with a
This was fixed in ca-certificates version 20211016 which is what Jammy
released with. As of today, all Ubuntu releases from Bionic onward ship
20230311 so marking as fix released.
** Changed in: ca-certificates (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Nowadays, btrfs snapshots can only be taken by the owner of the source
subvol. https://btrfs.readthedocs.io/en/latest/ch-mount-
options.html#btrfs-specific-mount-options:
> Historically, any user could create a snapshot even if he was not
owner of the source subvolume, the subvolume deletion has
@kip, it seems the problem was merely a configuration issue on your
machine (missing SSL cert file), not a bug in NGINX or NGINX's package.
As such, we probably don't need to look further into your logs but if
you want to take a look, they should still be available for you to
consult with
@kip, it should in theory not have crashed the installer. Only the
nginx(-*) package(s) should be left unconfigured. You can check that
with "dpkg -l | grep -v ^ii", it should show you which packages need
attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
MySQL 5.1 has long been EOL in Ubuntu and upstream. Please open a new
bug if MySQL 5.7 or MySQL 8.0 as shipped in currently supported Ubuntu
version still have the problem.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
This has long been fixed.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Confirmed => 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/779670
Title:
The usage of --defaults-file
@Jan, indeed before replying to you I opened
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1970440 ;)
@Paul, I am assuming you are referring to the "not well maintained" part
of my comment so let me clarify. Ubuntu being a "frozen distro" (package
versions are normally set in stone at
Hello Holbok,
It looks like your system is booted with `ipv6.disable=1`:
Apr 26 08:28:53 kvmf kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-109-generic
root=UUID=a5928baa-1a87-4f79-88a2-eab3489fdea1 ro net.ifnames=0
biosdevname=0 ipv6.disable=1 maybe-ubiquity ipv6.disable=1
@Jan, while I understand the convenience of `apt install`, Wordpress is
unfortunately not well maintained in Ubuntu so I would recommend doing a
manual installation of an upstream supported version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ubuntu-archive, would it be possible to add `wordpress` the sync
blocklist/blacklist, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970440
Title:
wordpress should be removed from the
Public bug reported:
The just released Ubuntu 22.04 ships with wordpress 5.8.3 which is
already outdated as 5.8.4 was released addressing 1 bug and 3 security
problems, see https://wordpress.org/support/wordpress-
version/version-5-8-4/#maintenance-updates
It seems that nobody from the community
Looks like the missing bits were re-added in Bionic HWE kernel version
5.4.0-108.122~18.04.1. This allowed confirming with the recently
released -109 version:
root@bionic-vm:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@bionic-vm:~# uname -a
Linux bionic-vm
Public bug reported:
# Steps to reproduce
1) Install Chromium's snap
snap install chromium
2) Monitor logs
journalctl -o cat -f --grep chromium
3) Start Chromium
journalctl will be filled with errors due to some syscalls not permitted
by the seccomp policy, like those:
Apr 14 11:18:14
Here is the syscall number => name mapping on amd64:
312: sys_kcmp
314: sys_sched_setattr (so also covered in LP: #1900679)
330: pkey_alloc
** Description changed:
# Steps to reproduce
1) Install Chromium's snap
snap install chromium
2) Monitor logs
journalctl -o cat -f --grep
Thanks Athos, I can confirm the fix from you PPA deals with the problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968200
Title:
squid (GnuTLS flavour) links with OpenSSL libs
To manage
Looks like this was fixed as it now (rsync 3.2.3-8ubuntu3 from 22.04
dev) says:
man rsyncd.conf:
> A chroot-enabled module should not have this parameter set to false unless
> you're using a "name converter" program or you've taken steps to ensure that
> the module has the necessary resources
`yelp man:rsync` works fine on Ubuntu 20.04 with rsync version
3.1.3-8ubuntu0.3 so marking as fix released, thanks!
** Changed in: rsync (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello David, Ubuntu 14.10 was released a long time ago and is long end
of life. Are you still able to reproduce the issue on a supported
release? I'll mark the bug as Incomplete until you can report back.
Thank you!
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received
*** This bug is a duplicate of bug 279557 ***
https://bugs.launchpad.net/bugs/279557
This bug was filled a long time ago so it is probably fixed. Also, as
Hans noted, this looks like a dup of LP: #279557 so I'll mark it as
such. Please re-open if that is still a problem, thanks!
** This bug
The error message is now clearer (IMHO of course):
$ rsync
rsync://cdimage.ubuntu.com/cdimage/releases/hardy/alpha-6/hardy-desktop-i386.iso
rsync: change_dir "/releases/hardy/alpha-6" (in cdimage) failed: No such file
or directory (2)
rsync error: some files/attrs were not transferred (see
Ubuntu Natty (11.04) was a long time ago and since it was reported as
fixed in that release, it means all still supported releases should be
good.
** Changed in: rsync (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Looks like rsync got that option in the end as this is what I get from
18.04's version:
# rsync --help | grep copy-devices
--copy-devices copy device contents as regular file
# dpkg -l| grep rsync
ii rsync3.1.2-2.1ubuntu1.4
amd64
** Description changed:
Something in Ubuntu's squid build causes it to link with OpenSSL's
libssl.so.3:
root@jammy:~# apt-get install -y squid
root@jammy:~# dpkg -l| grep -w squid | grep GnuTLS
ii squid 5.2-1ubuntu3
amd64
Public bug reported:
Something in Ubuntu's squid build causes it to link with OpenSSL's
libssl.so.3:
root@jammy:~# apt-get install -y squid
root@jammy:~# dpkg -l| grep -w squid | grep GnuTLS
ii squid 5.2-1ubuntu3amd64
Full featured
Your comment #13 is what hinted me. I've been messing with openssl
lately and noticed an annoying message about .rnd but only on Bionic
machines ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@paelzer, upstream OpenSSL stopped using RANDFILE a while ago, I've
linked a MR to drop that directive from swtpm's patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968131
Title:
Starting VM
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/swtpm/+git/swtpm/+merge/418865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968131
Title:
Starting VM with UEFI
@paelzer, you made me revisit this and I can confirm that Focal+ is
fixed, only Bionic is still affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581864
Title:
nginx.service: Failed to read
Hi Rashid,
It seems to be a local config issue as hinted in the logs:
Elb 06 12:02:07 rashid-pc nginx[6538]: nginx: [emerg] could not build
server_names_hash, you should increase server_names_hash_bucket_size: 64
Elb 06 12:02:07 rashid-pc nginx[6538]: nginx: configuration file
Thanks Jeremy!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966127
Title:
ubuntu-desktop-minimal pulls gnome-session which is in universe
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/squid/+git/squid/+merge/418482
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967807
Title:
Apparmor doesn't let
Public bug reported:
After installing squid in a Jammy container:
audit: type=1400 audit(1649103012.819:218): apparmor="STATUS"
operation="profile_replace"
label="lxd-squid_//&:lxd-squid_:unconfined"
name="/usr/sbin/squid" pid=1003733 comm="apparmor_parser"
audit: type=1400
@alexmurray, totally random observation that is not related to this bug
but might save you/others some times. The following 4 steps:
# use a LXD VM for testing
lxc launch --vm images:ubuntu/jammy sec-jammy-amd64
# stop the VM and disable UEFI secure boot
lxc stop sec-jammy-amd64
# ensure
When rsyncd cannot find the address it was told to bind to, it exits
with rc=10 and systemd doesn't even attempt a restart.
To make it restart on such condition, the systemd unit should have
`Restart=on-failure` added.
--
You received this bug notification because you are a member of Ubuntu
I tested on a Jammy machine running bind9 1:9.18.1-1ubuntu1 and there,
bind9 won't complain if the IPv6 address it is supposed to listen on is
missing. Bind9 will simply start listening when the IP finally shows up.
This makes it more resilient to IPv6 DAD taking time.
--
You received this bug
Bionic verification was successfully done using the steps outlined in
the bug description. The important parts are captured here:
$ lxc exec lp1959047 -- apt-get install -y lxd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional
** Description changed:
[Impact]
Ubuntu carries a patch on top of systemd [a] to silence
namespace set up failures. This is meant as a workaround
for a bug in the LXD version shipped in Ubuntu 18.04.
Masking namespace set up failures creates a false sense of
security for the
It's been a while that ubuntu-minimal depends on isc-dhcp-client:
$ apt-cache show ubuntu-minimal | grep Depends | grep dhcp
Depends: adduser, apt, apt-utils, console-setup, debconf, debconf-i18n,
e2fsprogs, eject, init, iproute2, iputils-ping, isc-dhcp-client, kbd, kmod,
less, locales,
Public bug reported:
ubuntu-minimal already depends on `init` which depends on `systemd-sysv`
which depends on `systemd` which comes with `systemd-networkd` that has
a DHCP client in it.
Having the isc-dhcp-client package feels redundant.
# Additional information
$ lsb_release -rd
Description:
It turns out the Bionic verification failed because the required changes
went into 5.4.0-106.120~18.04.1 but were dropped from
5.4.0-107.121~18.04.1. Presumably because the later address multiple
CVEs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
5.13.0-38.43 has the fix but 5.13.0-39.44 doesn't, presumably because
-39 includes urgent security fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966499
Title:
Recent 5.13 kernel has broken
Bionic (HWE) verification *failure*:
root@bionic-vm:~# uname -a
Linux bionic-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@bionic-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.4.0-105-generic 5.4.0-105.119~18.04.1
@stgraber, I added the SRU template, let me know if something's off.
Thanks!
** Description changed:
+ [Impact]
+
+ Ubuntu carries a patch on top of systemd [a] to silence
+ namespace set up failures. This is meant as a workaround
+ for a bug in the LXD version shipped in Ubuntu 18.04.
+
+
Thanks @stgraber for providing 3.0.3-0ubuntu1~18.04.2~ppa1 (via
https://launchpad.net/~stgraber/+archive/experimental). This allowed me
to create a Bionic VM in which I created a Jammy container.
The Jammy was then configured to have systemd in debug mode:
root@bionic-vm:~# lxc config set c1
Public bug reported:
ubuntu-desktop-minimal is in main but installing it pulls gnome-session
from universe. Here is how to reproduce it:
1) Create a Jammy VM:
$ lxc launch images:ubuntu/jammy jammy-vm --vm
2) Enter the Jammy VM:
$ lxc shell jammy-vm
3) Install ubuntu-desktop-minimal
** Summary changed:
- Tourchpad not working
+ Touchpad not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966107
Title:
Touchpad not working
To manage notifications about this bug go to:
Hi Nick,
As you mentioned in the issue description, "Unable to fetch DNSKEY set
'.': failure" is not a fatal error as named is still fully functional.
This is because named comes with the current root zone KSK (key id
20326) compiled in. The error is because it tries to refresh it using
RFC5011
This seems to be fixed upstream by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6248c0a22352f09ea041665d3bd3e18f6f872c
which is marked `Cc: stable `.
I'd expect this commit to eventually percolate to Ubuntu kernels, right?
If so, should this bug be kept open until
Impish verification done:
root@impish-vm:~# uname -a
Linux impish-vm 5.13.0-38-generic #43-Ubuntu SMP Fri Mar 18 12:42:26 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@impish-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.13.0-35-generic 5.13.0-35.40 amd64
Focal verification done:
root@focal-vm:~# uname -r
5.4.0-106-generic
root@focal-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.4.0-104-generic 5.4.0-104.118amd64
Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii linux-modules-5.4.0-106-generic
FYI, this problematic behavior is fixed in Jammy/bind9 1:9.18.0-2ubuntu2
where the automatic-interface-scan feature works properly and detects
IPs appearing/disappearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI, I've quoted the "EOF" to avoid the heredocs from turning the "$?"
into "0".
** Description changed:
When a program is running in an overlayfs, /proc/self/maps reports the
wrong path. Notably, it lacks a prefix equal to the mountpoint of the
overlayfs. This only happens on
** Also affects: linux-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- When booting 5.11.0-38-generic, dmesg shows this:
+ When booting 5.13.0-30-generic, dmesg shows:
+
+ ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
+ BUG: kernel NULL
For some reason, strongswan can't find the PSK to use for the connection
as hinted in:
no shared key found for '1.i.p.2'[1.i.p.2] - '2.i.p.7'[2.i.p.7]
no shared key found for 1.i.p.2 - 2.i.p.7
Can you share the strongswan-starter logs? Maybe it will explain what's
wrong with the ipsec.secrets.
That is correct, the installation order needs to be ceph-base first then
ceph-osd.
When Juju puts both a ceph-fs and a ceph-osd unit on the same machine,
it sometimes bring in the ceph-base first causing problems further down
the road.
--
You received this bug notification because you are a
Public bug reported:
Steps to reproduce:
1) Setup and enter a LXD VM
$ lxc launch images:ubuntu/focal foo --vm
$ lxc shell foo
2) Install ceph-base in the VM
# apt-get update -qq
# apt-get --assume-yes --option=Dpkg::Options::=--force-confold install
ceph-base
3) Install ceph-osd
# apt-get
Public bug reported:
When booting 5.11.0-38-generic, dmesg shows this:
ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
thermal thermal_zone3: failed to read out thermal zone (-61)
BUG: kernel NULL pointer dereference, address: 0017
#PF: supervisor read access in kernel
*** This bug is a duplicate of bug 1947601 ***
https://bugs.launchpad.net/bugs/1947601
** This bug has been marked a duplicate of bug 1947601
Cannot start docker container on ubuntu 21.10 server for raspberry pi
--
You received this bug notification because you are a member of Ubuntu
Oops, the above comment might be unrelated, please ignore it as there
seems to be something else going on:
root@sdeziel-lemur:~# zpool status -v
pool: data
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
Another of my FSes has a snapshot affected by this I/O error:
root@sdeziel-lemur:~# zfs --version
zfs-0.8.3-1ubuntu12.13
zfs-kmod-2.0.2-1ubuntu5.1
root@sdeziel-lemur:~# zfs send -vw -I
'data/rootfs-backup'@'syncoid_sdeziel-lemur_2021-10-08:09:17:03'
This worked beautifully, thanks Brian! Here's the verification logs for
bionic and focal:
=> bionic
$ lxc launch images:ubuntu/18.04 ab
$ lxc shell ab
root@ab:~# apt install --no-install-recommends -V -y apache2
...
root@ab:~# systemctl status apache2
● apache2.service - The Apache HTTP Server
It works:
# witness the original bug while running `sudo -i` in another session:
sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam
Sep 28 16:56:52 xeon sudo: pam_unix(sudo:auth): Couldn't open /etc/securetty:
No such file or directory
Sep 28 16:56:53 xeon sudo: pam_unix(sudo:session): session
I finally got around to take another look, sorry for the delay. The
problem is the "noplaintext" in smtpd_sasl_security_options Here's a
small config diff that fixes the problem:
# diff -Naur main.cf.bug main.cf
--- main.cf.bug 2021-09-15 19:14:02.919982259 +
+++ main.cf 2021-09-15
Here too, memtest86+ 5.01 version from Ubuntu would consistently freeze
during test #2 (58% in). If test #2 was skipped, test #3 would trigger a
reboot at some point. Those 2 problems only occurred when more than 4G
was installed in the system.
Switching to the pre-compiled binary from
1 - 100 of 2420 matches
Mail list logo
