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
*** 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
Touch seeded packages, which is
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
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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2060965
Title:
liblxc is missing in
@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
FYI, snapd is a "base-less" snap:
$ lxc launch ubuntu-minimal-daily:22.04 c1
$ lxc shell c1
root@c1:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
root@c1:~# snap install snapd
2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart...
snapd 2.61.1 from Canonical✓
This was verified on Mantic with -proposed (1:5.0.1-0ubuntu8~23.10.1).
Here's how:
$ lxc launch ubuntu-daily:23.10 c2
Creating c2
Starting c2
$ lxc shell c2
root@c2:~# apt-get update
...
root@c2:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
This was verified on Jammy with -proposed
(1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1). Here's how:
$ lxc launch ubuntu-daily:22.04 c1
Creating c1
Starting c1
root@c1:~# apt-get update
...
root@c1:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
Reading
** Description changed:
In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
core22 snap.
This means that are subsequent snap
@bdrung, I just noticed this package is now in universe in Noble. Is the
demotion related to this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2047939
Title:
Let
Using a fast HTTPS server (same LAN as client), the `main.py` tests goes
from ~8s to ~2.5s:
# time python3 /tmp/main.py
Distro: Ubuntu 22.04.3 LTS
Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022
0 1 2 3 ... 99
real0m8.163s
user
In fact, the same but updated note was already on
https://documentation.ubuntu.com/lxd/en/latest/installing/#install-lxd-
from-source where it mentions that it affects 22.04 onward while the one
you dug up says 23.04/23.10 are not affected ;)
--
You received this bug notification because you are
** Summary changed:
- liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
+ liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/patches/0003-meson-
Set-DEVEL-flag-post-release.patch is the patch that should be dropped by
the SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Public bug reported:
My home network comprises many VLANs managed by `systemd-
networkd`/`netplan`. Those VLANs are then used as parent interfaces for
LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
update), my whole network breaks because all the unmanaged bridges lose
their
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
@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.
That same
Did I mentioned it was not convenient? :P
$ d="$(mktemp -d)"
$ lxc manpage "$d"
$ ls -1 "$d"
lxc.1
lxc.alias.1
lxc.alias.add.1
lxc.alias.list.1
lxc.alias.remove.1
lxc.alias.rename.1
lxc.cluster.1
lxc.cluster.add.1
...
$ ls -1 "$d" | wc -l
293
--
You received this bug notification because you
I've been told that snaps can't ship man pages unfortunately:
https://forum.snapcraft.io/t/support-for-man-pages/2299/24
https://bugs.launchpad.net/snapd/+bug/1575593
You can get something with `lxc manpage` which is basically the builtin
--help formatted for man. However, that's not
Interesting! If your recollection is accurate then I unfortunately don't
see how rsync could workaround that FAT32 limitation :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Jammy's rsync (3.2.7) has --trust-sender that's described as: "trust the remote
sender's file list"
However that won't be of much help as that's not available in older releases :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The rsync versions mentioned in the bug are very old and the distro
version they came with, long out of support. As such, I'll mark the
issue as incomplete until this can be reproduced/confirmed with a
recent/supported version. Thanks!
** Changed in: rsync (Ubuntu)
Status: Confirmed =>
I'll mark this old bug as fix released because I can't reproduce it on
20.04 (3.1.3) nor 22.04 (rsync 3.2.7). Here's how I tested it on 20.04:
# rsync --version
rsync version 3.1.3 protocol version 31
...
# mkdir -p "src/a " dst
# rsync -aiv src/ dst/
sending incremental file list
.d..t..
I /think/ there is work being done by security to land a MRE for rsync,
you might want to sync with @mdeslaur.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2007837
Title:
@georgiag, the behaviour changes when you tell tcpdump to do line
buffering (`-l`).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1641236
Title:
Confined processes
Yeah, I figured it was likely the outcome when I replied to a bug that
was last touched 10 years ago ;) The bug will close itself in ~60 days
if nothing happen so I think that's OK. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I tested a rsyslog client talking to a rsyslog server both using
`rsyslog-gnutls 8.2112.0-2ubuntu2.2` on Ubuntu 22.04 and it worked fine.
There, there is no error loading "/usr/lib/x86_64-linux-
gnu/rsyslog/lmnsd_gtls.so" as long as the `-gnutls` package is
installed. I used only a cert (from
@paride, I know it's a low priority item but I was wondering what's next
to do for the SRU? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1965076
Title:
rsync
Thanks Paride for the feedback, here's a refreshed debdiff!
** Patch removed: "rsync_3.2.3-8ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff
** Patch added: "rsync_3.2.3-8ubuntu3.1.debdiff"
I packaged the upstream fix (minus the changes to NEWS.md) and created
the debdiff attached.
** Description changed:
+ [Impact]
+
+ This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime
as being "newer"
+ implying they would need to be transfered/sync'ed where in fact
** Also affects: rsync via
https://github.com/WayneD/rsync/issues/98
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1965076
If you can fill out the SRU template, that'd be great! I see that you
worked with upstream to ID which commit corrected the problem, that will
be useful to whoever creates a debdiff! If you need a hand with the
debdiff, please let me know and I'll set some time aside. Thanks!
--
You received
@Ian, the back and forth on status was apparently due to a simple
mistake on which distro version was affected. The good news is that
thanks to comment #7, we now know that Kinetic is fixed which is one of
the required step to do a SRU
(https://wiki.ubuntu.com/StableReleaseUpdates) to have the fix
I can confirm the problem affects rsync 3.2.3-8ubuntu3 as shipped in
22.04.
** Changed in: rsync (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
I can confirm the issue on an *old* GCP instance:
$ mount | grep devtmp
devtmpfs on /dev type devtmpfs
(rw,relatime,size=490260k,nr_inodes=122565,mode=755,inode64)
$ cat /etc/cloud/build.info
build_name: server
serial: 20200902
$ uname -a
Linux mx1 5.15.0-1018-gcp #24~20.04.1-Ubuntu SMP Mon
I'll mark the bug as fix released as I think Ubuntu releases no longer
suffer from this problem. Also, all Ubuntu releases still receiving
normal support have moved away from upstart.
** Changed in: upstart (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
** Summary changed:
- dnsmasq often using 100% of CPU
+ dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Public bug reported:
If an update for a package is available but not installed, simulating a
purge shows the wrong version.
On that 20.04 system, an update to libxml2 2.9.10+dfsg-5ubuntu0.20.04.4
was available but only the ".3" one was installed. Simulating a purge
gives this bogus output (with
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
The affected Ubuntu release is no longer supported so closing the bug.
The problem seemed like a mirror or an apt issue more than a rsyslog one
anyway.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Ubuntu 22.04 with rsyslog 8.2112.0 doesn't have this problem so marking
as fixed, thanks!
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Ubuntu 18.04 with rsyslog 8.32.0 is not affected by that problem anymore
so marking as such. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Marking as fix released based on versions reported in comment # 10.
Ubuntu Trusty ships 7.4.4 so it has the patch.
** Changed in: rsyslog (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/583936
Title:
package rsyslog-mysql 4.2.0-2ubuntu8
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release. Marked as incomplete
until then. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
I've proposed the change to Debian: https://salsa.debian.org/sdeziel-
guest/quassel/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1814302
Title:
Thanks for the explanation and pointer to the ML thread, makes sense to
me now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1966562
Title:
ubuntu-minimal should
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
Touch seeded packages, which is
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
Thanks Jeremy!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1966127
Title:
ubuntu-desktop-minimal pulls gnome-session which is in universe
Status in gdm3 package
@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
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:
@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
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
> these can be added fairly soon.
> https://gitlab.com/apparmor/apparmor/-/merge_requests/684
>
> though that is just landing it upstream and I am not sure when the
> next ubuntu upload will be
At least on 20.04, the profile comes from the firefox package, not the
apparmor one:
$ dpkg -S
Verification for Groovy (246.6-1ubuntu1.5)
# Initial repro on groovy:
root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf
/etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823
1625844823 0 4096
root@groovy:~#
Verification for Focal (245.4-4ubuntu3.8)
# Initial repro on focal:
root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf
/etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273
1625844273 0 4096
root@focal:~# ip
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You
1 - 100 of 339 matches
Mail list logo
