The debdiff is attached.
** Patch added: "modemmanager_1.20.0-1~ubuntu22.04.3.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/2047008/+attachment/5730935/+files/modemmanager_1.20.0-1~ubuntu22.04.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
The verified log is attached.
** Attachment added: "modemmanager_1.20.0-1~ubuntu22.04.3_verified.log"
https://bugs.launchpad.net/oem-priority/+bug/2047008/+attachment/5730937/+files/modemmanager_1.20.0-1~ubuntu22.04.3_verified.log
--
You received this bug notification because you are a
Public bug reported:
After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.
It seems that the crashed applications all used the QSettings. The
Hi, I'm on Ubuntu 23.10 using Brave browser SNAP and I still face the
issue (cannot open links in evince -using Brave browser snap).
Here are the versions:
```console
❯ apt list --installed | rg 'evince|apparmor'
apparmor/mantic,now 4.0.0~alpha2-0ubuntu5 amd64 [installed,automatic]
Thanks Damjan for the investigation work and the fixes, I've
cherrypicked the gcr fix and uploaded to Debian now (which will sync to
Ubuntu later today).
I would prefer to see an upstream review for the keyring change before
distro patching that one since the situation there is a bit more
I also made a mistake with a person who can help with this problem
https://github.com/codepayne/linux-sound-huawei/issues/27
** Bug watch added: github.com/codepayne/linux-sound-huawei/issues #27
https://github.com/codepayne/linux-sound-huawei/issues/27
--
You received this bug notification
How acceptable or possible would a solution be that had one universal
"allowUserNamespaces" attribute in an AppArmor config that could then
simply be set on whatever files one wanted to enable the features on?
That would support all third-party apps that a user deemed worthy
without needing much
I can't seem to get the xattr solution to work. I'm trying it on a
normal binary and it's failing like so:
# Contents of /etc/apparmor.d/falkon
abi ,
include
profile falkon xattrs=(security.apparmor=falkon) flags=(unconfined) {
userns,
include if exists
}
# setfattr command
Thanks, this definitely does point at debconf. However:
> Preconfiguring packages ...
This line is from /usr/sbin/dpkg-preconfigure, which is called via
/etc/apt/apt.conf.d/70debconf.
> Can't exec "/tmp/cryptsetup-initramfs.config.UaZ02N": Permission
denied at
No
--
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/1517030
Title:
ubuntu-bug (apport-kde) crashes every time I submit a problem report
Status in apport package in Ubuntu:
Pleasure Sebastien, that's how open-source works, we help each other and
all win :-).
I'm glad you are picking it up at the distro level, but that gcr-3 patch
alone won't fix this issue, as it only comes into play after gnome-
keyring-pkcs11.so is loaded, which won't happen without the gnome-
Thanks for testing. I am marking this bug as fixed. In case you can
trigger this bug again, please re-open it or open a new bug report.
Thanks.
** Changed in: apport (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
Unfortunately it has to be a privileged operation, otherwise any
application could set the attribute and then have access to user
namespaces. The problem with unprivileged user namespaces is that it
makes privileged interfaces available to the user in ways that they
weren't designed for, leading
Right, I do plan to cherry pick the gnome-keyring change at some point,
I just started with gcr while waiting to see if a gnome-keyring upstream
maintainer is still active to review the change
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
RE: security.apparmor attribute attachment not working
Sorry for the current version of apparmor in Ubuntu requires a path
attachment as well, you need to change the profile to (caveat untested
so I may have made another mistake too)
profile falkon /** xattrs=(security.apparmor=falkon)
$ readlink -f /var/cache/debconf/tmp.ci
/var/cache/debconf/tmp.ci
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/2043711
Title:
Open3.pm tries to run code in /tmp when
We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:
Setting up
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in openssh package in Ubuntu:
New
Bug
Fun, this isn't even reliable. The first atttempt failed:
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log
I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with
Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.
But it is a red herring due to the || true. The upgrade failed on
something
This system has remained substantially vanilla since the original
install - 18.04 if I remember correctly - with only LTS upgrades and I
have certainly made no local changes to the packaging tools.
$ which apt-extracttemplates
/usr/bin/apt-extracttemplates
$ debsums -s apt-utils
$
That is to say
Public bug reported:
In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
Ok. Then I still have absolutely no idea how/why this is happening for
you, because that doesn't seem to match the code we ship.
Unless you have some non-distribution version of the apt-
extracttemplates program installed? (which apt-extracttemplates; sudo
apt install debsums; debsums -s
23 matches
Mail list logo
