Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
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/2037667
Title:
Regression on Jammy's kernel 5.1
This was the upgrade in question.
Aptitude 0.8.12: log report
Tue, Apr 13 2021 10:34:25 -0300
IMPORTANT: this log only lists intended actions; actions which fail
due to dpkg problems may not be completed.
Will install 16 packages, and remove 0 packages.
7168 B of disk space will be used
Hey, Dan.
Thanks for looking into this. I am attaching a journal log from the time
I got the failure.
Cascardo.
** Attachment added: "journalctl output"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+attachment/5490397/+files/systemd_upgrade.log
--
You received this bug
Public bug reported:
Whenever I upgrade systemd on my groovy system, my gnome session is
terminated.
This is very annoying, as everything that was running on that session is
terminated.
NetworkManager also stops running.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status:
Now building on ppa:cascardo/ppa.
** Patch added: "Fix for groovy"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+attachment/5401581/+files/oss4_4.2-build2010-5ubuntu7.debdiff
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug
So, dot-symbols on powerpc are not a thing on userspace since a while
(from gcc 3.4 times). And, then, I realized this header comes directly
from alsa, and for a different reason, this same section has already
been dropped there. So applying the same changes makes sense here.
--
You received
** Also affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1891565
Title:
oss4 does not build on
So after some investigation on systemd failures on ppc64el triggered by
the kernel on eoan, I noticed some coredumps on processes when running
under qemu inside the ADT environment.
As one of these processes is sleep, I am pretty confident this is caused
by the lack of emulation or rather the
https://lore.kernel.org/lkml/20200311170120.12641-1-j...@kernel.org/T/#u
This patch just caught my attention. I didn't do any investigation, but
as I recall seeing something about namespaces, maybe this is related.
Cascardo.
--
You received this bug notification because you are a member of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948350#20
In particular, this seems to come to a Debian specific patch on kmod
that turns that message from a DEBUG message to an ERROR message.
As there has been no responses from the patch's author, we could do a
quick diligence investigation
Exactly my point about consistency. They should either return EIO in
both cases or succeed in both cases. Which behavior will depend on: 1)
which is the easier solution; 2) what upstream thinks is okay.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
so the problem is inside the block layer ?
More likely the loop driver not undoing something it does when a file is
attached to it. But could as well be something related to the multiqueue
support, so could still be something in the block layer. Still needs
investigation.
Anyway, as this is not
I did some quick testing and it seems this happens on whatever loop
device that had a file attached and then detached. No matter if it's the
next available or not. So, if you create a new loop device without ever
attaching a file to it, it seems the block layer is not setup
sufficiently so any
route2 to 5.2 fixes this.
** Changed in: linux-hwe-edge (Ubuntu)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux-hwe-edge (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification
The log only shows the SKIPs. I managed to reproduce one FAIL that I
have seen as well:
TEST: ipv6: list and flush cached exceptions[FAIL]
can't list cached exceptions
This one ended up being caused by the script itself and a difference in
behavior between different
Public bug reported:
11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh
11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
11:52:44 DEBUG|
The autopkgtest regression was caused by a network timeout. A retry was
done and was successful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1844524
Title:
text
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1844524
Title:
text relocation of grep prevents its use under udevd
Status in grep package in Ubuntu:
Invalid
root@lewis:~# dpkg -s grep | grep Version
Version: 3.1-2build1
root@lewis:~# systemd-run -t --property MemoryDenyWriteExecute=yes grep -i
crashkernel= /proc/cmdline
Running as unit: run-u73.service
Press ^] three times within 1s to disconnect TTY.
root=UUID=b995e70a-9241-4f98-b451-b3ecc7fa990c ro
** Changed in: grep (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1844524
Title:
text relocation of grep prevents its use under udevd
Public bug reported:
[Impact]
grep can't be used under udev, preventing kdump-tools to be used after a memory
hotplug.
[Test case]
Run grep with systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep
crashkernel /proc/cmdline
[Regression potential]
The fix is a simple rebuild, so
Hi, Manoj.
There is nothing wrong in what you are doing here. This seems to be an
unrelated bug. I am looking at any known problems on cpuidle for power9.
Can you, please, open a different bug report, and try a different system
for regression testing? From the log message, it doesn't seem there
https://lists.freedesktop.org/archives/systemd-
devel/2019-May/042570.html
--
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/1814373
Title:
storage / luks / dmsetup
After applying the two fixes, I managed to get the test running on a
loop for more than 24 hours on disco. Will review the case with someone
on the team before attaching the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
It goes back to xenial. I think I found the cause on systemd, will test
a fix and report back soon.
--
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/1814373
Title:
storage
So, I tested with a 4.18 kernel and I could still reproduce the issue on
eoan. Then, I tested on a bionic system, 4.15 kernel, systemd 237, glibc
2.27, and I see a failure on malloc, also memory corruption.
This appears on the backtrace.
3738malloc_printerr ("malloc(): memory
Still need to fix it so it will exit when unit is failed, and maybe
after some timeout.
---
debian/tests/storage | 2 ++
1 file changed, 2 insertions(+)
diff --git a/debian/tests/storage b/debian/tests/storage
index 04d11c8..47fbe81 100755
--- a/debian/tests/storage
+++ b/debian/tests/storage
With systemd storage test, I got two different situations:
Also on amd64, the test is still flaky, it needs to wait for the unit to
be active before stopping it, otherwise it's canceled. I will send a
comment with a preview of a fix.
On ppc64el, however, even after that fix, the patch will fail
Upgrading a cloud image, I couldn't reproduce it. I also tried
installing mate-desktop-environment-core + mate-dock-applet (because it
depends on bamfdaemon) before upgrading, and still couldn't reproduce. I
will install a cosmic mate desktop and see if I can reproduce this
problem when upgrading.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification be
@vorlon, test case updated.
Thanks.
Cascardo.
** Description changed:
[Impact]
initramfs created with MODULES=dep or kdump initrd won't boot a system with
root filesystem on a multipath nvme.
[Test case]
Systems with nvme multipath were able to boot with the created initramfs.
Also
; Thadeu Lima de
Souza Cascardo (cascardo)
** Changed in: initramfs-tools (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs
** Patch added: "fix for bionic"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1778844/+attachment/5256424/+files/initramfs-tools_0.130ubuntu3.8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi, Andrew, with the debdiff attached and ubuntu sponsors team
subscribed, now we should wait for someone on that team to sponsor that
update. With the SRU template attached, the only thing blocking that
sponsorship now is that disco is now on freeze, so the sponsor is the
one who would decide
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Incomplete
** Also affects: kmod (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod
** Also affects: mesa (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: libdrm (Ubuntu Disco)
Importance: Undecided
Status: Fix Released
** Also affects: xorg-server (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu
I have tested that the module loads and works fine on POWER, on a KVM
guest on top of a Power8 system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1795857
Title:
enable
** Patch added: "initramfs-tools_0.131ubuntu19.debdiff"
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1778844/+attachment/5249521/+files/initramfs-tools_0.131ubuntu19.debdiff
** Description changed:
+ [Impact]
+ initramfs created with MODULES=dep or kdump initrd won't boot a system
Public bug reported:
After isc-dhcp update from 4.3.5 to 4.4.1, dhclient-script uses
valid_lft option when adding an IPv4 address.
When used on the initrd generated by initramfs-tools, this will fail
because busybox ip does not support this option.
This affects the use of
That's an OOM problem. Just increase the reserved crashkernel memory
size and test again, please.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
Public bug reported:
During reboot:
Mar 01 14:15:52 P8lpar5 systemd[1]: Stopping Login Service...
[...]
Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Failed to abandon session scope,
ignoring: Connection timed out
Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Session 5 logged out. Waiting for
Tested on a chroot that the resulting initramfs is smaller and doesn't
contain the framebuffer drivers. After installing some cryptsetup
packages, those same drivers were included again after regenerating
initrd images.
Cascardo.
** Tags removed: verification-needed verification-needed-bionic
**
Hi, Andrew and Hari.
The original issue is only resolved by using an initramfs-tools from my
ppa. We still need to get this fix included in our releases. I will
start working to get this in disco.
Cascardo.
** Changed in: initramfs-tools (Ubuntu)
Status: Invalid => In Progress
** Also
The system has too many devices, so too many drivers are using too much
memory. So, the system goes out-of-memory before makedumpfile is
complete. Please, reserve more memory on crashkernel, reboot the system
and repeat the crash test.
To reserve more memory on crashkernel, edit file
** Description changed:
+ [Impact]
+ initramfs-tools would always include all "framebuffer" drivers/firmware
inside initramfs, which was making it ever more huge. In some systems with low
memory, that would even prevent systems to boot. kdump, for example, had an
impact.
+
+ [Test case]
+
I have pushed a version of initramfs-tools to my ppa that seems to fix
the problem. Can IBM test it?
add-apt-repository ppa:cascardo/kdump2
It's a version for bionic. Only initramfs-tools should come from this
source. kdump-tools and makedumpfile should be from bionic-updates or
bionic.
After
Upstream is a little reluctant to accept my changes, and seems to
suggest that we find out the layout of the paths some other way (which
is possible, but would be such a special case on initramfs-tools, only
for nvme).
Cascardo.
--
You received this bug notification because you are a member of
https://lore.kernel.org/linux-block/20181213113549.GA7543@calabresa/T/#t
Upstream discussion in progress.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Upstream discussion is progressing. I have tested some patches from hch,
will send him some feedback later today and post the links here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
I have been working upstream to get this fixed on the nvme driver, but
it might still take some time, I already have done a back and forth with
hch. Will send a v3 later this month.
Meanwhile, there are multiple workarounds we documented so far in the
bug, namely:
1) Disable nvme multipath,
First piece of the puzzle submitted:
http://lists.infradead.org/pipermail/linux-nvme/2018-September/020174.html
Tested with a small change on initramfs-tools, though I will wait for
comments on the first one before submitting that to initramfs-tools
upstream.
--
You received this bug
Just create a /etc/modprobe.d/nvme.conf file with the following
contents, recreate initrd, remove kdump initrds so they are recreated in
the next boot, then reboot.
# cat /etc/modprobe.d/nvme.conf
options nvme-core multipath=0
# update-initramfs -u
# rm /var/lib/kdump/initrd.img*
# reboot
--
As a workaround, I suggest setting nvme-core.ko multipath=0 parameter.
Can you try that, rebooting, recreating the kdump-tools initrd, then
crashing?
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools
So, the hidden disk was introduced by hch as commit
8ddcd653257c18a669fcb75ee42c37054908e0d6 just to support nvme multipath.
This thing prevented lsblk from working when there were slaves under the
multipath nvme, as lsblk would postpone processing those, and lsblk
could not process the paths
** Summary changed:
- ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is
not working and system enters into initramfs state
+ nvme multipath does not report path relationships
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
So, this is a multipath disk, whose parent is the nvme-subsys0 device,
not nvme0 device. The latter is a PCI device, but the former is a
virtual one. Some code to add slaves/holders relationships was added,
but reverted. I will investigate any further discussion about this
upstream, or look into
I managed to download the lp1778844_sys.tar.gz from FTP in time. It has
some huge resource files, so I have to play a little with the tarball.
It looks like some symlinks were tarred as empty files, so maybe I'll
miss something, but I am investigating right now. I'll let you know if I
need any
The sysrq mechanism allows someone with physical access to the system to
easily cause it to boot by just pressing some keys. That's why the sysrq
default allows only very few commands to be issued. kdump is for real
crashes. kdump testing may require using the sysrq-trigger mechanism,
but that
** Patch added: "fix for cosmic"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+attachment/5188455/+files/initramfs-tools_0.131ubuntu11.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The number of processes (in systemd, tasks).
The command below works for me.
Now, should we change the default on our test systems? Running under
systemd-run does not look like a good option.
# systemd-run -p TasksMax=100 ./testcases/bin/msgstress03
--
You received this bug notification
Adding initramfs-tools and nominating for bionic.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Ah, I see what you meant about the PHB. The two new attached logs are
not at all similar to the original ones, maybe pointing to an unrelated
problem.
As for the sosreport, the /sys/ directory is missing almost everything
that I would need to debug this. So, I need any other form of collecting
Hi, Hari.
The sosreport should be enough. I sent that message without an updated
view of the bug, so did not notice the attachments. They came on the
same day I asked. Just realized now that they are present. Let me look
at them.
Now, if kdump works with MODULES=most, then the PHB initialization
Public bug reported:
As systemd limits the number of processes, this test will fail because
it can't fork enough processes. That is limited to when the test is run
after logging as user 1000, then running sudo. I guess that logging as
root may not cause this to happen.
#
Can you run apport-collect -p linux 1778844 ?
Thank you.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
I have managed to test kdump and initramfs with MODULES=dep on an
emulated nvme, using qemu. Both worked just fine. The sysfs tree seems
reasonable too, in respect to how initramfs finds the necessary modules.
So, I would really need the specific details on that failure case, that
is, the sysfs
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic-canonical-kernel-team-
bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz
== TEST-21-SYSUSERS ==
make: Entering directory
** Description changed:
+ [Impact]
+ Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because
the post-update script for zipl will fail.
+
+ [Test Case]
+ Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on
s390x.
+
+ [Regression]
+ zipl update on
** Also affects: s390-tools (Ubuntu Bionic)
Importance: Undecided
Status: Fix Released
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also
This will likely break with linux-hwe-edge on xenial as well. Hence,
requesting SRU for xenial with the attached debdiff.
** Also affects: s390-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
** Patch added: "for bionic"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+attachment/5126843/+files/initramfs-tools_0.130ubuntu3.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
*** This bug is a duplicate of bug 1561643 ***
https://bugs.launchpad.net/bugs/1561643
** This bug has been marked a duplicate of bug 1561643
initramfs-tools ignores the FRAMEBUFFER option
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: laptop-mode-tools (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu
The systemd update fixes the problem for me on artful.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Once in a while I get:
[ TIME ] Timed out waiting for device dev-hvc0.device.
[DEPEND] Dependency failed for Serial Getty on hvc0.
That means I cannot login to the system using the console, and sometimes
it's the only method available. Console is on hvc0 itself.
Happens on
It seems this has been reverted on systemd 235. However, as this might
come to bite us back again in the future (it was mentioned that
dependencies should not be added to aliases), and as Steve has pointed
out, it makes more sense to use multi-user.target, I am going to fix it
in a future release
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/696435
Title:
wait-for-root fails to
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1567597
Title:
implement 'complain mode'
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1567597
Title:
implement 'complain
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => 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/1660832
Title:
unix domain socket cross
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => 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/1661030
Title:
regession tests failing after
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => 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/1648143
Title:
tor in lxd: apparmor="DENIED"
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1673350
Title:
dm-queue-length module is
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1673350
Title:
dm-queue-length
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Xenial)
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 Ubuntu.
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Xenial)
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 Ubuntu.
** No longer affects: tor (Ubuntu)
** Also affects: tor (Ubuntu)
Importance: Undecided
Status: New
--
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/1648143
Title:
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1660832
Title:
unix domain socket cross
90 matches
Mail list logo
