@smoelius:
If you are interested in learning more of the processes, you can read
about it at https://wiki.ubuntu.com/StableReleaseUpdates
To summarize the upload is at step 4 of the procedures. It has been
uploaded but has not been promoted to the -proposed pocket. Once it has
been accepted it
Attempting a forced install of python3-software-properties=0.96.20,
software-properties-common=0.96.20 also removes critical (necessary?)
files: software-properties-gtk and ubuntu-desktop. It also suggests
autoremoving multiple other critical apps and support files.
Since this update is not ESM
An explanation would be helpful in order to understand, for future
reference, why software updates are issued for a release, Ubuntu 16.04
(xenial) ESM, that is no longer supported.
The Maintainer of this upgrade package is a subscriber to this bug
report.
--
You received this bug notification
Public bug reported:
I can't update python3-ubuntutools because it says it needs
python3-launchpadlib-desktop. I think it depends on
python3-launchpadlib, not python3-launchpadlib-desktop.
** Affects: ubuntu-dev-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received
Just checking a theory - does installing libnvidia-egl-wayland1 help
with being able to open the Settings app, at least?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065791
Title:
incorrect
I experienced this on my desktop with Nvidia-only graphics - the "egl"
message in the terminal was the tip-off that installing libnvidia-egl-
wayland1, which had worked for me previously to solve some odd Wayland
issues, might help here, and it did in fact help in 24.04 as well.
From my "I know
Uhmmm sorry Oracular not Oneiric, seems I am a full 13 years out of sync
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065708
Title:
Add Picture button in Background does not allow you to select
I can report the bwrap-userns-restrict profile in Oneric makes this work
for me. This fix migrated out of proposed this week, so it has only been
available for a few days.
We will work on getting it SRUed to noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@samlan00:
you should be able to revert your fix on Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065708
Title:
Add Picture button in Background does not allow you to select
wallpaper
Agreed that, we don't want to remove sandboxing on the thumbnailer. We
are looking at what we can do for a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065708
Title:
Add Picture button in
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu
** Changed in: linux-azure (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: Fix
** Changed in: linux-azure (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Noble)
Status: New => In
** Description changed:
SRU Justification
[Impact]
- * Request to enable MANA driver on arm64 arch using 4k page size
+ * Request to remove multiple of 64 alignment on mana Rx DMA datasize
[Fix]
- * Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
- net: mana:
** Description changed:
SRU Justification
[Impact]
* Request to enable MANA driver on arm64 arch using 4k page size
[Fix]
* Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
net: mana: Enable MANA driver on ARM64 with 4K page size
[Test Plan]
*
Public bug reported:
SRU Justification
[Impact]
* Request to enable MANA driver on arm64 arch using 4k page size
[Fix]
* Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
net: mana: Enable MANA driver on ARM64 with 4K page size
[Test Plan]
* Compile tested
* Boot tested
*
** Description changed:
SRU Justification
[Impact]
* Request to enable MANA driver on arm64 arch using 4k page size
[Fix]
* Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
net: mana: Enable MANA driver on ARM64 with 4K page size
[Test Plan]
*
** Description changed:
SRU Justification
[Impact]
* Request to enable MANA driver on arm64 arch using 4k page size
[Fix]
* Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
net: mana: Enable MANA driver on ARM64 with 4K page size
[Test Plan]
*
* Microsoft to test
[Regression potential]
* Limited to configuration options, no regression potential
[Other Info]
* SF: #003859
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Assignee: John Cabaj (john-cabaj)
Status: New
** Affects: linux-azure (Ubuntu Focal
@mhalano:
can you check your logs for apparmor denial messages?
sudo dmesg | grep DENIED
or
journalctl -g apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user
I opened a Ubuntu Noble specific task. We can close it after verifying
the current apparmor in noble fixes the issue.
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Noble)
Importance: Undecided
Status: New
--
You
policy<{'arm64': 'y'}>
CONFIG_ARCH_R9A08G045 enabling RZ/G3S. This is supported from Linux kernel v6.7
onwards
CONFIG_ARCH_R9A09G057 enabling RZ/V2H. This is supported from Linux kernel
v6.10 onwards
Best Regards
John
** Affects: linux (Ubuntu)
Importance: Undecided
Status:
It seems like you've encountered a technical issue with aptd crashing
due to a UnicodeDecodeError. Technical glitches like these can be
frustrating, but it's great that you're reaching out for assistance.
As for your Ubuntu version and package details, it's always helpful to
provide such
Yes for the appimages that are affected they should be reported
upstream. There are some things that upstream can do to make appimages
work under the restriction, ideally they would do it dynamically based
on whether the user namespace is available than just based on distro
which is the quick fix
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Maxime Bélair (mbelair)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685
Title:
aa-logprof fails with 'runbindable' error
To
The AppArmor profile covers the packaged version and the standard
privileged install location. You are correct that it does not cover
running firefox from an unprivileged user writable location like $HOME.
For unprivileged user writable locations like $HOME/bin/ the user has to
deliberately make
Public bug reported:
The sound fades off after initially playing for about 2s. In Firefox, sometimes
if I pause a Youtube video, switch between applications, and then return to
Firefox, the same things repeats. The sound plays for 2s and then stops. In
Rhythmbox, after it stops, the sound
APNG is already supported in all major browsers (except for Edge/IE,
naturally).
I would vote having Plasma supporting it (not just khtml), since it
would allow, for example, users to set simple animated wallpapers
(i know... system resources... but it's not for the faint of heart,
anyway ;)
--
@jorge-lavila:
technically possible yes. I want to be careful with what I promise here,
as the user experience is not my area. With that said we are currently
looking at using aa-notify as a bridge to improve the user experience.
We would install it with a filter to only fire a notification for
@zgraft:
I have added a tor item, a profile will land in an update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation restrictions cause many
@jorge-lavila,
Its not a theoretical case, they have been used by multiple exploits
every year (including this one) since landing in the kernel. Ubuntu is
not the only ones looking at restricting them. SELinux has also picked
up the ability but they haven't really rolled it out in policy, there
Your understanding is mostly correct. There are as best I can tell, 2
exceptions with how things are setup atm
1. If the environment is setup to use early policy load, the init script
bailout won't stop that policy from being loaded. But it prevents it
from being live updated via systemctl reload
sadly yes, the init script has a bail out that stops loading policy on
the live cd. We are going to have to investigate this.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
s/live cd/live image/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065088
Title:
AppArmor profiles allowing userns not immediately active in 24.04 live
image
To manage notifications about this
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
@1fallen: it looks like there is something more going on here, can you
check your kernel log / dmesg for apparmor DENIED messages.
eg.
```
sudo dmesg | grep DENIED
```
--
You received this bug
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
As for upgrade vs. clean install. The unprivileged userns restriction is
enabled via a sysctl and upgrading will not enable it by default.
--
You received this bug notification because you are a member of
Paride,
I've updated the packages at https://launchpad.net/~john-
cabaj/+archive/ubuntu/asrdfd to include all versions in the changes file
for the new package. Let me know if anything else is amiss.
Thanks,
John
--
You received this bug notification because you are a member of Ubuntu
Bugs
Unfortunately there isn't a way to do this via abstractions or configs.
It would be possible to add a patch to the userspace and SRU it. This
would be the quickest solution while we work on the necessary kernel
changes to make the use of attach_disconnected unnecessary.
--
You received this bug
Does the profile have the attach_disconnected flag set?
Does the profile have the attach_disconnected flag set while in complain
mode?
It looks to me that we are looking at open file descriptors that exist
out of the current namespace. This will result in a partial unattached
path that will not
So while I don't think we are where snapd can get rid of the snap-
confine.internal snippets, with it now vendoring a more recent apparmor,
a lot of these can drop away. It doesn't need to detect capabilities
anymore.
It can just specify
deny capability perfmon,
and it will work, for all
@neigin: yes the capability to resolve this exists. So now it is a matter of
getting it functioning in snapd for these cases. This will get resolved I just
can't say when it will land.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@u-dal:
thankyou, though I have to say I am at a loss as to why the snap version
of thunderbird is trying to access
```
/media/lubuntu/drive/hq/email/thunderbird/awesomenough/.parentlock
/media/lubuntu/drive/hq/email/thunderbird/awesomenough/lock
```
what kind of configuration have you done? I
So my supposition on the overlay looks to be incorrect. Would you being
willing to attach your full mount information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064363
Title:
thunderbird snap
For the thunderbird issue I have created
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064363
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace
@u-dal:
can you attach the overlay mount information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064363
Title:
thunderbird snap on live systems "already running" but not responsive
To manage
Public bug reported:
Moving this here from
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844
snap policy on an overlay system is preventing thunderbird from running.
This is related to the snapcraft form report
https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
** Attachment added: "dmesg denial output"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064363/+attachment/5773409/+files/comment-106.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg denial output"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064363/+attachment/5773408/+files/comment-106.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@u-dal:
the problem with firefox (it has a snap profile and is allowed access to
user namespaces) is different than with chrome (no profile loaded), but
still might be apparmor related. Can you look in dmesg for apparmor
denials
```
sudo dmesg | grep DENIED
```
--
You received this bug
@u-dal:
are you running in a live cd environment? Something odd is happening on your
system, with some profiles loaded and systemctl reporting
ConditionPathExists=!/rofs/etc/apparmor.d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Paride, thanks for having a look. I don't expect Bionic/Focal/Jammy
to need backports for compatibility reasons, mostly because the latest
changes were to enable compatibility with the 6.8 kernel. Only Jammy
will need some form of compatibility with the 6.8 kernel as that will be
the last HWE
Virtualbox in focal and jammy (20.04 and 22.04) has migrated to
6.1.50-dfsg-1~ubuntu1.20.04.1
reminder that virtualbox is a multiverse package, meaning it relies on
community support at this time. Since we ar eon 6.1.x in 22.04 and
20.04, users can expect bugfixes and security fixes from the
@u-dal:
This sounds like the apparmor policy is not being loaded can you please
provide the output of
```
sudo aa-status
```
and
```
sudo systemctl status apparmor
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu just needs to update Audacious to version 4.2 to fix this.
See https://audacious-media-player.org/news/53-audacious-4-2-released:
- Prevent the Qt interface from popping up multiple error dialogs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> To clarify, this is not something that can be solved upstream in
apparmor, and a profile can't be accepted due to the nature of the path
location?
correct, if it is a unprivileged user writable location it can't be
fixed entirely upstream. It is possible for us to ship a profile that is
Public bug reported:
For a few weeks now my terminal has had an odd hang of up to nearly a second.
Usually on the first character I type in a line. I'd say it happens on at least
one out of 5 times. At first I thought that maybe it was something that bash
was doing in the background, but I
running privileged applications out of home is dirty. But it is the
situation we are in with user namespaces and app images as well. Ubuntu
will not ship a profile for a privileged executable in the users home or
a writable location of an unprivileged user. As this can be leveraged to
by-pass the
Commit 789cda2f089b3cd3c8c4ca387f023a36f7f1738a only controls the
behavior of unprivileged user namespace mediation.
With the unprivileged_userns profile loaded, when a user namespace is
created by an unprivileged unconfined application the task will be
transitioned into the unprivileged_userns
Balena Etcher 1.18 dpkg won't install on 24.04 due to dependency issues,
1.19.16 installs fine and runs, but in a degraded sandbox mode. So
adding a profile for it would be beneficial
The appimage version of Belena Etcher unfortunately fails to run. We can not
provide a default profile for the
The Wike fix is coming in the next SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation restrictions cause many applications
to crash with SIGTRAP
I want to add: I faced a similar issue. Though updating to the 550
drivers through apt seemingly fixed the issue, there was actually more
issues at play.
First and foremost, on the Wayland session, running "glxinfo | egrep "OpenGL
vendor|OpenGL renderer" returns:
"OpenGL vendor string: Mesa
I found a fix for this that at least works for me.
;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm
;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go
stat /usr/share/guile/3.0/ice-9/eval.scm
and
stat /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go
FWIW I also just tried 24.04 as well as the latest BIOS update (1.37).
The issue appears to be significantly worse. I was initially unable to
boot into a desktop environment at all.
Changing the BIOS setting for Display to Discrete (from Hybrid) meant
that everything worked but monitor detection
Its not just that app images don't have a default path, we can handle
that as well. It is that user namespaces have become a privileged
operation, and the user must take some privileged action to allow
applications to use them.
That can be any of
- moving the application into a well known
I experience this same issue on a fresh Noble installation. FWIW, this
is only with the Debian repository version - the Snap version of Remmina
is able to connect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unless there are other denials, this is not related to bug #2046844
Try adding the following rule to the torbrowser_firefox profile
allow rw /run/dbus/system_bus_socket,
and then reloading it with either
sudo systemctl reload apparmor
or by using
sudo apparmor_parser -r
Debdiffs provided. Packages also uploaded to
https://launchpad.net/~john-cabaj/+archive/ubuntu/asrdfd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063362
Title:
Backport for 22.04, 20.04
** Changed in: involflt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: involflt (Ubuntu Bionic)
Assignee: (unassigned) => John Cabaj (john-cabaj)
** Changed in: involflt (Ubuntu Focal)
Assignee: (unassigned) => John Cabaj (john-cabaj)
** Changed in: involfl
** Patch added: "Bionic 18.04 debdiff"
https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+attachment/5770457/+files/1-0.1.0-0ubuntu6~18.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Focal 20.04 debdiff"
https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+attachment/5770456/+files/1-0.1.0-0ubuntu6~20.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Jammy 22.04 debdiff"
https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+attachment/5770455/+files/1-0.1.0-0ubuntu6~22.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Request to backport Azure Site Recovery Disk Filter Driver to Jammy
- (22.04) and Focal (20.04)
+ [Impact]
+
+ * Request to backport Azure Site Recovery Disk Filter Driver to Jammy
+ (22.04), Focal (20.04), and Bionic (18.04)
+
+ [Fix]
+
+ * Simple re-package, with
To make this generic so that it will work on older and newer hosts we
should probably change the peer expression to
signal (receive) peer={runc,unconfined},
or possibly, define an @{runc} variable in the preamble and use that.
This really only is advantageous, in that it shows semantic intent,
Public bug reported:
Request to backport Azure Site Recovery Disk Filter Driver to Jammy
(22.04) and Focal (20.04)
** Affects: involflt (Ubuntu)
Importance: Undecided
Status: New
** Affects: involflt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects:
Thank you for your quick and helpful reply. A few quick checks make it
appear that reinstalling libssl as you suggested has completely resolved
the problem.
Thanks also for your suggestion about checking failing hardware. There
seems to be no sign of any errors in my drive, but I'll continue to
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063271
Title:
Illegal opcode in libssl
To manage notifications about this bug go to:
Public bug reported:
Description: Ubuntu 24.04 LTS
Release: 24.04
There is no "entire disk with lvm and encryption" option available.
When the "Erase disk" option is selected the entire disk is selected for
installation and the user is given the option to "Encrypt system" but there is
no
*should be changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061918
Title:
package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new
thunderbird package pre-installation script
I think release upgrader settings changed. To do deb2snap transitions
first before upgrade happens.
Because during upgrade, packages are inconsistent, and snap hooks must
be deffered until they are safe to execute on the system.
Note all other deb2snap transitions were always graceful and would
FWIW, looks like a Debian patch must already exist for this:
https://security-tracker.debian.org/tracker/CVE-2024-32462
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32462
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I will note that current snap behavior is by design. Not saying that
they couldn't make this easier but the snap side is functioning the way
it was desiged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for checking Aditya. I'll leave this open till you get some
guidance from VMware regarding any changes in Cloud Director that may be
affecting serial console connections.
I've also added this to our 24.04 release notes (to be published soon
for the clouds). Thank you a bunch for trying
1. what versions of VMware ESXi is this applicable?
2. is this reproducible in other environments, such as Virtualbox?
3. is this error true of all ubuntu images for those versions then? This was
added in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1895104
at the request of
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895104
Title:
It hangs during booting after deploy cloud image(.ova) and upgrade
** Changed in: zfs-linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Noble)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
unfortunately Joplin is only shipped as an appimage for Linux. Which
means we can not ship a profile for it by default that will allow it to
use capabilities within the unprivileged user namespace that the
electron embedded browser is attempting to use.
This means that the user is required to
I've tested an initial version with the upstream patch and attached the
debdiff here. Will work to get this uploaded.
** Patch added: "zfs-linux_2.2.2-0ubuntu9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2058179/+attachment/5767995/+files/zfs-linux_2.2.2-0ubuntu9.debdiff
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2061698/+attachment/5766302/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061698
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2061698/+attachment/5766301/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected jammy third-party-packages
** Description changed:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
the kernel team is already rolling kernels with the fix for 2061851 but
it is also building in https://launchpad.net/~apparmor-
dev/+archive/ubuntu/apparmor-devel ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is likely a dup of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061851
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061869
Title:
Snaps unable to connect to network under
Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
@DisatesR : if you're not seeing a 50-cloud-init.conf file, it indicates
to me that cloud-init is failing to parse the cloud_init configuration
properly, and thus not adding the required configuration to
/etc/ssh/sshd_config.d/
could you provide your entire cloud config? you can also use
Public bug reported:
Cannot obtain lock:E: Could not get lock
/var/lib/dpkg/lock-frontend. It is held by process 17406 (unattended-upgr)
W: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to acquire the dpkg frontend lock
Thanks for the suggestion.
I have passed your suggestions along to the Guest Customization team
along with links to this bug report in an internal bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
More applications will be getting confinement, on an individual level I
don't think it will be everything from debs. In this case its because it
uses unprivileged user namespaces. Which is now being restricted and
treated as a semi-privileged because it gives access to several
privileged kernel
There are vague plans, yes. The time line of it has not been scoped, but
it would be something akin to what happens on macos when you try to run
a downloaded application for the first time and you have to go into
their security config to allow it.
The application will still be "confined" but it
Alternative idea, what about instead of writing a wrapper:
1. look at https://packages.ubuntu.com/noble/libnet-ssleay-perl
a. libnet-ssleay-perl is in main
2. add eddsa-25519 to the list of constants upstream
a. if i'm reading correctly, there's a mapping in a
helper_scripts/constants.txt
1 - 100 of 55854 matches
Mail list logo
