See attached screenshot.
** Attachment added: "Screenshot showing result after apt upgrade"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+attachment/5553494/+files/ss75.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I've checked, and the problem is still there. The update:
~ $ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
Fixed in gwenview version 21.12.1.
---
gwenview (4:21.12.1-0ubuntu1) jammy; urgency=medium
* New upstream release (21.12.1)
-- Rik Mills Thu, 06 Jan 2022 10:21:02 +
** Changed in: gwenview (Ubuntu)
Importance: Undecided => Medium
** Changed in: gwenview (Ubuntu)
Status:
This sounds related, but it was closed by Cinnamon blaming the graphics
library:
https://github.com/linuxmint/cinnamon/issues/10067
and is now in:
https://bugzilla.redhat.com/show_bug.cgi?id=1956512
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks.
It looks like there's a basic texturing problem in OpenGL. Since that's
done entirely in software for VMs, this should be assigned either to
Mesa or to Cinnamon itself. I don't think we need to involve the kernel.
** No longer affects: linux (Ubuntu)
** No longer affects: xorg-server
This seems to be an upstream issue:
https://github.com/libexpat/libexpat/issues/501
With that said, it doesn't seem like an upstream fix is likely any time
soon, as is suggested by this comment by one of the members of the
`libexpat` GitHub team on this NixOS pull request addressing this issue:
Public bug reported:
When running `lscpu` on arm64, the number of sockets is not populated.
This is seen on both Raspberry Pi hardware and in the autopkgtest
environment. Example output:
Architecture:aarch64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little
Fixed in wpa version 2:2.9.0+git2026+0b853303ae31-1
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
*** This bug is a duplicate of bug 1955297 ***
https://bugs.launchpad.net/bugs/1955297
** This bug has been marked a duplicate of bug 1955297
Xorg freeze
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Okay, so the current patch is for Focal? Please also provide debdiffs
for Jammy and Impish, as we'll stick with v249 (in Jammy) for the LTS
and Impish will not see a systemd update either. We need to fix it in
Jammy first, before we can start SRUing the change.
** Also affects: systemd (Ubuntu
Public bug reported:
tried with nvidia 390 driver also ,but no improvement
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture:
Public bug reported:
During update occured a system error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
ApportVersion:
I have installed version 21.2.6 by:
sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade
since some time.
I never had noticed problems and bug 1950044 was fixed by that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged => In Progress
--
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/1957076
Title:
sync cyrus-sasl2
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
Public bug reported:
It has the fix for bug #1956833, which is our only delta presently.
** Affects: cyrus-sasl2 (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: Triaged
** Tags: needs-merge
--
You received this bug notification because you are
We were recently hit by bug #1956833, where GSS-SPNEGO was suddenly
disabled and nobody noticed until an app tried to use it.
For that case, I'm thinking about a very simple test that would be like
this:
for algo in $ALGORITHMS; do
saslpluginviewer -m $algo > /dev/null || {
echo "Algorithm
Hi everyone,
small progress report :
I tried the pipewire trick and it didn't work out for me, while it initially
seemed to work: auto switch to the HSP/HPF profile didn't work and after a
manual switch the headset would drop out during a conversation.
I reverted to pulseaudio and invested a
Public bug reported:
Full log (same on all architectures):
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz
The test is from systemd:
https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619
Tail of the log:
```
ERROR:
Hi Marc,
will the issue of dns specified in network-manager not being forward in vpn
tunnel when using openvpn (bug occuring ONLY on current ubuntu 21.10)
will it be solved on next ubuntu release??
I really hope so since it will be a LTS
(dns leaks are common on linux when using openvpn and
** Changed in: cyrus-sasl2 (Ubuntu)
Milestone: None => ubuntu-22.01
--
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/1957076
Title:
sync cyrus-sasl2 2.1.27+dfsg2-3
This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3
---
cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium
[ Andreas Hasenack ]
* Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152)
-- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100
** Changed in:
ubuntu@lp1949970-i:~$ dpkg -l lightdm|grep lightdm
ii lightdm 1.30.0-0ubuntu4
amd64Display Manager
ubuntu@lp1949970-i:~$ journalctl -b -g 'unable to dlopen'
-- Journal begins at Tue 2022-01-11 17:28:57 UTC, ends at Tue 2022-01-11
17:59:05
ubuntu@lp1949970-f:~$ dpkg -l lightdm|grep lightdm
ii lightdm1.30.0-0ubuntu4~20.04.1 amd64Display Manager
ubuntu@lp1949970-f:~$ journalctl -b -g 'unable to dlopen'
-- Logs begin at Tue 2022-01-11 17:28:51 UTC, end at Tue 2022-01-11 18:02:33
UTC. --
Jan 11 17:58:09 lp1949970-f
I think we should ignore hirsute since it reaches EOL next week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1949970
Title:
attempt to dlopen nonexistent
Public bug reported:
openssh-server tries to restart itself, but openssh-server reports port
22 in use. This is true: systemd has taken port 22 to start sshd if one
connects to port 22.
two solutions:
1. dont start sshd after installing.
configure it without starting it afterwards.
2. stop
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu1.6
---
exiv2 (0.27.3-3ubuntu1.6) hirsute-security; urgency=medium
* SECURITY REGRESSION: out of range access that may cause a crash
- debian/patches/CVE-2021-37620-4.patch: fix out of range access that may
cause a
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu4.1
---
exiv2 (0.27.3-3ubuntu4.1) impish-security; urgency=medium
* SECURITY REGRESSION: out of range access that may cause a crash
- debian/patches/CVE-2021-37620-4.patch: fix out of range access that may
cause a
It seems to be like this is a bug in encfs rather than in rsync? I
appreciate newer rsync might have changed behaviour, but ultimately
encfs needs to provide a regular (if virtual) filesystem. Where it
doesn't, rsync can't be expected to work.
Is there any specific reason to think that encfs is
** Changed in: oem-priority
Status: Triaged => In Progress
--
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 function on a
This bug was fixed in the package exiv2 - 0.27.2-8ubuntu2.7
---
exiv2 (0.27.2-8ubuntu2.7) focal-security; urgency=medium
* SECURITY REGRESSION: fix out of range access
* Bugfix: Fix regression introduced when fixing CVE-2021-37620 (LP:
#1941752)
-
Result of the repro:
#2 ipv6 fails and gets into a loop
dig @10.241.3.1 -t math.lab
#2a - Good case (dnsmasq 2.85)
root@j-dnsmasq-release:~# dig @10.241.3.1 -t math.lab
dnsmasq: query[] math.lab from 10.241.3.1
dnsmasq: config math.lab is NODATA-IPv6
; <<>> DiG 9.16.15-Ubuntu
As usual once you know what you search for the results are much better.
It turns out that it might be related to one of those reports:
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016015.html
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016069.html
But
# FYI cleanup
# Minimal Reset (e.g. when switching dnsmasq)
killall dnsmasq
rm /tmp/dnsmasq*
dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log
--conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind-interfaces
--interface=router_eth42 --except-interface=lo
Detailed Logs:
Before the test:
dnsmasq.log is identical
dnsmasq-vpn.log as well, except the version number
Good Case:
ubuntu@autopkgtest:~$ resolvectl query math.lab
math.lab: 10.241.3.3 -- link: testvpnrouter
-- Information acquired via protocol DNS in 20.8ms.
-- Data
Reproducing the case outside the systemd tests
(Commands on Ubuntu 22.04, with root permissions)
jammy-Proposed has dnsmasq 2.86 right now
apt update; apt upgrade -y; apt install dnsmasq-base
systemctl reset-failed systemd-networkd systemd-resolved
mkdir /run/systemd/resolved.conf.d
cat >
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4.21.10.1
---
lightdm (1.30.0-0ubuntu4.21.10.1) impish; urgency=medium
* debian/lightdm.lightdm-greeter.pam,
debian/lightdm.pam:
- Suppress log error for missing pam modules (LP: #1949970)
-- Dan Streetman Fri,
The verification of the Stable Release Update for lightdm has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4~20.04.2
---
lightdm (1.30.0-0ubuntu4~20.04.2) focal; urgency=medium
* debian/lightdm.lightdm-greeter.pam,
debian/lightdm.pam:
- Suppress log error for missing pam modules (LP: #1949970)
-- Dan Streetman Fri, 05
39 matches
Mail list logo
