apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1958032/+attachment/5554967/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958032
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1958032/+attachment/5554965/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1958032/+attachment/5554964/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958032
Title:
[igb
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1958032/+attachment/5554966/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958032
apport information
** Tags added: apport-collected focal
** Description changed:
Hi,
I get no network connection established.
In dmesg I get repeatively messages regarding a TX hang and adapter reset:
[ 202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps
Hello, I am affected by the same bug.
The output of your command is the following:
gsettings list-recursively org.gnome.shell
org.gnome.shell enabled-extensions ['sound-output-device-choo...@kgshank.net']
org.gnome.shell command-history ['r']
org.gnome.shell remember-mount-password false
It looks like the last time we updated /boot partition sizing used by
the install was with the Artful (17.10) release of Ubuntu, so your
install was well before this and likely has small /boot partition. Given
that we can't do anything about the already installed system I'm going
to close this as
Public bug reported:
sudo apt-get install mouseemu
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
mouseemu
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 16.6 kB of
I attached a fix for the reported issue. However, since I am not
familiar with unzip, someone should review it. Thanks!
** Patch added:
"0001-Fix-null-pointer-dereference-and-use-of-uninitialized-data.patch"
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927192
Title:
gdb ftbfs on
Upstream bugfix released in https://github.com/OpenPrinting/cups-
filters/releases/tag/1.28.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912911
Title:
When printing with my Brother hl-2170w
If a package is covered by ESM-Apps but you don't have it enabled then
I'd expect the message to be "1 could receive security updates with ESM
Apps".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The reason I didn't want to do that in Debian is that x-d-p-gnome
Recommends gnome-shell, and circular Recommends prevent unused packages
from being autoremoved.
In Debian, the gnome-core metapackage Depends on x-d-p-gnome. I think
ubuntu-desktop pulling it in as a Recommends is also appropriate.
** Description changed:
Upstream raspberrypi patchset 2022-01-14
Ported from the following raspberrypi branch:
rpi-5.15.y
from https://github.com/raspberrypi/linux.git
drm/vc4: hdmi: Fix clock value used for validating hdmi modes
drm/vc4: Disable Gamma control on HVS5
However, audio going through USB on the X1 ThinkVision (called "Analog Output -
X1") is now playing correctly in Wayland with both monitors at 60Hz.
When selecting the television output "HDMI / DisplayPort - Vega 20 HDMI Audio
[Radeon VII]" on Wayland with 60Hz on both monitors, the playback
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Invalid => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Expired => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Triaged => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: In Progress =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed =>
This bug was fixed in the package linux - 5.15.0-17.17
---
linux (5.15.0-17.17) jammy; urgency=medium
* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)
-- Andrea Righi Thu, 13 Jan 2022 17:11:21
+0100
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This bug was fixed in the package libio-socket-ssl-perl - 2.074-2
---
libio-socket-ssl-perl (2.074-2) unstable; urgency=medium
[ Simon Chopin ]
* d/control: Drop libssl1.1 explicit dependencies (LP: #1957170)
-- gregor herrmann Thu, 13 Jan 2022 20:02:13 +0100
** Changed in:
This does not fix the issue. Playback is still double and high pitched in
Wayland with both monitors at 60Hz.
In Xorg I can still only select 30Hz as the maximum on the television.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: dnsdbq
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956639
Title:
FTBFS with glibc 2.34
To manage notifications about this bug go to:
According to /proc/cpuinfo, your processor doesn't appear to support
sse3, which is now a hard requirement for chromium, see
https://bugs.chromium.org/p/chromium/issues/detail?id=1123353. This has
been the case since version 89, released in April 2021.
There is unfortunately nothing that can be
golang-github-containers-toolbox 0.0.99.2-2ubuntu1 available in
ppa:xypron/gnu-efi fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958132
Title:
Build failure on riscv64
To manage
** Description changed:
-
Upstream raspberrypi patchset 2022-01-14
- Ported from the following raspberrypi branch:
- rpi-5.15.y
- from https://github.com/raspberrypi/linux.git
+ Ported from the following raspberrypi branch:
+ rpi-5.15.y
+ from
The attachment "18-lp1957094-adjust-on-demand-mode-description.patch"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
I just did a do-release-upgrade from impish to jammy (to check a
different situation) and I've got the above message (with the "%s"),
too:
┌┤ Pending kernel upgrade ├┐
│
Done. now after reboot starting gnome-software i see 'automatic update
paused' and if i click on 'find out more' i have a box saying 'the
current network is metered...'
and i'm unable to correct with
sudo systemctl restart packagekit
or
sudo systemctl restart NetworkManager.service
or
sudo nmcli
** Description changed:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit
** Description changed:
[Impact]
The newer version of Telegram Desktop, 3.1.1, which is currently in
Ubuntu 21.10 (Impish Indri), provides an important support for 64-bit
user identifiers. In the next few weeks will register users with UID
more than 2 ³¹ - 1 (maximal 32-bit signed
About the messages:
- The plurals are exactly as before, I didn't touch them, but I do agree that
it can be improved. `1 are` could also be fixed.
- The upper message is telling that the package is covered by ESM-Apps, and
receive security updates through ESM-Apps. The second part of the message
Thanks Simon. The MIR got accepted and xdg-desktop-portal-gnome added as
a recommends of ubuntu-desktop now. Do you think we should also make
gnome-shell Recommends the portal to increase the chance users who
install GNOME the non standard way would still get it?
** Changed in:
** Description changed:
[Impact]
No driver is loaded for MT7922, and fw is missing too.
[Fix]
Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
Enable 160Mhz channel.
[Test]
Verified on RZ616, it works fine, suspend OK.
iperf test result looks fine.
+ Bluetooth
** Description changed:
[Impact]
No driver is loaded for MT7922, and fw is missing too.
[Fix]
Add firmware of MT7922 wifi and bluetooth.
[Test]
Verified on RZ616, it works fine, suspend OK.
iperf test result looks fine.
Bluetooth works fine.
[Where problems could occur]
Public bug reported:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0
It looks like this issue is fixed on Ubuntu 20.04 but a similar issue persists
if `lvresize --resizefs` is called within a init-premount script (even though
lvresize and fsadm copied via coy_exec).
```
/sbin/fsadm: execvp failed: No such file or directory
Filesystem check failed.
exit code 5.
** Changed in: fwts
Status: In Progress => Fix Committed
** Changed in: fwts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914
Title:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1958153
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Dear developers,
unfortunately since a couple of days the installation of ghostscript
fails on Ubuntu. I can reproduce this and it happens consistently. I had
a CI that installed ghostscript working flawlessly for at least a month.
```
Run sudo apt-get install -y
Hello Nicholas, or anyone else affected,
Accepted libtgowt into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libtgowt/0~git20210627.91d836d+dfsg-3ubuntu1~20.04
in a few hours, and then in the -proposed repository.
Please help us by testing
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-January/127192.html (jammy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955383
Title:
Support Intel IPU6 MIPI camera on Alder Lake
Thanks for taking the time and trying to make Ubuntu better.
The information you provided is not enough to triage this bug. I see
there is a segmentation fault but it is not possible to figure out
what's happening without more information. You can try to provide a
backtrace for us to help us
Public bug reported:
[Impact]
No driver is loaded for MT7922, and fw is missing too.
[Fix]
Add firmware of MT7922 wifi and bluetooth.
[Test]
Verified on RZ616, it works fine, suspend OK.
iperf test result looks fine.
Bluetooth works fine.
[Where problems could occur]
It may break MT7921 wifi
Hi Claude,
Are you able to roll rsycn back to version 3.1.3-8 to see if this gets
fixed? In 2021-11-16, we got an update to fix LP #1896251. FWIW, this is
the upstream patch that was applied:
https://github.com/WayneD/rsync/commit/af6118d98b3482cbcfc223bf2a0777bc19eccb02
--
You received this
Hello everyone! Sorry I didn't get to this sooner. I'll perform reviews of both
the new telegram-desktop and libtgowt. Looking at Robie's initial assessment,
the main problems were:
a) Robie was looking for certainty and analysis that users will *certainly* be
broken, and
b) If a cherry-pick
Public bug reported:
The source includes a Test directory but those aren't run as part of the
build, it would be nice to do so and also to add some autopkgtest.
It was raised as something to fix as part of the MIR review even if it
was agreed it would not be a blocker for this cycle, the bug aim
nvidia-settings for focal
** Patch added: "18-lp1957094-adjust-on-demand-mode-description.focal.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554942/+files/18-lp1957094-adjust-on-demand-mode-description.focal.patch
--
You received this bug
** Description changed:
- Opening a placeholder MIR for now until seb has some time to look at it and
decide on a strategy:
- - either removing the recommends on suitesparse
- - or handle this MIR.
+ [Availability]
+ The package suitesparse-graphblas is already in Ubuntu universe.
+ The package
ubuntu-drivers-common for focal
** Patch added:
"0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554941/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch
--
skip debdiff for jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957094
Title:
on-demand mode doesn't work with nvidia-390
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958151
Title:
[SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922
ubuntu-drivers-common for impish
** Patch added:
"0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554940/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch
--
You
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1958151
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
[Impact]
No driver is loaded for MT7922, and fw is missing too.
[Fix]
Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
Enable 160Mhz channel.
[Test]
Verified on RZ616, it works fine, suspend OK.
iperf test result looks fine.
[Where
Same problem on Ubuntu 22.04
corrado@corrado-n3-jj-0103:~$ apt policy network-manager
network-manager:
Installed: 1.32.12-0ubuntu2
Candidate: 1.32.12-0ubuntu2
Version table:
*** 1.32.12-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100
Brian Murray (brian-murray)
It's tested other man on ubuntu 20.04 x64 and apple mac pro with m1 pro CPU.
GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
I will test it from lubuntu 20.04 x64 livecd and will add new results.
101 - 200 of 299 matches
Mail list logo
