This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-2ubuntu1
---
cyrus-sasl2 (2.1.27+dfsg2-2ubuntu1) jammy; urgency=medium
* d/p/0036-autoconf-270-fix.patch: fix configure.ac for autoconf 2.70.
This also fixes detecting and enabling GSS-SPNEGO in our build.
(LP: #19
Hi Lukas,
The jammy and impish do have this issue and will be fixed in v250[1],
FWIK, we will upgrade to v250 soon? let me know if you think I should
still prepare the workaround for impish and jammy.
[1] https://github.com/systemd/systemd/pull/20219
--
You received this bug notification becaus
Here is a demonstration as requested in Discourse. These steps were run
on a stock image of Ubuntu Impish taken from https://cloud-
images.ubuntu.com/impish/current/.
Showing the inconsistent behavior of the default settings if the goal is
private home directories. Both adduser and useradd creat
** Changed in: cyrus-sasl2 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1956833
Title:
No GSS-SPNEGO support in jammy
Status
why would you say you won't fix this? it would be easy to implement
systems and policies for ubuntu modders and upstream teams to
coordinate. at minimum, give upstream access to the crash reports,
issue trackers, etc.
it doesn't take manpower, you don't have to test. all you have to do is
forwa
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
There are frequently modifications made to Ubuntu packages which
upstream developers are not aware of or the Ubuntu version of a package
can be one or more versions behind the latest upstream version. For
these reasons the crash reports first come to Ubuntu and ideally are
then forwarded to the ups
** Changed in: ubiquity (Ubuntu Focal)
Milestone: None => ubuntu-20.04.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1951519
Title:
ubiquity 20.04.15.17 fails to bui
Also removed -prune primary as it conflicted with -depth, which is
automatically turned on by -delete.
** Patch added: "removed_prune_primary.patch"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+attachment/5553122/+files/removed_prune_primary.patch
--
You received this bug n
What series is this needed for? Does it already work as expected in
Jammy?
--
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/1955997
Title:
The airplane hotkey has no functio
Hello Timo, or anyone else affected,
Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.2.6-0ubuntu0.1~20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Timo, or anyone else affected,
Accepted mesa into impish-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/21.2.6-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Timo, or anyone else affected,
Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.2.6-0ubuntu0.1~20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
*** This bug is a duplicate of bug 1949553 ***
https://bugs.launchpad.net/bugs/1949553
focal will get this via impish backport
** This bug has been marked a duplicate of bug 1956915
New bugfix release 21.2.6
** This bug is no longer a duplicate of bug 1956915
New bugfix release 21.2.6
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Miguel Pires (miguelpires1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-pt-base in
Ubuntu.
https://bugs.launchpad.net/bugs/1932579
Title:
snap p
Ah, OK. I'll re-test and report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1938998
Title:
[vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not
r
Public bug reported:
what this proplim
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpython2.7-minimal (not installed)
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
Cas
Public bug reported:
3 weeks after installing 20.04.3
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture:
Public bug reported:
After migrating from Ubuntu 20 amd64 to aarch64 I started experiencing
"can't load seccomp filter" when doing `apt update && apt upgrade` and
"Kernel refuses to turn on BPF filters" when using Puppeteer.
I wrote about it more extensively here:
https://stackoverflow.com/questi
Hi Lukasz,
Carrier network providers use bearer information to carry the MTU
setting, this can be received by the modem then exposed to its host
system either via NetworkManager's ipv4_config or ipv6_config.
I think ipv4_config is the must supported setting in carrier's network,
that may be why t
Hey Jerry! This looks good and I can certainly sponsor it for you.
One question before I do that though. Looking at the original source commit:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
It is mentioned there
The bug has not been confirmed by another human. That's just the status
used by the kernel bot.
Since all the relevant packages (mesa, xorg-server and kernel) have been
updated since this bug was logged we would appreciate it if you could
retest.
If the problem still occurs then please consider:
Has this (now confirmed) problem been identified and fixed, and if so,
which versions of the package(s) contain the fix? With this information,
one could update to the version containing the fix and seeing if the
system actually works as expected. I now generally turn off the updates
for these pack
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915
** This bug has been marked a duplicate of bug 1956915
New bugfix release 21.2.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to me
So what about impish? Focal will soon get 21.2.x from impish.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1939455
Title:
Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915
** This bug has been marked a duplicate of bug 1956915
New bugfix release 21.2.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to me
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915
** This bug has been marked a duplicate of bug 1956915
New bugfix release 21.2.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to me
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.n
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Impish)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
Public bug reported:
[Impact]
This is the last point-release of the 21.2.x-series, we should put it in
impish so latest bugfixes would get there, and in focal for 20.04.4
image.
[Test case]
Install the updates, test desktop use and some basic games etc on at
least AMD and Intel hw.
[Where thin
32 matches
Mail list logo
