Thanks for reporting this issue - but it is strange since this update
has been published since 2024-02-27 and this is the first such report of
any issues.
Also given this update has been available for nearly 2 months it is
surprising you are seeing errors from it so much later - I wonder if
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers. Additionally, please only mark a bug as "security" if it
shows
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Given this has been reverted in Debian, it should not be synced into
Ubuntu.
** Changed in: xz-utils (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xz-utils in Ubuntu.
Ok whilst I still can't see the /StatusNotifierItem object listed via
d-feet I can reproduce the denials when launching element-desktop so I
have added some additional changes to the aforementioned PR which
resolve these as well. With all the changes from that PR in place all of
these mentioned
The subsequent error is:
Main script file /usr/lib/x86_64-linux-
gnu/calamares/modules/automirror/main.py for python job automirror
raised an exception.
Is there any way I can debug this further?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Ah although it seems I can reboot the VM at this point and whilst
Calamares appeared to run again again in the rebooted vm if I choose
Install Calamares closes and I see the installed kubuntu environment -
weird
Anyway I think I will be able to use this to debug the original issue
further -
Yes I hit that exact issue in Calamares but after fixing it I then hit
another similar crash in a different script in calamares - will see if I
can reproduce and provide you with details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
So I installed kubuntu-desktop on an up-to-date noble VM and then after
logging into the kubuntu session I was able to reproduce the issue for
Notifications but I couldn't see anything owning the /StatusNotifierItem
dbus path.
For notifications I submitted
Public bug reported:
Latest upstream release
https://gitlab.com/apparmor/apparmor/-/releases/v4.0.0-beta3
Contains only bug fixes since 4.0.0-beta2 which is currently in noble-
proposed thus does not require a FFe.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
> Log: apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/freedesktop/DBus" interface="org.freedesktop.DBus"
member="ListActivatableNames" mask="send" name="org.freedesktop.DBus"
pid=2950 label="snap.element-desktop.element-desktop"
peer_label="unconfined"
This is provided by
Uploaded to noble-proposed yesterday
https://launchpad.net/ubuntu/+source/apparmor/4.0.0~beta2-0ubuntu3
** Changed in: apparmor (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
As per
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/409#note_2298588
this can also be fixed by adding an additional rule to
/etc/fonts/conf.d/70-no-bitmaps.conf of the form:
false
** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/-/issues #409
Both deb8 tests already declares a Depends on python3-distutils - and we
can see that the current test runs all used the 3.11 based
python3-distutils - do we need a no-change-rebuild of python3-stdlib-
extensions so that it builds against python 3.12?
--
You received this bug notification
** Also affects: ufw
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status
Actually I just got it working - no need to send PoC @kerneldude - I
made my own.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/2029464
Title:
A stack overflow in GNU Tar
So I managed to create a tar file with an extended attribute name of
length of ~ 36 bytes long (the largest I can do without exceeding
the existing check on maximum extended header lengths it seems) but this
is not able to trigger the vuln - so if you are able to share your PoC
that would be
@kerneldude - any chance you could share your poc (perhaps email it to
secur...@ubuntu.com rather than post it publicly here)? I have tried
creating one via the following but I hit the CLI args limit before I can
get an xattr key long enough:
touch bar
tar --pax-option SCHILY.xattr.user.$(python3
Excellent - thanks for letting us know. So since a CVE has already been
assigned then we won't assign an additional one. I'll add the details to
our CVE tracker.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
@kerneldude - do you know if MITRE ever assigned a CVE for this?
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I am struggling to see the vulnerability here still - the path used in
this case is /tmp/ubuntu-drivers-common.config.55GJ8b appears to have a
randomly generated suffix and so couldn't have been guessed beforehand
nor preseeded with other contents by a local attacker - so the only way
then that I
Adding a task against libseccomp until we know more about where the bug
lies.
** Also affects: libseccomp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
As discussed with the wider security team, we have decided not to push
ahead with this change for mantic and instead will look to enable it
very early in the 24.04 devel cycle . Marking as invalid and
unsubscribing the release team.
** Changed in: apparmor (Ubuntu)
Status: New => Won't Fix
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member
Public bug reported:
Similar to
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2035315 the
proposed unprivileged user namespace restrictions feature of apparmor in
mantic breaks various third-party applications that use unprivileged
userns for sandboxing themselves.
These include:
-
** Changed in: apparmor (Ubuntu)
Status: Incomplete => 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/2036128
Title:
[FFe] enable unprivileged user namespace
@vorlon - the FFe you approved was to upload a whole new release
apparmor-4.0.0~alpha2 with supporting infrastructure for this feature,
but crucially it did not enable it at that time (as we wanted more time
to add additional profiles for all the packages in the archive so that
when then feature
FYI I redid this change again on top of the fix from
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2036302 and have
uploaded it to the aforementioned PPA (debdiff is almost identical,
except for the different context in debian/changelog)
** Patch added:
As seen in
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2036302 it turns
out the lxc package already shipped a profile in
/etc/apparmor.d/usr.bin.lxc-create - so this profile itself needs to be
updated to add the userns permission and declare the new ABI in lxc in
mantic.
** Also
Uploaded in apparmor 4.0.0~alpha2-0ubuntu4 - currently waiting to build
etc -
https://launchpad.net/ubuntu/mantic/+queue?queue_state=3_text=apparmor
** Changed in: apparmor (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Apologies for this - I am working on an update now to resolve it.
--
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/2036302
Title:
apparmor 4.0.0~alpha2-0ubuntu3 ships same file
@sil2100 - apologies, I think I wasn't clear - for the actual enablement
to take effect, this FFe does require the new kernel - BUT I added some
fallback logic to detect if the kernel doesn't support the required
feature so that the sysctl gets disabled in that case when the apparmor
service is
I have uploaded this new version to
https://launchpad.net/~alexmurray/+archive/ubuntu/lp2036128 and so it
should be built soon (from which the build log will be available).
Please let me know if any other information is required.
--
You received this bug notification because you are a member of
apt log when installing new apparmor packages
** Description changed:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-
restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user
namespace restrictions for Ubuntu 23.10 are to be enabled by default via
a
Proposed changes for FFe to enable the sysctl by default but add
fallback logic to disable it if the system doesn't provide all the
required features.
** Patch added: "apparmor_4.0.0~alpha2-0ubuntu4.debdiff"
Public bug reported:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-
restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user
namespace restrictions for Ubuntu 23.10 are to be enabled by default via
a sysctl.d conf file in apparmor.
In
)
Importance: High
Assignee: Alex Murray (alexmurray)
Status: Confirmed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Statu
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
lt;(aa-features-abi -x)
f17b0a97806d733b5b884d8a1c2fea37 /etc/apparmor.d/abi/4.0
f17b0a97806d733b5b884d8a1c2fea37 /dev/fd/63
** Affects: apparmor (Ubuntu)
Importance: Undecided
Assignee: Alex Murray (alexmurray)
Status: New
** Affects: apparmor (Ubuntu Mantic)
Impo
** Patch added: "bionic debdiff with corrected version number"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+attachment/5682930/+files/apparmor_2.12-4ubuntu5.3.debdiff
** Patch removed: "debdiff for bionic"
It turns out there was already an upload of apparmor 2.12-4ubuntu5.2 to
bionic-proposed that got rejected
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1703821/comments/15),
so this update will instead need to skip this version number and use
2.12-4ubuntu5.3 instead.
--
You received
Importance: Undecided => High
** Changed in: apparmor (Ubuntu Xenial)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu Bionic)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu Xenial)
Status: New =>
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+attachment/5682828/+files/apparmor_2.12-4ubuntu5.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
A possible fix on the snapd side is being prepared in tandem in
https://github.com/snapcore/snapd/pull/12909
--
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/2024637
Title:
** Also affects: snapd (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/2024637
Title:
apparmor.service tries to load
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
As of snapd 2.60, when installed as a snap, snapd includes its own
vendored apparmor_parser and configuration. As such, it generates
profiles using newer apparmor features than the system installed
apparmor may support.
This is seen as a failure to load the apparmor.service
This bug is fixed and the behaviour you are seeing is expected - ie. it
is expected that AppArmor prints a warning about forcing complain mode
for the usr.sbin.sssd profile and that it then also prints a warning
about caching being disabled for that due to it being in force complain
mode. This is
These have now been uploaded to -proposed and are sitting in UNAPPROVED:
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=apparmor
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=apparmor
** Changed in: apparmor (Ubuntu Focal)
Status: Confirmed => In Progress
**
This current bug looks like LP: #1991691
--
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/1992930
Title:
chromium won't launch at menu when installed; lubuntu kinetic
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691
** This bug has been marked a duplicate of bug 1991691
cannot change mount namespace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks I have updated the status of this CVE in the Ubuntu CVE tracker.
** Changed in: tar (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
** Description changed:
- Placeholder for preparation of AppArmor 3.1.1 for kinetic.
+ AppArmor 3.1.1 is the latest upstream version of the apparmor userspace
+ tooling.
+
+ This includes a large number of bug fixes since the 3.0.7 release which
+ is currently in kinetic, as well as various
** Attachment added: "apparmor-3.0.7-to-3.1.1-git-log.log"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git-log.log
** Description changed:
AppArmor 3.1.1 is the latest upstream version of the apparmor userspace
This sounds like a kernel regression.
The commit you link to is for SELinux, which is not enabled by default
in Ubuntu, so I doubt it is that specifically - instead I suspect this
is due to the following commit: https://git.launchpad.net/~ubuntu-
Public bug reported:
Placeholder for preparation of AppArmor 3.1.1 for kinetic.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [FFe] apparmor 3.1.0 upstream release
+ [FFe] apparmor 3.1.1 upstream release
--
You received this bug
> I do not intend to take further action to modify those packages. If it is a
> blocker for Ubuntu
> that they are fixed, then someone from Ubuntu will need to do that work.
Given the relationship between the packages has now changed - ie.
polkitd-pkla is not mutually exclusive from the
** Changed in: gimp (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/283115
Title:
Gimp: toolbox windows can't be minimized
Kinetic)
Importance: High
Status: Confirmed
** Changed in: apparmor (Ubuntu Kinetic)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu Jammy)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Kinetic)
Assignee: (unassigned) => Al
FYI I have sent a MR to the upstream AppArmor project to remove this
dbus deny rule from the exo-open abstraction:
https://gitlab.com/apparmor/apparmor/-/merge_requests/884
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This looks like a duplicate of LP: #1959375
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status
>From what I can see of this postinst this looks to be a bug from adduser
in debian itself - and would appear to come from
https://salsa.debian.org/debian/adduser/-/blob/master/debian/postinst#L33
- ie. if the default value is unchanged then an /etc/adduser.conf.dpkg-
save is always generated when
@mardy I thought we had snapd.apparmor specifically to avoid this
scenario but I can't see that service mentioned at all in systemd-
analyze plot...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
I believe this is caused by debootstrap - it only uses packages from the
release pocket (and this is frozen from the time Ubuntu 20.04 LTS was
originally released). This is a known issue
https://askubuntu.com/questions/744684/latest-security-updates-with-
debootstrap but I am not sure if there is
ges:
- Update autopkgtests to use syscalls from 5.16-rc1
-- Alex Murray Thu, 24 Feb 2022 09:53:35
+1030
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1971288/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
P
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Nice - thanks @sdeziel
--
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/1452115
Title:
Python interpreter binary is not compiled as PIE
Status in Python:
New
Status in
Thanks @doko :)
--
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/1452115
Title:
Python interpreter binary is not compiled as PIE
Status in Python:
New
Status in
I have proposed a fix for this upstream -
https://gitlab.com/apparmor/apparmor/-/merge_requests/861 - once that is
reviewed then we can include the fix in jammy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
For posterity - this is how I did the analysis above:
# download the current python3.9 source package and rebuild it with PIE enabled
apt source python3.9
cd python3.9-3.9.10/
sed -i "/export DEB_BUILD_MAINT_OPTIONS=hardening=-pie/d" debian/rules
dch -i -D jammy "Enable PIE (LP: #1452115)"
I am actively looking at this - FWIW the performance results with PIE
enabled look good - https://paste.ubuntu.com/p/PZjqMFSNSR/ - so I am
discussing internally whether this is something that can still land for
Ubuntu 22.04.
--
You received this bug notification because you are a member of
See this related debian bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1006368
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1962276
Title:
[jammy] Laptop monitor
This appears to be caused (for me at least) by upower 0.99.16-1 - after
upgrading today to 0.99.16-2 things are working again as expected.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #1006368
I hit this too - just reported
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 from
the associated gnome-shell crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
Hmm so had to redo my merge after the 3.0.3-0ubuntu9 upload... see new
bileto ticket/PPA for the current version of it
https://bileto.ubuntu.com/#/ticket/4797
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
FYI I am preparing this in https://bileto.ubuntu.com/#/ticket/4796 - I
have included the original patch from arighi to fix the aa-notify tests
too. Once britney looks happy with this I will upload it to jammy-
proposed.
--
You received this bug notification because you are a member of Ubuntu
FYI I am working on merging apparmor-3.0.4 from debian unstable to jammy
at the moment which should resolve this.
--
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/1961196
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
As reported in https://discourse.ubuntu.com/t/private-home-directories-
for-ubuntu-21-04-onwards/19533/13:
A common situation is to have a central set of users (e.g. in LDAP) and
use pam_mkhomedir.so to create the home directory when the user first
logs in.
These changes do
@leosilva - as you did the original update for exiv2 could you please
sponsor the attached debdiff? Thanks.
** Changed in: exiv2 (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
FWIW I can't reproduce this on a RPi 4 running the aarch64/arm64 Ubuntu
20.04 LTS image:
ubuntu@rpi4:~$ wget https://wrapdb.mesonbuild.com/v2/libuv_1.42.0-1/get_patch
--2021-12-07 05:50:01--
https://wrapdb.mesonbuild.com/v2/libuv_1.42.0-1/get_patch
Resolving wrapdb.mesonbuild.com
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1953301
Title:
Segfault on AArch64 caused by OpenSSL
Public bug reported:
CodecUrl in /etc/PackageKit/Vendor.conf on Impish at least currently
has:
http://shop.canonical.com/index.php?cPath=19=f1e370ea7563ed5e654c10450364ff24
shop.canonical.com does not have a DNS record and has been dead for a
long time so this should be removed.
** Affects:
I think the changelog entry should still list the private home dirs
change for login.defs under Remaining changes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1951161
Public bug reported:
The kmod package ships with a number of files in /etc/modprobe.d which
have non-inclusive names:
$ dpkg -L kmod | grep blacklist
/etc/modprobe.d/blacklist-ath_pci.conf
/etc/modprobe.d/blacklist-firewire.conf
/etc/modprobe.d/blacklist-framebuffer.conf
Is there any option to do this via portals - ie can evince use
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-
org.freedesktop.portal.OpenURI to open the URI? Would then this allow to
avoid going via xdg-open?
--
You received this bug notification because you are a member of
Can you please post a simple reproducer?
--
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/1944436
Title:
Please backport support for "close_range" syscall
Status in
Hmm there is also a crypto abstraction too
https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor.d/abstractions/crypto
- and this is included in the base abstraction so perhaps this *might*
be another candidate..?
--
You received this bug notification because you are a member of
We already have an abstraction (ie a policy fragment) for openssl -
https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor.d/abstractions/openssl
- perhaps a similar one should be created for gnutls and then this can
be #include'd into the profiles for the various applications that
1 - 100 of 340 matches
Mail list logo