** Tags added: sec-6302
--
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/2109707
Title:
apparmor openvpn pritunl problem
Status in apparmor package in Ubuntu:
New
Bug d
The proposed uploaded for Plucky is also available at
https://launchpad.net/~rlee287/+archive/ubuntu/apparmor-
staging/+packages in a PPA.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launch
** Changed in: util-linux (Ubuntu Plucky)
Status: New => Invalid
--
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/2107402
Title:
lsblk on IBM z Systems blocked by ap
Public bug reported:
[ Impact ]
This SRU contains fixes for a number of bugs:
* The unprivileged_userns profile did not have access to the root directory
(https://gitlab.com/apparmor/apparmor/-/issues/505)
* lsblk could not list DASD devices on IBM System Z (LP: #2107402)
* Various commands s
** Tags added: sec-6287
--
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/2107727
Title:
iotop-c: Call of nl_init fails due to insufficient rights
Status in apparmor packag
I was able to reproduce and confirm this bug, which will need fixing in
the apparmor package.
In the meantime, you can add the rule "network netlink raw," to
/etc/apparmor.d/local/iotop-c and reboot, as a workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: iotop-c (Ubuntu)
Status: Confirmed => Invalid
--
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.n
Can you please attach logs with AppArmor denial information as well as
additional information (beyond "not working anymore") that could help us
reproduce the failures locally?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
Public bug reported:
Configuration of an OpenVPN client with a "remote some_hostname.local"
rule on Plucky fails because the OpenVPN profile does not allow access
to /run/avahi-daemon/socket for mDNS lookups.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You r
Upon further investigation, it turns out that the remmina profile is
missing other rules as well and needs to be expanded to handle e.g.
keyed SSH connections. As such, we have decided to pull the remmina
profile from Plucky.
--
You received this bug notification because you are a member of Ubunt
This is a problem with the lsblk profile shipped by AppArmor and not a
problem with the util-linux package. I am not super familiar with IBM z
Systems, but I think the path that would need to be added is
/sys/devices/css0/**. @fheimes could you confirm whether this path
always includes "css0" as op
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
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/2107402
Title:
lsblk blocked by apparmor in 25.04
Status
Updating statuses (again) to reflect that there should no longer be an
active wpa_supplicant profile on Plucky, and to request that people
still running into issues attach the contents of their
/etc/apparmor.d/wpa_supplicant, which should no longer exist.
** Changed in: wpa (Ubuntu)
Status:
** Tags added: sec-6112
--
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/2106311
Title:
File picker does not work in browsers in Ubuntu 25.04 beta for SSSD
users
Status
Can you please share 1) the version of the AppArmor package you now have
installed, 2) the contents of /etc/apparmor.d/remmina, and 3) the
AppArmor denial log from the syslog (which should have something like
"dbus-daemon[3722]: apparmor="DENIED""?
--
You received this bug notification because yo
Also found by LP: #2102680. Fixes are in Plucky but will need to be
backported to Noble and Oracular
--
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/2105840
Title:
apparmo
cided
Assignee: Ryan Lee (rlee287)
Status: New
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
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.
Public bug reported:
The default configuration of aa-notify does not have any filtering on
the notifications that it pops up, resulting in notifications that
suggest adding capabilities to unprivileged_userns, circumventing and
breaking the AppArmor userns restrictions. Since Plucky is very close
** Summary changed:
- not able to deploy Plucky Puffin
+ unable to deploy Plucky Puffin due to AppArmor lsblk denials
--
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/2092232
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
The profile fix will be added as a patch to the version packaged in
Plucky, and should be uploaded into the queue by my EOD tomorrow.
** Tags added: sec-6054
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Both paths involved should be in the latest lsusb profile - can you
double check the AppArmor package version you have installed and also
include the contents of your /etc/apparmor.d/lsusb?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
The corresponding umount rule also needs to be fixed, but otherwise the
diff LGTM
** Tags added: sec-6014
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
--
You received this bug notifi
AIL
==
FAIL: test_sock_dgram (__main__.ApparmorUnixDomainConnect.test_sock_dgram)
Test mediation of file based SOCK_DGRAM connect
--
Traceback (most recent call last):
File "/home/ryan-lee/qrt-test-
Public bug reported:
As reported by https://gitlab.com/apparmor/apparmor/-/issues/302,
execution log ignore and inherit shared the same hotkey (i) in aa-
genprof and aa-logprof, so there is no way to ignore the execution.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: N
Public bug reported:
As reported in https://gitlab.com/apparmor/apparmor/-/issues/493, the
child profile component of a profile name is not handled correctly by
aa-enforce, resulting in it being stripped.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Assignee: Ryan Lee (rlee287
On Fri, Mar 21, 2025 at 10:52:52PM -, Bryce Harrington wrote:
>openldap | 2.6.9+dfsg-2ubuntu1 | plucky
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: sec-5988
--
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/2103524
Title:
lsblk apparmor profile denies block device lookup on Azure
Status in apparmor packa
After a discussion with Alex Murray and John Johansen, we decided on the
following OpenVPN policy adjustments:
- allowing writes to files in the /etc/openvpn, and not just reads
- allowing reads to most of the home directories
- allowing writes to most of the home directories, with an owner restri
*** This bug is a duplicate of bug 2101909 ***
https://bugs.launchpad.net/bugs/2101909
** This bug has been marked a duplicate of bug 2101909
AppArmor OpenVPN profile blocks access to NetworkManager-OpenVPN imported
certs
--
You received this bug notification because you are a member of
Also, I see that you added remmina to LP: #2046844, but the log that you
pasted into the bug report above does not have anything to do with user
namespaces.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
h
Is that the only AppArmor log message being generated, or are there
more?
--
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/2102033
Title:
remmina blocked by apparmor in Plu
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/2101869
Title:
apparmor utils tools cannot parse fusermoun
Public bug reported:
The openvpn profile shipped in the AppArmor package in Plucky
(4.1.0~beta5-0ubuntu6 as of time of writing) does not allow access to
the ~/.cert/nm-openvpn, which is needed to allow OpenVPN to use
certificate files imported by NetworkManager. This was reported by
"@zorn-v" upst
** Changed in: apparmor
Status: New => Fix Released
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: apparmor (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubunt
Does the imfile module still work correctly despite the denial logs, or
is it unable to perform monitoring as expected?
--
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/2101180
We'll be packaging up os-prober profiles in the main AppArmor package so
that they're installed by default and so that we can update them more
easily if necessary.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ub
For the record: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476184
has a rationale for why os-prober introduced mount namespaces in the
first place. If we remove the unsharing of the mount namespace, can we
also make sure that os-prober won't fall over if its unmount calls fail?
** Bug watch
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/2100295
Title:
Apparmor settings for fusermount3 break fla
The broken profile located in /etc/apparmor.d/wpa_supplicant should have
been removed by the upgrade to 4.1.0~beta5-0ubuntu5. Was it still there
on your system after the upgrade?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi Heinrich,
Could you also confirm how you constructed the above AppArmor profile
for wpa_supplicant? Did you create it based on the broken wpa_supplicant
profile shipped in the earlier AppArmor package, or did you create it
some other way?
--
You received this bug notification because you are
Switching this to "Fix Released" now that the 0ubuntu5 release is out
that disables the profile - feel free to switch back if you're still
encountering issues even on that release.
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification bec
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
--
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/2098906
Title:
apparmor breaks sbuild with unsha
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
--
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/2098838
Title:
apparmor appears to deny wpasuppl
This breakage is due to the latest AppArmor packaging enabling a
unshare-userns-restrict profile by default. In most cases, this allows
more usage of unshare than before (while limiting the attack surface
exposed by capabilities in unprivileged user namespaces), but sbuild is
one of the cases where
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Seems like the new wpa_supplicant protocol will need rules allowing read
access to /sys/devices/pci*:*/*:*:*.*/ieee80211/phy*/** and to allow
dgram socket creation, but there may be other accesses we might have
missed that would be needed to unbreak the profile. For now, we'll
proceed by disabling
Public bug reported:
Debian: 2.6.9+dfsg-1
Ubuntu: 2.6.9+dfsg-1~exp2ubuntu1
Please merge openldap from Debian unstable for plucky. These
documentation additions are important for any users whose config (server
or client) might be affected by the switch to OpenSSL:
* d/slapd.preinst: Back up con
As noted in the original Debian bug, this issue is tracked upstream at
https://gitlab.com/apparmor/apparmor/-/issues/447.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #447
https://gitlab.com/apparmor/apparmor/-/issue
Public bug reported:
Sometimes, when booting into a Plucky VM (provisioned via virt-manager),
the login screen flickers constantly, rendering the GUI unusable.
Occasionally, the flickering pauses long enough for me to type in the
first few characters of my password, before the flickering starts ag
ew upstream version, also consider adding an
entry to the Jammy Release Notes:
https://discourse.ubuntu.com/c/release/38
### New Debian Changes ###
openldap (2.5.18+dfsg-3) unstable; urgency=medium
* Fix FTBFS on 32-bit architectures. (ITS#10253) (Closes: #1078822)
-- Ryan Tandy
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
** Also affects: python-defaults (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug n
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2089071
Title:
tarfile.py regression
Hi, there seems to be a regression for the Thinkpad Z13 Gen 2 which uses
the Realtek ALC287 with the CS35L41 speaker amp, and has an existing
quirk to load the CS35L41 side codec. I'm using Alpine, and the
distribution 6.6 LTS kernel works fine, but the -edge kernel (6.11.5
currently) doesn't even
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
After rechecking
https://git.launchpad.net/ubuntu/+source/apparmor/tree/debian/patches/ubuntu
Alex Murray found that this second patch in comment #4 was already
applied in the last upload of the apparmor package, so we don't have to
apply the patch again.
--
You received this bug notification bec
While we're at it, John Johansen also decided to include this patch,
which fixes a critical bug in which the rule priority directives could
destroy permissions for some classes.
** Patch added: "Patch for commit 204c0c5a3a34ac2eb47b863aae20bace48e0ad3c
downloaded from Gitlab"
https://bugs.lau
Gitlab MR has been merged, with commit
c86c87e8868c72e5ab2084b5bf783cd5ca800a9b fixing the ABI break. Patch is
attached.
** Description changed:
Commit 3c825eb001d33bb6f2480c4f78df03aee4c40396 in the Gitlab upstream
adds a field called `execpath` to the `aa_log_record` struct. This field
wa
** Patch added: "Patch of commit c86c87e8868c72e5ab2084b5bf783cd5ca800a9b
downloaded from GitLab"
https://bugs.launchpad.net/apparmor/+bug/2083435/+attachment/5823945/+files/c86c87e8868c72e5ab2084b5bf783cd5ca800a9b.patch
** Description changed:
Commit 3c825eb001d33bb6f2480c4f78df03aee4c403
** Tags added: oracular
--
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/2083435
Title:
AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
Status in AppArmor:
I generated the smaller diff with:
$ diff -u <(awk '{print $6}' lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents )
<(awk '{print $6}' lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents) > file-
list.diff
so one can just see which files were added/removed vs the date/timestamp
change on files that are in both ar
dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output
** Attachment added: "dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814927/+files/lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents
--
You received this bug noti
** Patch added: "Diff of dpkg --contents file column only between 7 and 8"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814925/+files/file-list.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
dpkg --contents on lxc-dev_5.0.3-2ubuntu7_amd64.deb
** Attachment added: "output from dpkg --contents on
lxc-dev_5.0.3-2ubuntu7_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814926/+files/lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents
--
You received this bug
Public bug reported:
1) # lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
2) # apt-cache policy lxc-dev
lxc-dev:
Installed: 1:5.0.3-2ubuntu7
Candidate: 1:5.0.3-2ubuntu7
Version table:
*** 1:5.0.3-2ubuntu7 500
500 http://archive.u
I'm not sure exactly how the liblxc.a static lib was dropped, but the
attached debdiff resolves this by not removing all .a files (an extra
find|rm is around a comment about removing all .la files) and then
adding the file to lxc-dev.install
This produces a lxc-dev deb which includes the static l
** Description changed:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now
Public bug reported:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now it appears to
** Summary changed:
- Wine program crashes with unhandled page fault on startup
+ [regression] Wine program crashes with unhandled page fault on startup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://
Public bug reported:
Today, APT Performed the following update:
Start-Date: 2024-03-02 16:23:10
Commandline: aptdaemon role='role-commit-packages' sender=':1.304'
Upgrade: tcpdump:amd64 (4.99.1-3ubuntu0.1, 4.99.1-3ubuntu0.2),
libglx-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubun
Public bug reported:
As reported in the following question, Ubuntu 22.04 is currently missing the
CMake installation files from tinyxml version 9.0.0.
https://answers.launchpad.net/ubuntu/+source/tinyxml2/+question/708581
These were added in the following source PR as part of the 9.0.0
release:
Can confirm that the workaround worked for me as well. I had a yubikey
on my google account and that was what caused the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.laun
** Attachment added: "ProcCPUinfoFull.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+attachment/5712189/+files/ProcCPUinfoFull.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-o
I am facing this issue on Ubuntu 22.04 LTS as well so I suspect that
this is not related to the operating system per se but more of the
package and how it interacts with google. I have attached my
dependencies as well as my full cpuinfo.
** Attachment added: "Dependencies.txt"
https://bugs.lau
Public bug reported:
I am attempting to install Zoom onto my laptop. Any assistance would be
greatly appreciated. Thank you!
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-bsd 2.3.1-9ubuntu1.5
ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-8
I also have this bug on Ubuntu 22.04 following this guide, aside from setting
it to my user.
https://code.luasoftware.com/tutorials/linux/ubuntu-prompt-system-policy-prevents-modification-of-network-settings-for-all-users
[Let all users modify system settings for network]
Identity=unix-user:ryan
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2000170
Title:
bond interface down: devi
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2000325
Title:
ipv6 duplicate address pr
root@ubuntu:/home/ubuntu# networkctl status eth2-2 --no-pager
● 2: eth2-2
Link File: /run/systemd/network/10-netplan-eth2-2.link
Network File: /run/systemd/network/10-netplan-eth2-2.network
Type:
There are two scenarios: Applying to VM the first time, on subsequent
boots.
On first boot without the updated netplan config, when you first add it
root@ubuntu:/home/ubuntu# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:
** Attachment added: "netplan config for vm2"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637221/+files/50-v4-v6-fail-vm2.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
** Attachment added: "netplan config for vm1"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637220/+files/50-v4-v6-fail-vm1.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
# Create a bridge and add two ports
$ sudo ip link add name atx-fabric0 type bridge
$ sudo ip link set up dev atx-fabric0
$ sudo ip tuntap add atx-fabric0i1p1 user $USER group $USER
$ sudo ip tuntap add atx-fabric0i2p1 user $USER group $USER
# create two focal VM images from focal daily server
$
To reproduce what happens on physical systems I create two VMs with nics
in the same bridge on the host. Booting the first VM up and allowing
the network config to apply, and then when booting the second VM up
layer, as it applies the IPv6 address to the interface in the bridge,
the kernel detects
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://archive.ubuntu.com/ubuntu focal-
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://azure.archive.ubuntu.com/ubuntu
Public bug reported:
possibly relating to locked boot disk.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
NonfreeKernelModules: nv
Simply stating that you no longer protect the last installed kernel and
providing a link to the details is preferred over making one feel
inadequate for reporting a perceived issue.
"apt-auto-removal" is not specifically mentioned in the changelog since
v0.9.12, and apt-file continues to indicate
Public bug reported:
#> lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
#> apt-cache policy apt
apt:
Installed: 2.0.9
Candidate: 2.0.9
Version table:
*** 2.0.9 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/l
client/server upon Jammy upgrade
Status in openssh package in Ubuntu:
New
Bug description:
This s390x VM has been upgraded to Jammy, including the host (qemu-
system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any
incoming sshd attempt immediately results in e.g.:
to use ssh, or any
incoming sshd attempt immediately results in e.g.:
ryan@s390x-dev:~$ ssh g...@github.com
[ 433.672800] User process fault: interruption code 0011 ilc:3 in
libc.so.6[3ffa6c0+1ca000]
[ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
[ 433.672
Public bug reported:
This s390x VM has been upgraded to Jammy, including the host (qemu-
system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any
incoming sshd attempt immediately results in e.g.:
ryan@s390x-dev:~$ ssh g...@github.com
[ 433.672800] User process fault: interruption
This is still broken on impish when running i3 under X11.
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]:
/etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not
found
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]:
/etc/X11/Xsession.d/75dbus_dbus
t for smbk5pwd.
* Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug
(#866122) is fixed in all relevant suites by now.
-- Ryan Tandy Fri, 27 Aug 2021 09:42:31 -0700
openldap (2.4.57+dfsg-3) unstable; urgency=medium
* Link smbk5pwd with -lkrb5. (Closes: #9
It also looks like, farther down, systemctl_redirect() leaks $service.
Not sure if it's intentional or not, given that it works to protect its
other variables, so maybe it could use some attention too.
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L70
--
You rec
I'm not a bash script architect, but I bodged together this workaround
and the ipmiutil_wdt service starts correctly with it applied to my
system:
https://gist.github.com/TheWug/1a7f509e040f10c05039acc06fe29d9e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
I am using systemd version 248.3-1ubuntu3 from the impish repository.
It was compiled and built in the following manner:
# add impish deb-src repository to apt sources
apt build-dep systemd/impish
apt source -b systemd/impish
Once built, it was installed over the top of syst
1 - 100 of 788 matches
Mail list logo
