date:20210519

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-40.2 fixed-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915929

Title:
  gnome-shell-calendar-server assert failure on arm64: double free or
  corruption (fasttop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928702] Re: 21.04 - Bay Trail - Annoying Graphic Artifacts

2021-05-19 Thread Kai-Heng Feng

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928702

Title:
  21.04 - Bay Trail - Annoying Graphic Artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928702/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920187] Re: Installer failure Lenovo Yoga

[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: grub-installer (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920187

Title:
  Installer failure Lenovo Yoga

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920583] Re: daily software update on ubuntu20.04 removed docker cannot reinstall!

[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920583

Title:
  daily software update on ubuntu20.04 removed docker cannot reinstall!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1920583/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19

2021-05-19 Thread Po-Hsu Lin

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: ubuntu-qrt-apparmor

** Tags added: sru-20210510

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192

Title:
  test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure
  with linux/5.11.0-18.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/192/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

2021-05-19 Thread Po-Hsu Lin

** Summary changed:

- evlink_port_split linux ADT test failure with linux/5.11.0-18.19 ( list index 
out of range)
+ devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure 
with linux/5.11.0-18.19 ( list index out of range)

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20210510 ubuntu-kernel-selftests

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928889

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928890] Re: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

2021-05-19 Thread Po-Hsu Lin

** Summary changed:

- vrf_route_leaking linux ADT test failure with linux/5.11.0-18.19 (Ping 
received ICMP Packet too big)
+ vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure 
with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20210510 ubuntu-kernel-selftests

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928890

Title:
  vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929009] Re: ubuntu install crashes said hardware problem

2021-05-19 Thread Chris Guiver

Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-

May 20 03:28:18 ubuntu kernel: [  229.997017] SQUASHFS error: zlib 
decompression failed, data probably corrupt
May 20 03:28:18 ubuntu kernel: [  229.997024] SQUASHFS error: 
squashfs_read_data failed to read block 0x171bfa76
May 20 03:28:18 ubuntu kernel: [  229.997174] SQUASHFS error: zlib 
decompression failed, data probably corrupt
May 20 03:28:18 ubuntu kernel: [  229.997177] SQUASHFS error: 
squashfs_read_data failed to read block 0x171bfa76

Examining the information you have given us, this does not appear to be
a useful bug report so I am closing it, as it appears to be a bad ISO or
faulty device (inc. bad write-to-device).  I suggest you verify your ISO
download, and use the 'check disc for defects' option to validate your
media before install to ensure a good download & write.

If you believe I'm in error, please leave a comment explaining why and
change the status back to 'New'.


Possibly useful : 
https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0 and 
https://help.ubuntu.com/community/Installation/CDIntegrityCheck  (where CD 
refers to your install media, be it CD, DVD, HDD, SSD, thumb-drive etc)

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929009

Title:
  ubuntu install crashes said hardware  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-19 Thread handsome_feng

Hi, Gunnar,

After talking to our partners such as Sogou, they want to postpone this
migration until 22.04 so that they have enough time to work on the
adaptation, is this possible?

Thanks,
handsome_feng

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-19 Thread handsome_feng

** Changed in: ubuntukylin
   Status: New => 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/1928360

Title:
  Switch to Fcitx 5 for Chinese

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone

2021-05-19 Thread Benoit Yelle

** Changed in: rhythmbox (Ubuntu)
   Status: Fix Committed => 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/1864178

Title:
  Rhythmbox crashes when trying to connect to iPhone

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1864178/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929009] [NEW] ubuntu install crashes said hardware problem

2021-05-19 Thread Han Cat Nguyen

Public bug reported:

Ubuntu 18.04 error while installing, mentioned as some hardware error,
but Windows running  fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.15
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CasperVersion: 1.394.3
CurrentDesktop: ubuntu:GNOME
Date: Wed May 19 20:28:56 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929009

Title:
  ubuntu install crashes said hardware  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836019] Re: shotwell hangs with high cpu usage when dir contains many image

2021-05-19 Thread Bug Watch Updater

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=794678.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-03-25T20:03:37+00:00 Jérôme de Bretagne wrote:

Hi,

First of all, thanks for this great software.

I've been trying to get rid of many _shotwell.jpg / _shotwell_1.jpg /
_shotwell_2.jpg files today, without success so far.

The issue I'd like to raise is that when closing Shotwell, either from
the menu or with the usual close button, the application doesn't fully
stop right away and keeps running in the background, taking a
significant part of the system resources (it looks like a full CPU core
at 100% out of 4).

This is a really unusual behavior among desktop apps, it can decrease
the battery life drastically on a laptop if the user doesn't notice, and
there is no message informing the user or offering a way to control this
when closing the app.

Launching Shotwell with export SHOTWELL_LOG=1 shows in the logs that it
was in fact still creating new thumbnails for the recently modified
pictures (the ones ending in _shotwell.jpg that it has recreated after
my deletion attempt) and it finally stopped after a bit more than an
hour.

>From a user point of view, this is really disturbing. Would it be possible to:
1/ properly stop all long-running background actions (such as thumbnail 
creation) as soon as the app has been closed by the user?
2/ and maybe offer an option in the settings for users that like the current 
beavhior?


Personally, if I want to keep things running, I simply keep an app open but 
minimized. But as soon as I close an app, I expect it to stop taking system 
resources (and certainly not to keep using 25% of total CPU resources for 1h+ 
long).

I don't know if this is a design decision or if I've hit a bug, so let
me know if you would need any other input. Btw, I've seen this using the
master branch, compiled on commit:
b5dd17ea16b1a44933fb65378dc5a30971dcec5a

Thanks a lot,
Jérôme

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/0


On 2018-03-25T20:05:50+00:00 Jérôme de Bretagne wrote:

Created attachment 370124
Extract of shotwell.log showing a small subset of all the thumbnail creations

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/1


On 2018-03-25T21:42:06+00:00 Jens Georg wrote:

Did you move your library to a different place? This sounds like bug
771613

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/2


On 2018-03-25T21:43:35+00:00 Jens Georg wrote:

Either way, the Cache definitely should not be running when closing the
window. That's a bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/3


On 2018-03-25T22:16:59+00:00 Jérôme de Bretagne wrote:

Thanks Jens. I can't tell for sure as I've moved my photo set onto
different disks and then laptops, but I thought I had kept the same base
directory.

Looking at bug 771613, I may be hit by that one indeed. I'll try to see
if I can clean my database manually as suggested there.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/4


On 2018-04-01T21:26:41+00:00 Jérôme de Bretagne wrote:

With a bit of delay: I can confirm that the trigger of the issue was
indeed the same bug 771613, as you had guessed.

I had changed my username when changing laptops and looking at the
database, the older filepath entries in BackingPhotoTable were still
pointing to the older location in /home/old_user and not in
/home/new_user. Creating a symlink did the trick for me to make the
filepath correct, as a quick workaround. Maybe the filepath should be
relative instead of absolute for RAW + JPG pairs?

Anyway, launching Shotwell right after the symlink creation still took
quite a lot of resources the very first time, and closing the window
didn't stop all the background activities once again, which is the main
topic of this bug. I've let it finish and I've taken the logs, that I'm
attaching in case they contain something useful.

Now, I'm back with a stable and efficient Shotwell, that's a relief.
I'll still need to fix the filepath in the database at some point
though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/comments/5

[Bug 1929008] [NEW] SDDM (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-2ms), your system is too slow

2021-05-19 Thread jhthayer

Public bug reported:

Have been trying to deal with this for 3 months now.  Have to use vt2
and startx.  More stuff is dicey than this, but this has been wrong from
installation.

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929008

Title:
  SDDM (EE) client bug: timer event3 debounce short: scheduled expiry is
  in the past (-2ms), your system is too slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1929008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic

2021-05-19 Thread Mariusz

Hi,

I have done another test and compared the same server running on
4.15.0-136-generic and kernel 4.15.0-142-generic. Collected zabbix CPU
utilization graph which is showing the problem from the performance
point of view. On 4.15.0-136-generic, the server works normal and there
are no processes stuck on 99% iowait. On 4.15.0-142-generic it is not
working at all and rsync, pg_receivewal or dd processes are hanging with
iowait 99%. I attached the zabbix graph to this bug.

** Attachment added: "kernel_issue.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+attachment/5498858/+files/kernel_issue.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928744

Title:
  Disk IO very slow on kernel 4.15.0-142-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846790]

2021-05-19 Thread Qa-admin-q

Dear pernegger,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846790

Title:
  [upstream] Saving files with a '#' in the name silently(!) fails on
  GVFS smb:// paths (Samba share)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929006] [NEW] package tftpd-hpa 5.2+20150808-1ubuntu1.16.04.1 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1

2021-05-19 Thread jnn

Public bug reported:

:~$ sudo apt install nfs-kernel-server 
正在读取软件包列表... 完成
正在分析软件包的依赖关系树   
正在读取状态信息... 完成   
nfs-kernel-server 已经是最新版 (1:1.2.8-9ubuntu12.3)。
升级了 0 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 13 个软件包未被升级。
有 1 个软件包没有被完全安装或卸载。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
正在设置 tftpd-hpa (5.2+20150808-1ubuntu1.16.04.1) ...
tftpd user (tftp) already exists, doing nothing.

tftpd-hpa directory (/home/j/tftp) already exists, doing nothing.
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
insserv: warning: script 'K01tftpd-hpa' missing LSB tags and overrides
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
initctl: 无法连接到 Upstart: Failed to connect to socket /com/ubuntu/upstart: 拒绝连接
insserv: warning: script 'tftpd-hpa' missing LSB tags and overrides
Job for tftpd-hpa.service failed because the control process exited with error 
code. See "systemctl status tftpd-hpa.service" and "journalctl -xe" for details.
invoke-rc.d: initscript tftpd-hpa, action "start" failed.
● tftpd-hpa.service
   Loaded: loaded (/etc/init.d/tftpd-hpa; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since 四 2021-05-20 10:37:22 CST; 14ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 27782 ExecStart=/etc/init.d/tftpd-hpa start (code=exited, 
status=1/FAILURE)

5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: Rather than invoking init scri...)
5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: utility, e.g. service tftpd-hp...t
5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: initctl: 无法连接到 Upstart: F…接
5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: Since the script you are attem...n
5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: Upstart job, you may also use ...a
5月 20 10:37:22 j-G31M-S2L tftpd-hpa[27782]: start: 无法连接到 Upstart: Fai…接
5月 20 10:37:22 j-G31M-S2L systemd[1]: tftpd-hpa.service: Control process e...1
5月 20 10:37:22 j-G31M-S2L systemd[1]: Failed to start tftpd-hpa.service.
5月 20 10:37:22 j-G31M-S2L systemd[1]: tftpd-hpa.service: Unit entered fail
5月 20 10:37:22 j-G31M-S2L systemd[1]: tftpd-hpa.service: Failed with resul
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: 处理软件包 tftpd-hpa (--configure)时出错：
 子进程 已安装 post-installation 脚本 返回错误状态 1
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tftpd-hpa 5.2+20150808-1ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.15.0-139.143~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-139-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
AptOrdering:
 tftpd-hpa: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu May 20 10:37:23 2021
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2020-12-29 (141 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: tftp-hpa
Title: package tftpd-hpa 5.2+20150808-1ubuntu1.16.04.1 failed to 
install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.init.d.tftpd-hpa: 2016-05-19T22:19:50

** Affects: tftp-hpa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929006

Title:
  package tftpd-hpa 5.2+20150808-1ubuntu1.16.04.1 failed to
  install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1929006/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

2021-05-19 Thread David Bartley

Nope, still doesn't work (specifically after installing the linux-tools-
common deb).  I'm assuming that just included the cherry-pick mentioned
earlier?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928183

Title:
  turbostat doesn't work with AMD Cezanne APUs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928602] Re: Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout

*** This bug is a duplicate of bug 1883493 ***
https://bugs.launchpad.net/bugs/1883493

** This bug has been marked a duplicate of bug 1883493
   amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928602

Title:
  Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1928602/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] ERROR Waiting for fences timed out!

Looks like this might be related to bug 1883493.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928932] Re: external monitor disabled upon editing file with vim

Thanks for the bug report. Please try logging into 'Ubuntu on Xorg'
(select it on the login screen) and tell us if that has the same bug.

Also, bugs like this are often caused by a faulty connection. It could
come and go at times when the amount or the structure of data over the
cable (DisplayPort??) changes. So please try a different cable if you
can.


** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

** Tags added: multimonitor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928932

Title:
  external monitor disabled upon editing file with vim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1928932/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746551] Re: GPU HANG since package update

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746551

Title:
  GPU HANG since package update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746551/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905724] Re: Compete system freeze with AMD GPU

*** This bug is a duplicate of bug 1883493 ***
https://bugs.launchpad.net/bugs/1883493

** This bug has been marked a duplicate of bug 1883493
   amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905724

Title:
  Compete system freeze with AMD GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] ERROR Waiting for fences timed out!

** Summary changed:

- [amdgpu] Gnome locks up with artifacts on screen
+ [amdgpu] Gnome locks up with artifacts on screen and 
[drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860002] Re: Airport Extreme not given working option

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860002

Title:
  Airport Extreme not given working option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1860002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928923] Re: motherboard microphone does not work

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928923

Title:
  motherboard microphone does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1928923/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917423] Re: Please merge 5.1.7-1 into hirsute

2021-05-19 Thread Bryce Harrington

This bug was fixed in the package autofs - 5.1.7-1
Sponsored for Utkarsh Gupta (utkarsh)

---
autofs (5.1.7-1) unstable; urgency=medium

  * New upstream release.
- autofs: Fix crash in sun_mount() (Closes: #892953).
- Use PKG_CHECK_MODULES to detect the libxml2 library. (Closes: #949055).
  * debian/patches:
+ Drop fix-autofs-schema.patch and make-bind-mounts-propagation-slave-by-
  default.patch. Applied upstream.
+ Trivially rebase patches.
+ Add another typo fix to spelling-error-fixes.patch.
  * debian/autofs.install:
+ Install libautofs.so into bin:pkg autofs (for now).
  * debian/control:
+ Bump Standards-Version: to 4.5.1. No changes needed.
  * debian/autofs.lintian-overrides:
+ Ignore libautofs.so (share lib) for now.
+ Ignore lintian complain about autofs.8 man page.
  * debian/watch:
+ Update format version to 4.

 -- Mike Gabriel   Thu, 04 Feb 2021 13:36:20 +0100

** Changed in: autofs (Ubuntu)
   Status: Confirmed => 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/1917423

Title:
  Please merge 5.1.7-1 into hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1917423/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "Strace log from an older example"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498841/+files/strace_2021-02-17_1613606097_405884989.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "upower_status.txt"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498840/+files/upower_status.txt

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to powerdevil in Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "systemd-inhibit-list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498839/+files/systemd-inhibit-list.txt

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to powerdevil in Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "pstree.log"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498838/+files/pstree.log

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to powerdevil in Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "journalctl-powerdevil.txt"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498837/+files/journalctl-powerdevil.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "gdb.log"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498836/+files/gdb.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928997] Re: powerdevil occasionally stops responding until manually suspended

** Attachment added: "acpi.txt"
   
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+attachment/5498835/+files/acpi.txt

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to powerdevil in Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1928522] Re: seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148

2021-05-19 Thread Thadeu Lima de Souza Cascardo

So, s390x ptrace does allow to set the syscall and return code as long
as it sets the return code at exit time.

However, when using seccomp SECCOMP_RET_TRACE, there is no possibility
to change it at exit time (by doing a ptrace after SECCOMP_RET_TRACE
stops the process). It only happens at entry time. Then, either the
syscall or return value could be set. This is aggravated by the fact
that when seccomp checks for an invalid syscall in order to skip
executing it, it checks for int_code, which cannot be changed by ptrace.
This is probably something that could be reviewed, however.

Without the code change that led to this test regression, the test sets
gpr[2] twice, once for the syscall number, then for the return value.
That return value was being used later on as the return code as it was
an invalid syscall number, which made the test accidentally work.

Now, instead, ENOSYS is returned, and the test fails.

One regression, however, that this patch causes (but not on 4.15), is
that when seccomp returns failure because of a signal, the
signal_restart should not be skipped, but it is. This causes a test
(that we don't currently run) to fail on 5.4, but that is not a
regression and has been like that on 5.4 since forever.

Upstream has changed the entry code for a common code, which should not
have this bug. That needs to be verified, though. Then, a different fix
should be applied to our earlier kernels, like this one:

@@ -905,7 +905,7 @@ asmlinkage long do_syscall_trace_enter(struct pt_regs *regs)
sd.args[5] = regs->gprs[7] & mask;
 
if (__secure_computing() == -1)
-   goto skip;
+   return -1;
}
 #endif /* CONFIG_SECCOMP */

Then, seccomp_bpf can be run just fine on 5.8, for example. 5.4 possibly
needs one small fix for s390x to work, instead of the very large
patchset I thought was needed.

That would be:
commit 4bae85b620dc1f7aa4d2338b923d9d9b394b58c4
Author: Sven Schnelle 
Date:   Mon Mar 9 16:56:53 2020 +0100

selftests/seccomp: s390 shares the syscall and return value register

s390 cannot set syscall number and reture code at the same time,
so set the appropriate flag to indicate it.

Signed-off-by: Sven Schnelle 
Signed-off-by: Vasily Gorbik 

Which is the same that is likely needed for 4.15 to skip these tests.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928522

Title:
  seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test
  failure with linux/4.15.0-144.148

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928997] [NEW] powerdevil occasionally stops responding until manually suspended

Public bug reported:

About twice a month or so, my laptop exhibits the following symptoms:

1. Adjusting the brightness with the usual keys no longer works.

2. Closing the lid no longer suspends

3. Plugging in or unplugging no longer updates the battery charging
icon.

When this happens, I run this command:

systemctl suspend

and after opening the lid and unlocking, everything works again.

Based on these symptoms and workaround, I believe this is a bug in
powerdevil. I first recorded it occurring in version 5.12.7-0ubuntu0.1
in 2019, but it persists in version 5.12.8.

Note that this is not a duplicate of bug #1766683:

https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1766683

Most of the time, closing the lid does suspend my laptop, and I have
lidAction=1 already set (see attached powermanagementprofilesrc).

I would greatly appreciate suggestions for debugging. Currently I have
tried looking at the output of:

systemctl status upower.service

systemctl status org.kde.powerdevil.backlighthelper.service

acpi -V

systemd-inhibit --list

journalctl --boot --lines=all | grep powerdevil

grep powerdevil ~/.xsession-errors

as well as running strace and gdb on the powerdevil process when it is
unresponsive, but I haven't turned up anything useful. (I've attached it
anyway in case anyone can make use of it.)

$ lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

$ apt-cache policy powerdevil
powerdevil:
  Installed: 4:5.12.8-0ubuntu0.1
  Candidate: 4:5.12.8-0ubuntu0.1
  Version table:
 *** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: powerdevil 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: KDE
Date: Wed May 19 20:21:10 2021
InstallationDate: Installed on 2020-02-01 (473 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: powerdevil
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: powerdevil (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "powermanagementprofilesrc"
   
https://bugs.launchpad.net/bugs/1928997/+attachment/5498831/+files/powermanagementprofilesrc

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to powerdevil in Ubuntu.
https://bugs.launchpad.net/bugs/1928997

Title:
  powerdevil occasionally stops responding until manually suspended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerdevil/+bug/1928997/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-19 Thread Tim Ryder

Will the fix be able to be compiled as a module for any kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926165

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924771] Re: hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Bug 1925209] Re: No iwilwifi driver in Linux 5.4.0-1034-raspi

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Bug 1926755] Re: Support Auvidea B101 (TC358743)

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Bug 1927108] Re: Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Bug 1927505] Re: pigpio not working with 5.11

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown

2021-05-19 Thread Jason Ritchie

Also see this on 20.10 on a Dell XPS 15 9550.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280300

Title:
  Desktop contents displayed on resume, before lock screen is shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

2021-05-19 Thread Samuel Ainsworth

As a quick update, I managed to kill all of the spurious pulseaudio
processes that had been lying around as a result of `pulseaudio -k &&
pulseaudio --start` and got the systemd pulseaudio process back on its
feet. Then I confirmed that the audio worked, suspended my system, and
woke it up again and the audio still works!

Therefore I suspect that pulseaudio processes started by the user in
terminal sessions (daemonized) do not survive the suspend/resume cycle
for some reason(?). How the systemd pulseaudio process failed to begin
with remains the larger issue, however.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928996

Title:
  [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  after resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926669] Re: 20.04 LTS upgrade fails

2021-05-19 Thread Dave Cutler

This fixed my problem. I have successfully installed 20.04 LTS. Thanx!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926669

Title:
  20.04 LTS upgrade fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926669/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928996] [NEW] [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

2021-05-19 Thread Samuel A

Public bug reported:

Sound works fine after an initial boot up, but fails after resuming from
a suspend. Going to the "Sound" section in the Settings app, I no longer
see the HDMI device presented as an output option when this occurs.

I suspect this is due to issues with pulseaudio. At least, running
`pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix
the issue. In particular I've found that the pulseaudio systemd service
has failed after resuming from suspend. After scanning through
journalctl, there are a few suspect sections. I've attached the logs in
their entirety, and an abbreviated log with only sections that I found
interesting. I cannot be sure which are at fault, but hopefully it helps
narrow the search.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
 /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 19 16:08:41 2021
InstallationDate: Installed on 2020-05-15 (369 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/home/username/.nix-profile/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
 /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago)
dmi.bios.date: 04/20/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: X58A-UD3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "pulseaudio-logs.zip"
   
https://bugs.launchpad.net/bugs/1928996/+attachment/5498825/+files/pulseaudio-logs.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928996

Title:
  [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  after resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922966] Re: Missing SVG skin icons with libKF5IconThemes5 5.80

2021-05-19 Thread ronso0

instead of fixing the usage of qss properties (cumbersome, a few visual 
regressions) we simply replace relative with absolute paths when reading the 
stylesheets
https://github.com/mixxxdj/mixxx/pull/3877

** Changed in: mixxx
   Importance: Undecided => High

** Changed in: mixxx
 Assignee: (unassigned) => ronso0 (ronso0)

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kiconthemes in Ubuntu.
https://bugs.launchpad.net/bugs/1922966

Title:
  Missing SVG skin icons with libKF5IconThemes5 5.80

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/1922966/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1915354] Re: [FFe] Include ubuntu-advantage-tools 27.0

2021-05-19 Thread Chad Smith

Closing as we missed the window on this FFe for hirsute. We have since
SRU'd this release 27.0 into Xenial Bionic Focal Groovy and Histute.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Triaged => 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/1915354

Title:
  [FFe] Include ubuntu-advantage-tools 27.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1915354/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778983] Re: Resume from suspend on Wayland breaks window positioning

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778983

Title:
  Resume from suspend on Wayland breaks window positioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1778983/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917101] Re: Booting into desktop results in flickering (also when I turn off and next turn on display)

2021-05-19 Thread Chris Guiver

Lubuntu 18.04 is EOL (see https://lubuntu.me/bionic-eol/) as flavors
only provide 3 years of supported life (using packages found in
'universe').

Main Ubuntu Desktop, Server and packages from 'main', which include the
kernel you're asking do have 5 years of support with regards security
fixes.

I had a quick look at your video, I couldn't see the issue you're
talking about, but Lubuntu 18.04 is no longer supported.  The
Ubuntu/Canonical team however will require the apport-collect to be
actioned.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917101

Title:
  Booting into desktop results in flickering (also when I turn off and
  next turn on display)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1917101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924685] Re: No sound output/input available after installing 21.04

2021-05-19 Thread Herczeg Zsolt

~mesouug I've tested my XPS 9700 on the self-compiled ubuntu kernel, and
it works great with a 4-pin plug, even the microphone input of the
headset is fully functional. There may be hardware differences within
the XPS 9700 line as well, but the driver must be fully functional for
at least some of the hardware sold.

Are you confident your headset should be compatible? Not all 4-pin
headphones have the same pin order, which was historically a common
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924685

Title:
  No sound output/input available after installing 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928995] [NEW] package rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3 failed to install/upgrade: el subproceso instalado paquete rtl8821ce-dkms script post-installation devolvió el código de salida de e

2021-05-19 Thread Jhonatan David Cambrano Que

Public bug reported:

This is translated from a translator, but I make known that I tried to
install a package installer and since I have all the updates enabled, I
wanted to update the Wi-Fi drives, which it indicates in the title, but
I first installed the Wi-Fi driver downloaded from a page, so I mark an
error, I would recommend doing something that checks if another driver
is installed that by the way the error that appeared gave a message
saying something like this, and uninstall the previous driver and
install the one offered, but fortune I think that if it was updated and
so far I do not see problems.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May 19 16:06:58 2021
ErrorMessage: el subproceso instalado paquete rtl8821ce-dkms script 
post-installation devolvió el código de salida de error 10
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: rtl8821ce
Title: package rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3 failed to 
install/upgrade: el subproceso instalado paquete rtl8821ce-dkms script 
post-installation devolvió el código de salida de error 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: rtl8821ce (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928995

Title:
  package rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3 failed to
  install/upgrade: el subproceso instalado paquete rtl8821ce-dkms script
  post-installation devolvió el código de salida de error 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1928995/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928993] [NEW] Executing 'grub-install/dev/sda' failed ssd Ubuntu 21

2021-05-19 Thread Natalia

Public bug reported:

when installing Ubuntu Hirsuite Hippo alongside Win10 the mentioned
message was shown

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Wed May 19 19:14:10 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928993

Title:
  Executing 'grub-install/dev/sda' failed ssd Ubuntu 21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928993/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928818] Re: Co-installation of mysql and mariadb can cause 'Link has been severed' failure on mysql.service when purging

2021-05-19 Thread Bryce Harrington

** Summary changed:

- package mysql-server-8.0 8.0.25-0ubuntu0.20.10.1 failed to install/upgrade: 
installed mysql-server-8.0 package pre-removal script subprocess returned error 
exit status 1
+ Co-installation of mysql and mariadb can cause 'Link has been severed'  
failure on mysql.service when purging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928818

Title:
  Co-installation of mysql and mariadb can cause 'Link has been severed'
  failure on mysql.service when purging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928818/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928648] Re: expiring trust anchor compatibility issue

** Description changed:

  [Impact]
  
   * gnutls28 fails to talk to letsencrypt website past September 2021,
  despite trusting the letsencrypt root certificate.
  
  [Test Plan]
  
   * Import staging cert equivalent to ISRG Root X1
  https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem
  
   * Import expired staging cert equivalen tto DST Root CA X3
  https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem
  
   * Test connectivity to the expired-root-ca test website
  https://expired-root-ca-test.germancoding.com
  
  setup:
  
  apt install wget gnutls-bin
  wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem
  wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem
  cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem
  
  test case:
  gnutls-cli --x509cafile=ca.pem expired-root-ca-test.germancoding.com
  
  bad result:
- - Status: The certificate is NOT trusted. The certificate chain uses expired 
certificate. 
+ - Status: The certificate is NOT trusted. The certificate chain uses expired 
certificate.
  *** PKI verification of server certificate failed...
  *** Fatal error: Error in the certificate.
  *** handshake has failed: Error in the certificate.
  
  good result:
- - Status: The certificate is trusted. 
+ - Status: The certificate is trusted.
  - Description: 
(TLS1.3-X.509)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
  - Session ID: 
A8:2B:AF:85:54:64:3A:79:81:99:16:D4:6D:9A:FC:30:F1:EC:49:A4:09:A9:0C:31:37:38:C2:0E:73:C7:C9:04
  - Options: OCSP status request,
  - Handshake was completed
  
  Connection should be successful and trusted with correctly working
  gnutls client that can manage to ignore expired CA, and build a valid
  trust path using non-expired CA in the chain.
  
  [Where problems could occur]
  
   * Changes as to how the trust paths are built in TLS connection may
  result in introducing bugs (failure to connect to valid sites) and/or
  security vulnerabilities (connecting to invalid sites successfully).
  
  [Other Info]
  
   * Background info
   * The current chain from letsencrypt is expiring, they are adding a new 
chain, but also keeping the expiring one. This will result in connectivity 
issues when using old gnutls/openssl against websites using the default 
letsencrypt configuration after September 2021.
  
  
https://community.letsencrypt.org/t/openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143816
  
https://community.letsencrypt.org/t/questions-re-openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143817
  
  Currently gnutls28 in bionic and earlier will not establish a
  connection, if any parts of the trust chain have expired, even though
  alternative non-expired chains are available.
  
  This has been fixed in GnuTLS 3.6.14, but probably should be backported
  to bionic and earlier if it was not already been done so.
  
  https://gitlab.com/gnutls/gnutls/-/issues/1008
  
  https://gitlab.com/gnutls/gnutls/-/merge_requests/1271
+ 
+ Openssl bug report for this issue is
+ https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989

** Tags removed: letsencrypt
** Tags added: letsencryptexpiry

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928648

Title:
  expiring trust anchor compatibility issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1928648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928989] Re: expiring trust anchor compatibility issue

** Information type changed from Public to Public Security

** Tags removed: letsencrypt
** Tags added: letsencryptexpiry

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928989

Title:
  expiring trust anchor compatibility issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928990] [NEW] Not searchable

2021-05-19 Thread Klitos Kyriacou

Public bug reported:

After installing the package openjdk-16-doc, when I open the index.html
in Chrome, the search box is not accepting any input. This is in
contrast to earlier versions, such as openjdk-14-doc and openjdk-11-doc,
where the search box worked as it should. Also, the Oracle Java 16
downloaded documentation also has a search box that works.

** Affects: openjdk-16 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928990

Title:
  Not searchable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-16/+bug/1928990/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909814] Re: Keyboard not working

2021-05-19 Thread Did VDT

Content of var/log/Xorg.0.log seems to consider webcam as keyboard if I 
understand it correctly.
Any idea ?


< grep -i keyboard /var/log/Xorg.0.log
[14.661] (II) Initializing extension XKEYBOARD
[14.851] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[14.856] (II) event1  - Power Button: is tagged by udev as: Keyboard
[14.856] (II) event1  - Power Button: device is a keyboard
[14.857] (II) XINPUT: Adding extended input device "Power Button" (type: 
KEYBOARD, id 6)
[14.865] (II) event1  - Power Button: is tagged by udev as: Keyboard
[14.865] (II) event1  - Power Button: device is a keyboard
[14.865] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[14.866] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[14.866] (II) event0  - Sleep Button: device is a keyboard
[14.866] (II) XINPUT: Adding extended input device "Sleep Button" (type: 
KEYBOARD, id 7)
[14.867] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[14.867] (II) event0  - Sleep Button: device is a keyboard
[14.867] (II) config/udev: Adding input device HID Keyboard Device 
(/dev/input/event3)
[14.867] (**) HID Keyboard Device: Applying InputClass "libinput keyboard 
catchall"
[14.867] (II) Using input driver 'libinput' for 'HID Keyboard Device'
[14.868] (**) HID Keyboard Device: always reports core events
[14.868] (II) event3  - HID Keyboard Device: is tagged by udev as: Keyboard
[14.868] (II) event3  - HID Keyboard Device: device is a keyboard
[14.868] (II) event3  - HID Keyboard Device: device removed
[14.868] (II) XINPUT: Adding extended input device "HID Keyboard Device" 
(type: KEYBOARD, id 8)
[14.869] (II) event3  - HID Keyboard Device: is tagged by udev as: Keyboard
[14.869] (II) event3  - HID Keyboard Device: device is a keyboard
[14.870] (II) config/udev: Adding input device HID Keyboard Device Consumer 
Control (/dev/input/event4)
[14.870] (**) HID Keyboard Device Consumer Control: Applying InputClass 
"libinput keyboard catchall"
[14.870] (II) Using input driver 'libinput' for 'HID Keyboard Device 
Consumer Control'
[14.870] (**) HID Keyboard Device Consumer Control: always reports core 
events
[14.871] (II) event4  - HID Keyboard Device Consumer Control: is tagged by 
udev as: Keyboard
[14.871] (II) event4  - HID Keyboard Device Consumer Control: device is a 
keyboard
[14.871] (II) event4  - HID Keyboard Device Consumer Control: device removed
[14.871] (II) libinput: HID Keyboard Device Consumer Control: needs a 
virtual subdevice
[14.871] (II) XINPUT: Adding extended input device "HID Keyboard Device 
Consumer Control" (type: MOUSE, id 9)
[14.871] (**) HID Keyboard Device Consumer Control: (accel) selected scheme 
none/0
[14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration 
factor: 2.000
[14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration 
threshold: 4
[14.872] (II) event4  - HID Keyboard Device Consumer Control: is tagged by 
udev as: Keyboard
[14.872] (II) event4  - HID Keyboard Device Consumer Control: device is a 
keyboard
[14.872] (II) config/udev: Adding input device HID Keyboard Device System 
Control (/dev/input/event5)
[14.872] (**) HID Keyboard Device System Control: Applying InputClass 
"libinput keyboard catchall"
[14.872] (II) Using input driver 'libinput' for 'HID Keyboard Device System 
Control'
[14.873] (**) HID Keyboard Device System Control: always reports core events
[14.873] (II) event5  - HID Keyboard Device System Control: is tagged by 
udev as: Keyboard
[14.873] (II) event5  - HID Keyboard Device System Control: device is a 
keyboard
[14.873] (II) event5  - HID Keyboard Device System Control: device removed
[14.873] (II) XINPUT: Adding extended input device "HID Keyboard Device 
System Control" (type: KEYBOARD, id 10)
[14.874] (II) event5  - HID Keyboard Device System Control: is tagged by 
udev as: Keyboard
[14.874] (II) event5  - HID Keyboard Device System Control: device is a 
keyboard
[14.875] (**) USB2.0 HD UVC WebCam: USB2.0 HD: Applying InputClass 
"libinput keyboard catchall"
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev 
as: Keyboard
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a 
keyboard
[14.876] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam: 
USB2.0 HD" (type: KEYBOARD, id 11)
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev 
as: Keyboard
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a 
keyboard
[14.879] (**) HID Keyboard Device Consumer Control: Applying InputClass 
"libinput keyboard catchall"
[14.879] (II) Using input driver 'libinput' for 'HID Keyboard Device 
Consumer Control'
[14.879] (**) HID Keyboard Device Consumer Control: always reports core 
events
[

[Bug 1928964] Re: update 20.04.01 to 20.04.02, that version its slow

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. You can also find help posting your problem
in the support forum of your local Ubuntu's community
http://loco.ubuntu.com/ or asking at http://askubuntu.com. For help on
reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

** Changed in: ubuntu
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+question/697150

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928964

Title:
  update 20.04.01 to 20.04.02, that version its slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1928964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928984] Re: keyboard layout return back to US during the install process

** Package changed: ubuntu => ubiquity (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928984

Title:
  keyboard layout return back to US during the install process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928984/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928989] [NEW] expiring trust anchor compatibility issue

Public bug reported:

[Impact]

 * openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.

[Test Plan]

 * Import staging cert equivalent to ISRG Root X1
https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem

 * Import expired staging cert equivalen tto DST Root CA X3
https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem

 * Test connectivity to the expired-root-ca test website
https://expired-root-ca-test.germancoding.com

setup:

apt install openssl
wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem
wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem
cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem

test case:
openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername 
expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem

bad result:
connection failed

good result:
connection successful

Connection should be successful and trusted with correctly working
openssl s_client that can manage to ignore expired CA, and build a valid
trust path using non-expired CA in the chain.

[Where problems could occur]

 * Changes as to how the trust paths are built in TLS connection may
result in introducing bugs (failure to connect to valid sites) and/or
security vulnerabilities (connecting to invalid sites successfully).

[Other Info]

 * Background info
 * The current chain from letsencrypt is expiring, they are adding a new chain, 
but also keeping the expiring one. This will result in connectivity issues when 
using old gnutls/openssl against websites using the default letsencrypt 
configuration after September 2021.

https://community.letsencrypt.org/t/openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143816
https://community.letsencrypt.org/t/questions-re-openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143817

Currently openssl in xenial and earlier will not establish a connection,
if any parts of the trust chain have expired, even though alternative
non-expired chains are available.

This has been fixed in OpenSSL 1.1.0+ by setting
X509_V_FLAG_TRUSTED_FIRST by default see
https://github.com/openssl/openssl/commit/0daccd4dc1f1ac62181738a91714f35472e50f3c

gnutls bug for this is
https://bugs.launchpad.net/ubuntu/bionic/+source/gnutls28/+bug/1928648

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: openssl (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: openssl (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: letsencrypt

** Also affects: openssl (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: openssl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: openssl (Ubuntu)
   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/1928989

Title:
  expiring trust anchor compatibility issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928648] Re: expiring trust anchor compatibility issue

** Tags added: letsencrypt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928648

Title:
  expiring trust anchor compatibility issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1928648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1903288] Comment bridged from LTC Bugzilla

2021-05-19 Thread bugproxy

--- Comment From naynj...@ibm.com 2021-05-19 16:51 EDT---
(In reply to comment #28)
> @Nayna Jain @Daniel
>
> Hm but we have CONFIG_LOAD_PPC_KEYS=y already which I would expect to be
> the only thing that loads keys into .platform keyring which was enabled as
> part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866909
> LTC-184073 . Which keys are present in firmware / get loaded into .platform
> because of that? I would have expected canonical keys to be loaded by that
> into the .platform keyring, or is that not the case?

Hi,

Yes you are right that CONFIG_LOAD_PPC_KEYS enables loading of keys into
.platform keyring from firmware at runtime. However, as Daniel has
mentioned in his comment dated 2020-12-17 , that the .platform keyring
is currently not loaded in pseries firmware as it is static keys based
solution and at the moment doesn't have any mechanism to expose trusted
keys (this will change with the full key management solution).

>
> Can you please share contents of "powerpc:db"? Ideally it should contain
> Canonical's two OPAL signing certs.
>

> If canonical keys are not in "powerpc:db", does it make sense to then add
> the two Canonical keys to the .builtin_trusted_keys_keyring, and then link
> the whole keyring into .ima keyring?
>
> I will attach the two Canonical OPAL signing keys here, and the ESL for them.

The final conclusion was to add a config option for PLATFORM KEYRING
similar to SYSTEM_TRUSTED_KEYS mechanism. It would allow loading
additional keys compiled into the kernel to be loaded only to .platform
keyring.  This would be in addition to the existing support for loading
firmware keys at runtime on the platfom keyring. It aligns with xnox
comment dated "2012-03-18".

At some point we will probably close the loop hole that allows self
signed certificates loaded onto the builtin keyring to be loaded onto
the IMA keyring.   It's better to define a mechanism for loading
additional certs on the platform keyring that would work today and will
continue to work in the future.

I am supposed to start looking at the patches. I would be starting to
look at them in June timeframe.

Thanks & Regards,
- Nayna

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903288

Title:
  Power guest secure boot with static keys: kernel portion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928986] Re: Some tray icons are generic

2021-05-19 Thread Carlos Eduardo Moreira dos Santos

In gnome-shell, they render fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928986

Title:
  Some tray icons are generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1928986/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928182] Re: Unable to deploy postgresql-k8s charm from charmhub

2021-05-19 Thread John A Meinel

That particular error is coming from here:
https://github.com/juju/juju/blob/19d6a75eea61f5021a9fa0ee8e37fe7f6e3c9d53/charmhub/download.go#L201

Given what it is downloading from, I believe it is coming from:
https://github.com/juju/juju/blob/19d6a75eea61f5021a9fa0ee8e37fe7f6e3c9d53/charmhub/download.go#L101

Essentially we got the charm URL from Charmhub, but when we went to download 
it, we got a status code that wasn't 200 OK, and wasn't 404 Not Found.
(I feel like we should at least be logging more information if not including it 
in the error)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928182

Title:
  Unable to deploy postgresql-k8s charm from charmhub

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1928182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917101] Re: Booting into desktop results in flickering (also when I turn off and next turn on display)

2021-05-19 Thread Piotr

** Description changed:

Dear Launchpad Community,

I have problem with my display on all version of Ubuntu system. It
doesn't matter what version I will install. I checked this on Ubuntu
18.04.5, Ubuntu 20.04, Ubuntu 20.04.1, Lubuntu 18.04.5. My screen is
- flashing for one second when I boot my system or if I will logout from
- the session. This same problem when I will log in to the session. My
- screen is flashing (white image) for one second. What is a problem? I
- think that this can be driver problem or with kernel itself. I have this
- same problem on other computer. On both computers I have Radeon graphic
- card.
+ flashing for one second when I boot my system or if I will turn off and
+ next turn on my display. My screen is flashing (white image) for one
+ second. What is a problem? I think that this can be driver problem or
+ with kernel itself. I have this same problem on other computer. On both
+ computers I have Radeon graphic card.

Some outputs from terminal:

lshw -C video

*-display
-description: VGA compatible controller
-product: RS880M [Mobility Radeon HD 4225/4250]
-vendor: Advanced Micro Devices, Inc. [AMD/ATI]
+ description: VGA compatible controller
+ product: RS880M [Mobility Radeon HD 4225/4250]
+ vendor: Advanced Micro Devices, Inc. [AMD/ATI]
configuration: driver=radeon latency=0

uname -ar
5.4.0-66-generic #74~18.04.2-Ubuntu x86_64 GNU/Linux

lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04

Package:

linux-hwe-5.4-headers-5.4.0-66/bionic-updates,bionic-updates,bionic-security,bionic-security,now
5.4.0-66.74~18.04.2

-
- I hope that you can help and fix it. I don't have this issue on Windows
family system.
+ I hope that you can help and fix it. I don't have this issue on Windows
+ family system.

I founded on askubuntu some solution. I can add to the GRUB nomodeset
option and this help me for the one of the machines. Flickers is gone
but system works slower and with lower resolution. On my machine with
RS880M this option is not possible because this cause problems with my
hardware and I can see artefacts so I will not try use this nomodeset
option anymore.

-
- I found Bug #1838644 and I have this same problem like more users in the
past. I am on 5.4.0-66 kernel like you can see above.
+ I found Bug #1838644 and I have this same problem like more users in the
+ past. I am on 5.4.0-66 kernel like you can see above.

Normally when I will boot my system or logout from the session I
shouldn't notice flickering of my display but it is happen.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917101

Title:
Booting into desktop results in flickering (also when I turn off and
next turn on display)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1917101/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928392] Re: add newer Ubuntu releases to lintian for older Ubuntu releases

I tested lintian in by using debuild with 2vcard after changing the
release name in 2vcard to impish. With the version of lintian in the
release pocket lintian raised and error about the release name and with
the version of lintian from -proposed no error was raised, so I'm
setting this to verification done.

** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928392

Title:
  add newer Ubuntu releases to lintian for older Ubuntu releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1928392/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928986] [NEW] Some tray icons are generic

2021-05-19 Thread Carlos Eduardo Moreira dos Santos

Public bug reported:

Icons for Slack and Microsoft Teams are generic (engine icon).

Versions:
Ubuntu 20.04
lxqt-panel 0.14.1-ubuntu3
slack-desktop/jessie,now 4.16.0 amd64 [installed]
teams/stable,now 1.4.00.7556 amd64 [installed]

** Affects: lxqt-panel (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Slack and Microsoft Teams icons"
   
https://bugs.launchpad.net/bugs/1928986/+attachment/5498810/+files/tray_icons.png

** Description changed:

- Icons for slack (installed from apt) and Microsoft Teams (installed with
- snap) are generic (engine icon).
+ Icons for Slack and Microsoft Teams are generic (engine icon).
  
+ Versions:
  Ubuntu 20.04
  lxqt-panel 0.14.1-ubuntu3
+ slack-desktop/jessie,now 4.16.0 amd64 [installed]
+ teams/stable,now 1.4.00.7556 amd64 [installed]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928986

Title:
  Some tray icons are generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1928986/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928182] Re: Unable to deploy postgresql-k8s charm from charmhub

2021-05-19 Thread Daniel Manrique

The download problem happened at 2021-05-12 10:01:49, charmhub didn't
have any outage at that time.

COuld we perhaps get more information about under which circumstances
Juju would say "unable to locate archive"?

ERROR storing charm "postgresql-k8s": cannot retrieve
"https://api.charmhub.io/api/v1/charms/download/y2vuZHGLElMmdfcL4q1zJayL9utaheIa_2.charm":
unable to locate archive

I'd like to know what HTTP response code / payload was received by Juju
to result in this message, so we can track down why charmhub responded
with that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928182

Title:
  Unable to deploy postgresql-k8s charm from charmhub

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1928182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable

2021-05-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928973

Title:
  Please merge lvm2 2.03.11-2.1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1928973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928964] Re: update 20.04.01 to 20.04.02, that version its slow

2021-05-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1928964/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928964

Title:
  update 20.04.01 to 20.04.02, that version its slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1928964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928984] Re: keyboard layout return back to US during the install process

2021-05-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1928984/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928984

Title:
  keyboard layout return back to US during the install process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1928984/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs

This bug was fixed in the package livecd-rootfs - 2.664.21

---
livecd-rootfs (2.664.21) focal; urgency=medium

  [ Thomas Bechtold ]
  * Add a new ubuntu-oci project that contains the customizations currently
performed downstream for the official Ubuntu images on dockerhub.
(LP: #1926732)

 -- Michael Hudson-Doyle   Tue, 11 May 2021
11:38:16 +1200

** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Status: Fix Committed => 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/1926732

Title:
  Add ubuntu-oci project for building OCI-ready tarballs with livecd-
  rootfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs

This bug was fixed in the package livecd-rootfs - 2.525.53

---
livecd-rootfs (2.525.53) bionic; urgency=medium

  [ Thomas Bechtold ]
  * Add a new ubuntu-oci project that contains the customizations currently
performed downstream for the official Ubuntu images on dockerhub.
(LP: #1926732)

 -- Michael Hudson-Doyle   Tue, 11 May 2021
11:39:46 +1200

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926732

Title:
  Add ubuntu-oci project for building OCI-ready tarballs with livecd-
  rootfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

2021-05-19 Thread Henrik Juul Hansen

@Koba
I tried kernel 5.13.0-051300rc2-generic. After boot d3cold_allowed was "1", 
ASPM L1 enabled for nvme (and bluetooth did not work). After suspend/resume 
ASPM L1 was disabled for nvme. Power consumption higher. dmesg is attached.

** Attachment added: "dmesg-koba-5.13.0.rc2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5498809/+files/dmesg-koba-5.13.0.rc2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912057

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928963] Re: Intel driver is not installed

2021-05-19 Thread Daniel Letzeisen

Virtualbox emulates a video adapter. What you are trying to do (or
expecting) is "VGA passthrough", which Virtualbox does not support.

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

** Package changed: xorg (Ubuntu) => virtualbox (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928963

Title:
  Intel driver is not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1928963/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928984] [NEW] keyboard layout return back to US during the install process

2021-05-19 Thread Jean-Do Veuve

Public bug reported:

When installing the 21.04 version on an Oracle VirtualBox, you can
choose the keyboard setting following your country.

What is expected: the chosen settings will remain during the whole
install process.

What happened: At the moment you are entering the login_name and the
login_password, the keyboard revert discreetly back to US layout and
will once again revert to chosen country setting after the reboot.

Resulting problem: you will type the login/password with a different
keyboard layout that the one you had when you entered it during the
install process.

IMPORTANT: This is a regression as the exact same problem was already
known with 20.04 and was solved. See :
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928984

Title:
  keyboard layout return back to US during the install process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1928984/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925972] Re: Upgrade from 18.04 to 20.04 not calculatable if python-bson-ext is installed