** Description changed:
+ Christian summarizes this after the great reports by Martin:
+
+ gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3
+ and added more later.
+
+ Due to that anything linked against gnutls while being apparmor isolated
+ now hits similar denials, preven
There is precedence in /etc/apparmor.d/abstractions/base holding various rules
like these
$ grep etc_ro /etc/apparmor.d/abstractions/base
@{etc_ro}/locale/** r,
@{etc_ro}/locale.alias r,
@{etc_ro}/localtime r,
@{etc_ro}/bindresvport.blacklistr,
@{etc_ro}/ld.so
Suggestion would be something like:
--- /etc/apparmor.d/abstractions/crypto.orig2024-03-11 11:05:24.027597234
+
+++ /etc/apparmor.d/abstractions/crypto 2024-03-11 11:06:12.035895701 +
@@ -24,4 +24,7 @@
/etc/crypto-policies/*/*.txt r,
/usr/share/crypto-policies/*/*.txt r,
+ #
Hey,
I think everything in the gnutls/ directory should be allowed: there can
be profiles with arbitrary names (or at least alnum I guess) which
define priority/configuration strings that can be used by gnutls
applications. I'm not aware of anything else that typically goes there
but I haven't che
Public bug reported:
pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
that has done the time_t transition.
test_gi.py runs a time_t test that I believe is using functions in
glib2.0
Test log excerpt
tests/test_gi.py
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2056753
Title:
pygobject FTBFS on armhf: time_t build test failure
Status in pygobject packa
** Also affects: initramfs-tools (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/apparmor/+git/apparmor/+merge/462142
--
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/2056739
Public bug reported:
I'm trying to report a bug in the new Snap for Thunderbird.
When I run "ubuntu-bug thunderbird", it:
* Collects information correctly after I input the sudo password
* Opens a page like
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
which
Marking thunderbird as affected as well, since the bug is specific to
it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2056758
Title:
ubuntu-bug doesn't let me file bugs
Definitely, I'm doing something very wrong.
I deployed a new VM (VMware) through MaaS, using the original initrd.
Applied the patch and did the same things I mentioned in my comment
above.
This time, the keyboard does not work (seems to be stuck; I'm not able
to scroll up to see what happens).
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
Please do not delete files, certainly not ubuntu.sources, or you will no
longer get updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Also affects: gobject-introspection (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.gnome.org/GNOME/gobject-introspection/-/issues #494
https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/494
** Also affects: gobject-introspection via
https://git
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager
in t
s.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.manifest
[2]
https://cockpit-logs.us-east-1.linodeobjects.com/pull-6048-20240311-125838-b465e9b2-ubuntu-stable-other-cockpit-project-cockpit/log.html#118
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Statu
** Changed in: gobject-introspection
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2056753
Title:
pygobject FTBFS on armhf: ti
** Summary changed:
- All Snaps are denied the ability to use DBus for notifications and apptray
indicators
+ All Snaps are denied the ability to use DBus for notifications and apptray
indicators in Kubuntu
** Summary changed:
- All Snaps are denied the ability to use DBus for notifications an
Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that
unshare --user --map-root-user /bin/bash -c whoami
(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.
I am starting to test Cockpit on the curren
** Changed in: gobject-introspection (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2056753
Title:
pygobject FTBFS on
After this update of this package "alsa-ucm-conf:amd64" the system
volume it's working as expected. So far, the issue is gone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/b
Something I forgot to mention, and it may be relevant after seeing the
comment above: I'm using the HWE kernel for Jammy.
Is it better to rollback to Focal with the default kernel?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
--
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/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committ
I am not sure I fully understand the latest comment. Does it mean that
8.0p1-19.0.1 just works? What about 8.0p1-19.0.1.2, mentioned in [1]?
[1] https://linux.oracle.com/errata/ELSA-2024-12164.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the s
I have read in a couple other pages that I can edit
/etc/apparmor.d/firefox. Since I'm using version 124 beta 9, and my
firefox is installed in /opt/firefox, do I just adjust the path in that
file to make it work? Thanks much in advance for the help.
--
You received this bug notification because
I think you can continue with your current kernel. We should back-port
this to all LTS
--
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/2056187
Title:
fails to confi
nice!
--
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/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix
This issue is also affecting me, and I do not have experience with
apparmor profiles to update the correct file.
Can someone explain in more details a patch that fixes the issue ?
(more precisely: what line should I write ? in what file ?)
Obviously: it is also a pain to have this issue with the
@gvarouchas, you need to be more specific. There are a couple interrelated
issues in this bug. What is the exact Denial message you are getting. The will
look something like the denial messages in comment 5. You can find them using
sudo dmesg | grep DENIED
or
journalctl -g apparmor
--
You r
I wonder if the latest update to Jammy has fixed the issue? Is this
issue still occurring for you when upgrading to the Jammy package
version 2.90-0ubuntu0.22.04.1 Julia?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq
As a temporary patch on my system, I disabled the apparmor rules for
/usr/sbin/runc
Following the documentation to disable one single apparmor profile
(link: https://help.ubuntu.com/community/AppArmor#Disable_one_profile )
:
```
sudo ln -s /etc/apparmor.d/usr.sbin.runc /etc/apparmor.d/disable/
su
Public bug reported:
From systemd version 245+ an option was added x-initrd.attach
-
Setup this encrypted block device in the initrd, similarly to
systemd.mount(5) units marked with x-initrd.mount.
Although it's not necessary to mark the mount entry for the root file
system with x-init
Public bug reported:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
Another peculiarity is that right clicking on the right side and lower
side
Thank you for the bug, Heather! I'm marking Bionic as "Won't Fix", as it's EOL.
If needed, please re-target against Pro 18.04. Thanks!
** Changed in: systemd (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
This is just malicious. You are not only packacking Ubuntu as adware,
you are making it deliberately harder to unbreak for people interested
specifically in spam removal.
While Ubuntu with easily removed ads would be still adware it would be
at least less annoying for people wishing to fix it.
An
> Canonical needs to make money and those ads aren't spammy at all.
I get ads on every single SSH login, that is incredibly spammy.
Currently for me that is majority of ad consumption and I will get rid
of it even if it means migration of several servers I am managing to a
different OS.
--
You r
36 matches
Mail list logo
