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
Nevermind, that turned out to be a red herring, using the latest linux
release candidate along with some bleeding edge versions of packages
solves both the audio and the microphone!
https://github.com/thesofproject/linux/issues/4879
** Bug watch added: github.com/thesofproject/linux/issues #4879
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.
Confirming that with snapd from edge (revision 21508), both the
notifications and apptray denials are resolved for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
I think sof-mtl-rt711-4ch.tplg and sof-mtl-rt711.tplg aren't the same
thing. I'm guessing the former is for devices with four audio channels?
I'm on arch with a sof-mtl-rt711-4ch.tplg and another file beginning
with "sof-mtl-rt711", but no "sof-mtl-rt711.tplg". Renaming either of
them to
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
*** This bug is a security vulnerability ***
Public security bug reported:
Buy Tramadol Online 100mg USA Overnight
➤Order here: https://t.ly/N0hN9
➤Shop Here: https://t.ly/N0hN9
Tramadol 100mg may interact with other medications, including certain
antidepressants, antipsychotics,
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
Public bug reported:
failed during upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4.7
ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257
Uname: Linux 5.4.0-170-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
@Seth I just want to say that I am that person! I signed up specifically
to thank @Chuan and you for getting to the bottom of this. I had the
exact same error and setting `ProtectHome=false` solved the issue, thank
you!
--
You received this bug notification because you are a member of Ubuntu
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
Public bug reported:
when the screen of my laptop goes blank, it will log me out. this
happens when I lock my laptop or put it to sleep. This only happens on
wayland.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Hi there, I appreciate the great work to fix this issue. We have some
AWS Ubuntu instance waiting for this release on Focal to upgrade from
18.04 to 20.04. Do you think there's an expected date that we can get
the new AppArmor from the generic focal pocket instead of Proposed
pocket?
--
You
FWIW I can reproduce this on Ubuntu 18.04, 20.04, and 22.04 and on
multiple architectures (x86_64 and aarch64).
--
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/1739628
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
It is happening to me too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/2018996
Title:
whoopsie uses 100% CPU indefinitely on chrome crash file
Status in whoopsie
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
Public bug reported:
Hello there,
I have Ubuntu 23.04 installed on a Dell XPS 13 9300 with an LG 32" 4K
Ergo Monitor attached as an external display. When I set the "primary
display" at 1080p@60Hz for the LG 32" only with the "secondary display"
of the Dell XPS 13" disabled" and "suspend power"
** Description changed:
The network card inside my laptop will stop detecting connections after a
while whithout having an ethernet cable inserted. in the gnome settings, it
will show that there is no cable conected. The lights on the port on the laptop
won't light up, but those on the port
** Description changed:
- The network card inside my laptop will stop detecting connections after a
while whithout having an ethernet cable inserted. in the gnome settings, it
will show that there is no cable conected. The lights on the port on the laptop
won't light up, but those on the port
Public bug reported:
The network card inside my laptop will stop detecting connections after a while
whithout having an ethernet cable inserted. in the gnome settings, it will show
that there is no cable conected. The lights on the port on the laptop won't
light up, but those on the port of
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
** Description changed:
I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
of the color because it only appears for a short time). I don't get this
problem in fullscreen games running with dxvk and
Public bug reported:
I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
of the color because it only appears for a short time). I don't get this
problem in fullscreen games running with dxvk and the random
It is imperative that we read blog post very carefully. I am already
done it and find that this post is really amazing. https://xtrench-
run.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
The report is now 2 years old, so I'm not sore if anyone will still read
or follow this, but I don't think it's related to policykit, not even
related to simple-scan.
I got the same message recently, and it's probably related to the hpaio
backend of sane (included in hplib).
There's a bugreport
Don't to what? Install unsigned kernel packages? My point is that there
is a regression. linux-image-unsigned-* are longer considered kernel
packages with the new patch.
If linux-image-unsigned-5.4.0-1099-aws and linux-image-
unsigned-5.4.0-1100-aws were the only kernel packages on the system,
There is a regression w.r.t. unsigned kernel packages:
- install linux-image-unsigned-5.4.0-1099-aws, reboot
- install linux-image-unsigned-5.4.0-1100-aws
- mark both as auto
- autoremove will attempt to remove 1100
apt 1.6.14 would keep both.
--
You received this bug notification because you
On an Ubuntu 22.04 (newly updated from 18.04) box I got Firefox and
Chromium browser back to using the good, system SaveAs dialog box
instead of the horrid (((search box focus grabber and almost impossible
to change file name from the default))) dialog box by doing this:
sudo snap install snapd
We are seeing SIGSEGV related to this in Bionic. lp1815101-0006-network-
make-KeepConfiguration-static-drop-DHCP-addr.patch is missing network
checks in link_drop_foreign_config
Would it be possible to incorporate this patch from upstream to prevent
this?
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
@AceLan,
In the comment #32 you were saying: "removed the beta bluez, and install stable
bluez"
It looks like you removed bluez that was from 22/beta track (bluez (22/beta)
5.64-3),
and then installed one from 20/stable track (bluez 5.53-7 334 20/stable).
You wrote that with that revision of
Public bug reported:
After upgrading from Ubuntu 18.04 to Ubuntu 20.04 on my x86_64 desktop
machine, I've noticed a significant regression in the debug experience
with gdb. In particular, function parameters in GDB now seem to reliably
have garbage values on entry to the function until I step
Public bug reported:
when I watch a video in fullscreen, my laptop can draw as many as 25w.
For comparaison, on windows 11, a similar video will take only 8w from
the battery. obviously, the cpu temps and fan speed are much higher on
ubuntu tan on windows. Also, this might be unrelated, but when
@Daniel,
The same Ubuntu Core image works as expected on the Thinkpad E15 and x86 Mac.
Why would the lack of "some extra privileges" impact how it runs on the Dell
system, but not Thinkpad and Mac?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
essage the second monitor became white
again for quite a long time (I did nothing there).
I hope you will be able to fix this bug :)
Best wishes,
Alex,
Prague, Czech Republic, EU
PS: When typing this message I found another bug compared to MS Windows.
When making screenshots (Alt/Shift +
pe you will be able to fix this bug :)
Best wishes,
Alex,
Prague, Czech Republic, EU
PS: When typing this message I found another bug compared to MS Windows.
When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture
even when you actually have the second monitor white all the ti
What fixed it for me was to remove my apt-cacher-ng container + cache,
then re-add it.
This resolved the issue on multiple servers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I can confirm that this is still happening in Kubuntu 18.04. Rudolfs
Caunes's solution actually works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986
Title:
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
I remove the files in `/etc/systemd/system/systemd-
suspend.service.wants` and it works
--
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/1933880
Title:
systemd-logind crash
I manually ran 'do-release-upgrade -d'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1983280
Title:
package libpam-modules 1.3.1-5ubuntu4.3 failed to install/upgrade: new
Public bug reported:
Error upgrading cloud instance from 20.04 to 22.04.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4.3
ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
** 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
Public bug reported:
1)
Description:Ubuntu 20.04.4 LTS
Release:20.04
2)
systemd:
Installed: 245.4-4ubuntu3.15
3) What you expected to happen
Interfaces in the bond keep their real "hardware" mac addresses. bond0 takes
MAC from first interface of the bond when not explicitly set.
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
1 - 100 of 982 matches
Mail list logo
