Well you figured out the versions we stopped shipping it, so you could
have just read the changelog to find out why that happened.
But anyway, we no longer protect the last installed kernel.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.14) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
trafficserver/8.0.5+ds-3 (ppc64el)
linux-oem-5.14/5.14.0-1042.47 (amd64)
linux-hwe-5.11/5.11.0-61.61 (armhf)
Now I think we should file upstream bug reports with x2go (which I don't
use) and nomachine and get some clarity on whether they are doing the
login in compliance with up-to-date
https://www.freedesktop.org/software/systemd/man/systemd-
logind.service.html
--
You received this bug notification
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.14) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
trafficserver/8.0.5+ds-3 (ppc64el)
linux-oem-5.14/5.14.0-1042.47 (amd64)
linux-hwe-5.11/5.11.0-61.61 (armhf)
All autopkgtests for the newly accepted openssl (1.1.1l-1ubuntu1.4) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
nagios-plugins-contrib/35.20210511ubuntu2 (ppc64el)
nodejs/12.22.5~dfsg-5ubuntu1 (amd64)
swupdate/2020.11-2
All autopkgtests for the newly accepted openssl (1.1.1l-1ubuntu1.4) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
nagios-plugins-contrib/35.20210511ubuntu2 (ppc64el)
nodejs/12.22.5~dfsg-5ubuntu1 (amd64)
swupdate/2020.11-2
Public bug reported:
#> lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
#> apt-cache policy apt
apt:
Installed: 2.0.9
Candidate: 2.0.9
Version table:
*** 2.0.9 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100
Added -proposed, updated, and eduroam is happy again. Nice to have
something to tell the Ubuntu-wielding students/faculty/staff until we
get 'round to upgrading our Radius servers. Thank you for the fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
Thx for the retest!
With that I would go from Incomplete back to In Progress ...
** Changed in: ubuntu-z-systems
Status: Incomplete => In Progress
** Changed in: zlib (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of
--- Comment From i...@de.ibm.com 2022-06-15 14:00 EDT---
I don't really remember, so I retested.
20.04: 1.2.11.dfsg-2ubuntu1.3 fixes the problem (I had to install the .deb file
manually with dpkg).
22.04: 1.2.11.dfsg-2ubuntu9.1 fixes the problem.
--
You received this bug notification
I would like to proceed on this (to not loose to much time...)
To sum things up:
On top of the actual zlib fix,
there is another patch 'Remove compressBound assertions. (PR #1258)'
needed for htslib.
Unfortunately there is a standalone 'htslib' package,
as well as a htslib version included in
Public bug reported:
I use a USB keyboard plugged into a laptop running Ubuntu. The USB
keyboard has volume adjustment integrated into the function row: mute is
Fn + F1, decrease volume is Fn + F2, and increase volume is Fn + F3. On
Ubuntu 20.04.4, I could use these keys to do volume adjustment.
** Patch added:
"debdiff_bedtools_jammy_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu0.1.patch"
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597489/+files/debdiff_bedtools_jammy_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu0.1.patch
--
You received this bug
** Patch added:
"debdiff_bedtools_impish_from_2.30.0+dfsg-1_to_2.30.0+dfsg-1ubuntu0.1.patch"
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597490/+files/debdiff_bedtools_impish_from_2.30.0+dfsg-1_to_2.30.0+dfsg-1ubuntu0.1.patch
--
You received this bug
** Patch added:
"debdiff_bedtools_kinetic_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu1.patch"
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597488/+files/debdiff_bedtools_kinetic_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu1.patch
--
You received this bug
** Description changed:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15 hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not
This bug was fixed in the package bluez - 5.48-0ubuntu3.9
---
bluez (5.48-0ubuntu3.9) bionic-security; urgency=medium
* SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
before attempting
This bug was fixed in the package bluez - 5.53-0ubuntu3.6
---
bluez (5.53-0ubuntu3.6) focal-security; urgency=medium
* SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
before attempting to
This bug was fixed in the package keyutils - 1.6.1-3ubuntu1
---
keyutils (1.6.1-3ubuntu1) kinetic; urgency=medium
* Merge from Debian unstable (LP: #1977982).
Remaining changes:
- d/p/apply-ttl-records.patch: Add patch to apply default TTL to records
obtained from
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mariadb-10.6 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mariadb-10.6 (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in:
As usual with non-security updates, we use the results of autopkgtest in
order to perform the verification. In this case, all tests succeeded
for openldap in Jammy. Therefore, tagging as verification-done-jammy.
** Tags removed: verification-needed verification-needed-jammy
** Tags added:
Tim Richardson, I recognize your effort and contribution to solve the
problem, but without my comment in #33, where I must say I were not very
nice, you would not have clarified that cgroups v2 was enabled again.
Maybe you stated that with nomachine community, but not here.
Not stated before my
I have been reading a bit more. I'm starting to form the impression that
this problem may originate from the way our various remote solutions are
logging in. They may not be doing it the proper modern login-systemd
way. This would mean that nomachine, x2go are both wrong.
--
You received this
Hello, any idea when the fix will land 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/1970634
Title:
FTBFS: mariadb fails to start due to low MEMLOCK limit
Ubuntu 20.04 is also affected by this bug in the same way.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1977645
Title:
python3-gpg "1.16.0-unknown" version is
And let us hope that someone who can fix it steps up and fixes it
properly because right now, ubuntu 22.04 and derivatives are unfit for
remote desktop deployments.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I'm just an ordinary user trying to get this working and volunteering what I
learn, so bear that in mind. I have no real clue about what the problem is and
I still don't understand where in the session start process
DBUS_SESSION_BUS_ADDRESS is set and why we get a wrong value when starting
Accepting this into Bionic blocked on bug 1940141, and it's further
noted there that there's an openssl security update expected on 21 June,
so it's probably best to rebase on that when it arrives.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thank you for the comments. These seem like good ideas, but need details
before they are actionable.
I think this update is still blocked on having a specific, step-by-step
test plan please.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
What's the current status of this please?
Julian's last comment suggests that there's a problem?
I see an upload in the queue for Bionic, but not for Focal. What's the
status in Focal?
Is this something that can be staged in proposed, or do you need it in
the updates pockets, and if so, why?
Public bug reported:
$ apt-cache policy openssh-server
openssh-server:
Installed: 1:8.2p1-4ubuntu0.4
Candidate: 1:8.2p1-4ubuntu0.4
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.4 LTS
Release:20.04
Codename: focal
After
** Tags added: dt-394
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1864215
Title:
Please add webp loader to gdk-pixbuf
Status in gdk-pixbuf:
Fix Released
Status
** Tags added: dt-392
--
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/1969896
Title:
Evince Document Viewer(42.0) does not remember last page in 22.04 and
opens in a
Tim, yes it works adding the environment variable, but you wrote "I
should have been clearer" in comment 35, but that is wrong, you should
at least had mentioned that you did enabled the cgroupsv2, and from
comment 27 to comment 32, there are no mention about reverting
I enabled propsed and updated wpasupplicant to 2:2.10-6ubuntu2 and I'm
now able to connect to the corporate WiFi network again. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
This is still an issue. I like the idea of deleting the bond (e.g.
"networkctl delete bond0" during the "netplan apply" call. But as stated
before by daxtens, we need to make sure not to bring down critical
interfaces, that might be in use.
We could either only apply this only to interfaces, that
This seems to be working nowadays. I cannot reproduce using the config
provided in the description:
$ netplan apply
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
Netplan generates configuration snippets to make sure an interface is
only handled by the backend renderer (networking-daemon: sd-networkd or
NetworkManager) that is instructed to control that interface nowadays.
This logic has been improved recently:
https://github.com/canonical/netplan/pull/276
See also https://gitlab.gnome.org/GNOME/mutter/-/issues/2307
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2307
https://gitlab.gnome.org/GNOME/mutter/-/issues/2307
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2307
Importance: Unknown
** Changed in: linux-raspi (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
Tim,
Two "Thank-you"s for you:
1. "spamming" elsewhere and here. Indeed, I got redirected here after I saw
your comments at snapcraft forum
2. Correctly specifying the bus address for the session by setting
DBUS_SESSION_BUS_ADDRESS. This worked like magic! My Ubuntu 22.04 running KDE
** Summary changed:
- NOt able to Install any updates
+ [Intel 9560] wifi connection does not work properly
** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
PS I do not think this is a bug in snap. It is a bug with the way the
session is being setup. I don't know what the bug is, I have spend some
hours trawling through bug reports and following clues (I tried to be
useful). My "spam" on the snapcraft bug was a helpful note directing
readers here,
I do not have cgroups disabled, I reverted that earlier change. My fix
works with cgroupsv2, at least for my xfce4 session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I've commented before, but if your desktop session is correctly set up,
the systemd --user instance should be available, then a transient scope
can be created for snap and proper device access filtering can be set up
in that cgroup, thus completing the sandbox. Cgroup v1 works
differently, in that
Public bug reported:
I am not able to say much, since I don't know how to describe the
problem. Yet I can mention that whenever I am trying to download the
files like whatever is required to upgrade the software, the wifi
connection does not work properly(Mobile Data, usually). I have checked
if
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
48 matches
Mail list logo
