[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Kai-Heng Feng]

8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings") is part of a series with 18 patches, so it's
safer to only bakcport it for 5.10 kernels.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

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

[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Peter Klein]

I have performed the installation several times.  It only happens with
either a BT 4 or a BT 5 dongle.  Bluetooth 4 is CRS.  Bluetooth 5 is
mediatek.

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

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

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

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Baq Domalaq]

@Coiby Xu (coiby) thanks a lot for your work! You really saved a lot of
laptops on linux.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

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

Re: [Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Wes Newell]

On 12/19/20 5:09 PM, Sean Young wrote:
> Hello, the author of those commits here. It's not clear to me how those
> commits broke things. Either something else changed, or there is
> something subtle going on.
>
> The following bits of information would be very useful.
>
> 1. Is the issue intermittent or consistent, i.e. does booting with a new 
> kernel always cause some keys to fail and an older kernel all the keys always 
> work fine?
> 2. What keymap are you loading?
> 3. Are you using a streamzap device?
> 3. How are you loading the keymap; i.e. how is ir-keytable run, and with what 
> command line.
> 4. Once the system is booted, it would be useful to know what the output of 
> the evtest command line tool is (after you select the device)
>
> Ideally it would also be useful to know what happens if you revert those
> commits.
>
> Thank you

1. It's consistent. older kernels always work. never ones never work.

2. I'm using a custom keymap. I'll attach my keymap file and config 
file. Don't know what the original reporter uses.

3. No. I'm using a JP1 remote with my own custom nec protocol.

4. You lost me on this one. Don't know what evtest you mean. Nor do I 
select the device. It just works after boot.

I'm not a kernel guy and don't know how to revert the commits. Here's my 
ir-keytable output on kernel 5.8.7.

wes@mythfe0:~$ ir-keytable
Found /sys/class/rc/rc3/ with:
     Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)
     Driver: mceusb
     Default keymap: rc-rc6-mce
     Input device: /dev/input/event19
     LIRC device: /dev/lirc3
     Attached BPF protocols: Permission denied
     Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp imon rc-mm
     Enabled kernel protocols: lirc nec rc-6

Newer kernels ir-keytable output does not enable the nec protocol. I 
have removed them from my system. Currently running 5.8.7. It was the 
last one that worked. All after that don't work. The last ubuntu kernel 
that worked was 5.4.0-48. None after that work either.

I have no clue if those commits have anything to do with this. It was someone 
else's comment in the bug report.
If I'm barking up the wrong tree I'm sorry to have bothered you.

-- 
https://github.com/wesnewell/Functionality
http://wesnewell.ddns.net


** Attachment added: "rc_maps.cfg"
   
https://bugs.launchpad.net/bugs/1901089/+attachment/5445176/+files/rc_maps.cfg

** Attachment added: "myremotes.toml"
   
https://bugs.launchpad.net/bugs/1901089/+attachment/5445177/+files/myremotes.toml

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

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

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

[Bug 1899289] Re: Computer freezes and the fan will start going really hard

[Launchpad Bug Tracker]

[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/1899289

Title:
  Computer freezes and the fan will start going really hard

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

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

[Bug 1900484] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: mysql-8.0 (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/1900484

Title:
  package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

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

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

[Bug 1900637] Re: lubuntu groovy install failed; message is larger than screen allows for

[Launchpad Bug Tracker]

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

** Changed in: calamares (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/1900637

Title:
  lubuntu groovy install failed; message is larger than screen allows
  for

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

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

[Bug 1900648] Re: Fresh installation crashes

[Launchpad Bug Tracker]

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

** Changed in: ubiquity (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/1900648

Title:
  Fresh installation crashes

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

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

[Bug 1900673] Re: package texlive-plain-generic 2019.202000218-1 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo.

[Launchpad Bug Tracker]

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

** Changed in: texlive-extra (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/1900673

Title:
  package texlive-plain-generic 2019.202000218-1 failed to
  install/upgrade: el paquete está en un estado muy malo e inconsistente
  - debe reinstalarlo  antes de intentar desinstalarlo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1900673/+subscriptions

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

[Bug 1908809] Re: [wayland-session] applications crash on system load

[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/1908809/+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/1908809

Title:
  [wayland-session] applications crash on system load

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

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

[Bug 1908807] Re: installation crashed at the end with cmd "update-grub -c failed "

[Ubuntu Foundations Team Bug Bot]

** 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/1908807

Title:
  installation crashed at the end with cmd "update-grub -c failed "

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

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

[Bug 1908809] [NEW] [wayland-session] applications crash on system load

[damianator...@gmail.com]

Public bug reported:

When on wayland applications crash when heavily loaded.

This happens for me with music players importing a big library or
opening a big folder/text file during that time I am trying to resize
it.

The easiest way to reproduce is:
1) Open a terminal.
2) start nautilus/gedit/totem
3) press ctrl - z
4) try to resize the application for a few seconds
5) write 'fg'
6) application crashes

** 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/1908809

Title:
  [wayland-session] applications crash on system load

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

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

[Bug 1908807] [NEW] installation crashed at the end with cmd "update-grub -c failed "

[Danushka]

Public bug reported:

I was installing Xubuntu 20.10 on a Acer Laptop with Nvidia-Intel Hybrid
Graphics and this crash occured

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
Date: Sun Dec 20 08:16:42 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
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.8.0-25-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy ubiquity-20.10.13 xubuntu

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

Title:
  installation crashed at the end with cmd "update-grub -c failed "

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

Cracking and popping is worse after suspend

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] PulseList.txt

[nacenteno]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1908804/+attachment/5445168/+files/PulseList.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] ProcCpuinfoMinimal.txt

[nacenteno]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1908804/+attachment/5445167/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] CurrentDmesg.txt

[nacenteno]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1908804/+attachment/5445166/+files/CurrentDmesg.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

apport information

** Tags added: apport-collected focal

** Description changed:

  Speakers sound fine
  Issue is only with headphones, more distortion on front left.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  arturo 1956 F pulseaudio
+  /dev/snd/pcmC0D0c:   arturo 1956 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   arturo 1956 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-01 (263 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Package: alsa-driver (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
+ Tags:  focal
+ Uname: Linux 5.4.0-58-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-10-01 (79 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 07/06/2018
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.04
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: 84BE
+ dmi.board.vendor: HP
+ dmi.board.version: 02.12
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd07/06/2018:svnHP:pnHPPavilionLaptop15-cs0xxx:pvrType1ProductConfigId:rvnHP:rn84BE:rvr02.12:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP Pavilion
+ dmi.product.name: HP Pavilion Laptop 15-cs0xxx
+ dmi.product.sku: 5GP03UA#ABA
+ dmi.product.version: Type1ProductConfigId
+ dmi.sys.vendor: HP

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1908804/+attachment/5445165/+files/AlsaInfo.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[Yuri Astrakhan]

I have been using rc6 kernel 5.10, plus I git cloned the ath11k-firmware
repo, and linking /lib/firmware/ath11k/QCA6390/hw2.0 -> /lib/ath11k-
firmware/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/

uname -a:   Linux minty 5.10.0-051000rc6-generic #202011291930 SMP Mon
Nov 30 00:36:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I have had pretty good results with the wifi, except that after sleep
resume, i always have to do   sudo modprobe -r -f ath11k_pci && sudo
modprobe ath11k_pci   -- which takes 2 to 3 minutes (last run - 2:34).
Otherwise wifi is not working at all.

Additionally, on occasion I have observed full system lock ups that
require hard reboot (long press on power button). I do not know if this
is related.


[  +0.06] usb 1-3.1: USB disconnect, device number 6
[  +0.219827] usb 1-3.2: USB disconnect, device number 5
[  +0.150986] pcieport :00:1c.4: PME: Spurious native interrupt!
[  +1.140384] ACPI Error: Thread 2487681024 cannot release Mutex [ECMX] 
acquired by thread 1375698944 (20200925/exmutex-378)

[  +0.19] No Local Variables are initialized for Method [_Q66]

[  +0.03] No Arguments are initialized for method [_Q66]

[  +0.07] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to 
previous error (AE_AML_NOT_OWNER) (20200925/psparse-529)
[  +0.079962] usb 6-1: USB disconnect, device number 2
[  +1.614174] wlp4s0: deauthenticating from 58:ef:68:0f:2a:3a by local choice 
(Reason: 3=DEAUTH_LEAVING)
[  +0.140469] PM: suspend entry (s2idle)
[  +0.009589] Filesystems sync: 0.009 seconds
[  +0.002797] Freezing user space processes ... (elapsed 0.060 seconds) done.
[  +0.060942] OOM killer disabled.
[  +0.01] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  +0.001721] printk: Suspending console(s) (use no_console_suspend to debug)
[Dec19 20:21] ACPI: EC: interrupt blocked
[Dec19 20:34] ACPI: EC: interrupt unblocked
[  +1.34] xhci_hcd :a5:00.0: BAR 0: error updating (0x8af0 != 
0x00)
[  +0.189078] nvme nvme0: 16/0/0 default/read/poll queues
[  +0.304973] OOM killer enabled.
[  +0.01] Restarting tasks ... 
[  +0.003223] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 
:00:02.0 (ops i915_hdcp_component_ops [i915])
[  +0.004528] done.
[  +0.063481] PM: suspend exit
[  +3.018443] ath11k_pci :04:00.0: wmi command 16387 timeout
[  +0.27] ath11k_pci :04:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[  +0.06] ath11k_pci :04:00.0: failed to enable dynamic bw: -11
[  +3.071691] ath11k_pci :04:00.0: wmi command 16387 timeout
[  +0.03] ath11k_pci :04:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[  +0.03] ath11k_pci :04:00.0: failed to enable PMF QOS: (-11
[  +3.071750] ath11k_pci :04:00.0: wmi command 16387 timeout
[  +0.05] ath11k_pci :04:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[  +0.05] ath11k_pci :04:00.0: failed to enable PMF QOS: (-11
[ +13.566946] ath11k_pci :04:00.0: wmi command 16387 timeout
[  +0.07] ath11k_pci :04:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[  +0.06] ath11k_pci :04:00.0: failed to enable PMF QOS: (-11
[  +0.144494] failed to send QMI message
[  +0.07] ath11k_pci :04:00.0: qmi failed to send mode request, mode: 
4, err = -5
[  +0.01] ath11k_pci :04:00.0: qmi failed to send wlan mode off
[Dec19 20:37] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[  +0.000191] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  +0.017076] ath11k_pci :04:00.0: WARNING: ath11k PCI support is 
experimental!
[  +0.000153] ath11k_pci :04:00.0: BAR 0: assigned [mem 
0xd210-0xd21f 64bit]
[  +0.070957] mhi :04:00.0: Requested to power ON
[  +0.000207] mhi :04:00.0: Power on setup success
[  +0.414557] ath11k_pci :04:00.0: Respond mem req failed, result: 1, err: 0
[  +0.06] ath11k_pci :04:00.0: qmi failed to respond fw mem req:-22
[  +0.010392] ath11k_pci :04:00.0: chip_id 0x0 chip_family 0xb board_id 
0xff soc_id 0x
[  +0.05] ath11k_pci :04:00.0: fw_version 0x101c06cc fw_build_timestamp 
2020-06-24 19:50 fw_build_id 
[  +0.204570] ath11k_pci :04:00.0 wlp4s0: renamed from wlan0
[Dec19 20:38] wlp4s0: authenticate with 58:ef:68:0f:2a:3a
[  +0.149049] wlp4s0: send auth to 58:ef:68:0f:2a:3a (try 1/3)
[  +0.005101] wlp4s0: authenticated
[  +0.15] ath11k_pci :04:00.0 wlp4s0: disabling HT/VHT/HE due to 
WEP/TKIP use
[  +0.007783] wlp4s0: associate with 58:ef:68:0f:2a:3a (try 1/3)
[  +0.019239] wlp4s0: RX AssocResp from 58:ef:68:0f:2a:3a (capab=0x11 status=0 
aid=3)
[  +0.015076] wlp4s0: associated
[  +0.007314] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Dec19 20:39] perf: interrupt took too long (4034 > 4022), lowering 
kernel.perf_event_max_sample_rate to 49500

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

[Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

[Dan Streetman]

Unfortunately (or maybe fortunately?) I'm no longer able to reproduce
this when deploying Ubuntu 20.04 instances in azure.

@deej are you able to reproduce this with newly deployed 20.04
instances?

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1902960/+subscriptions

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

** Attachment added: "lsmod_output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1908804/+attachment/5445164/+files/lsmod_output.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

** Attachment added: "lspci_output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1908804/+attachment/5445163/+files/lspci_output.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

** Attachment added: "lspci_output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1908804/+attachment/5445162/+files/lspci_output.txt

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[nacenteno]

Using Ubuntu 20.04.1 LTS
On HP-Pavilion-Laptop-15-cs0xxx
Intel® Core™ i7-8550U CPU @ 1.80GHz × 8 
Mesa Intel® UHD Graphics 620 (KBL GT2)

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] Re: Ubuntu – Cracking and popping sound from headphones

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1908804

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908804] [NEW] Ubuntu – Cracking and popping sound from headphones

[nacenteno]

Public bug reported:

Speakers sound fine
Issue is only with headphones, more distortion on front left.

** Affects: alsa-driver (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/1908804

Title:
  Ubuntu – Cracking and popping sound from headphones

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

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

[Bug 1908004] Re: Touchpad bug

[André Santoro]

I tried adding it and rebooting the laptop, still hasn't worked.

Maybe I did something incorrectly, the grub is looking like this right now
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nocrs"

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

Title:
  Touchpad bug

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

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

[Bug 1905054] Re: Firefox 83 Breaks WebGL

[Bug Watch Updater]

** Changed in: firefox
   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/1905054

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working

[Joel Jakubovic]

** Description changed:

  A fresh install of 20.04 from the live USB doesn't see internal keyboard
  or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private
  investigation to no avail
  (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop-
  internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert
  this as a bug. I'll restate the relevant info here, but see the link for
  a more chronological account. And I guess, for what it's worth, I would
  also assert that this is reproducible by installing 20.04 on my specific
  laptop model.
  
  So, I boot up the laptop. I'm presented with GRUB boot menu. At this
  point the keyboard works, and if I choose advanced options and boot into
  a root shell I can type commands and do things that way as a last
  resort. However, all the problems seem to begin right from the start of
  the graphical session, even the login screen. This, in accordance with
  the instruction of
  https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is
  why I've filed this as a bug in gdm3. As I couldn't run the graphical
  bug program in Ubuntu, I ran the CLI in the root shell and attached the
  apport file here. I've tried to follow the relevant steps, but this is
  my first bug report so apologies if something is wrong.
  
  I first noticed this problem a few weeks after upgrading 18.04 to 20.04.
  Yes, for the first few weeks of using 20.04, there were no problems. And
  then, one day, I booted up and the keyboard and touchpad spontaneously
  stopped working. This was mysterious because to my memory I hadn't done
  any major upgrade or change to any part of the system the previous day.
  
  When the system is asleep / suspended, pressing a key or the touchpad
  easily wakes it up -- after which, they refuse to work again.
  
  The brightness key combos (Fn+←/→) and one that turns off the screen
  (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work.
  
  I see all expected key output when I run `sudo libinput debug-events
  --device /dev/input/event4 --show-keycodes` and type keys.
  
  When I plug in an external USB keyboard and mouse, they work correctly
  while the internal keyboard and touchpad remain the same.
  
  Outside of those specific situations, absolutely no internal keyboard
  input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone
  ordinary typing -- has any effect, and same with the touchpad.
  
+ When I haven't had an external keyboard available I've used the on-
+ screen keyboard to painstakingly run terminal commands by clicking each
+ letter. However, sometimes the on-screen keyboard also stops sending
+ keystrokes. The only concrete situation I can report is what I saw after
+ resuming the system from sleep by opening the lid: at the login prompt
+ on the lock screen, the onscreen keyboard came up, but didn't do
+ anything when keys were clicked, forcing me to reboot.
+ 
  I had the following message in my `journalctl -b` logs:
  ```
  The XKEYBOARD keymap compiler (xkbcomp) reports:
  Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning:  
Unsupported maximum keycode 569, clipping.
  Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: >   X11 
cannot support keycodes above 255.
  Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error:   
Could not resolve keysym Invalid
  Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are 
not fatal to the X server
  ```
  This looks like it should have something to do with the keyboard issue. If it 
doesn't, then what is its significance?
  
  When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112
  in the boot menu, everything was fine again; keyboard and touchpad
  working. I also found everything working fine on the install USB demo.
  Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard
  and touchpad did not work.
  
  How can it be OK in the Live USB Demo but not the OS it installs? And
  why did switching down to that old kernel version fix my problem if the
  problems only happened in the GUI and not the root console? What on
  earth is the connection between the kernel and GNOME's input handling
  ... on top of an apparently working libinput??
  
  Ideally I'd want to know the different stages in the lifecycle of a
  keystroke (post-libinput) and to find out at which stage the key event
  is getting discarded. I literally went digging through the source code
  of various GNOME packages and programs, xkb tools, etc. I got as far as
  vaguely learning about Mutter or Clutter or something before deciding I
  had better things to do with my evenings. I am lost and I need someone
  who knows more about this.
  
  One person on Ask Ubuntu gave some pessimistic sympathy, describing the
  issue as "just a thing we have to live with" on this particular laptop
  model. This is unacceptable, and I am able and willing to spend more
  time

[Bug 1905054]

[Pat Suwalski]

(In reply to Jeff Gilbert [:jgilbert] from comment #19)
> Honestly at this point I'm tending towards #2.
> Websites had the chance to handle this well and they have bungled it, so I 
> think we should disable failIfMajorPerformanceCaveat as it stands today.

Are you suggesting PIXI doesn't handle this properly?

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

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1905054]

[Jgilbert]

Honestly at this point I'm tending towards #2.
Websites had the chance to handle this well and they have bungled it, so I 
think we should disable failIfMajorPerformanceCaveat as it stands today.

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

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1905054]

[Jgilbert]

After bug 1680595, it should be more clear to (power) users what they
can do to mitigate this.

Functionality here is, I think, working as intended now. Unfortunately
the specified behavior causes certain websites (which arguably may have
made poor choices) work worse for our users, whereas before things were
maybe slower than they could have been, but otherwise functional.

With that in mind, since we're now following
failIfMajorPerformanceCaveat spec properly, it's causing breakage. This
bug is tracking the user pain-point. In order to solve the user pain-
point, we might ditch failIfMajorPerformanceCaveat as accidentally-
user=hostile for the time being.

Two choices:
1. Call these bad websites, and try outreach/education
2. Re-evaluate the failIfMajorPerformanceCaveat mechanism entirely

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

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1905054]

[Pat Suwalski]

Although Firefox 84b2 from official binaries worked fine, Firefox 84.0
from official binaries (firefox-84.0.tar.bz2) does not.

Setting ```gfx.webrender.all``` as suggested above *does* work.

This appears to be a capability detection issue.

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

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1905054]

[Ddascalescu]

I don't know if Google Maps changed something, but after setting
`gfx.webrender.all` to true and restarting Firefox 83, I do get 3D
satellite maps.

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

Title:
  Firefox 83 Breaks WebGL

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

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

[Bug 1908799] Re: could not do a dist upgrade from eoan

[Chris Guiver]

FYI:  Well done on #2 (solving it yourself)

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

Title:
  could not do a dist upgrade from eoan

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

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

[Bug 1908799] Re: could not do a dist upgrade from eoan

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

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.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

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

Title:
  could not do a dist upgrade from eoan

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

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

[Bug 1908802] Re: backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1: backport-iwlwifi kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1: backport-iwlwifi
  kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1908802/+subscriptions

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

[Bug 1908802] [NEW] backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1: backport-iwlwifi kernel module failed to build

[Noriko Kono]

Public bug reported:

Sorry, I have no idea about this.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1
ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
DKMSKernelVersion: 5.4.0-58-generic
Date: Sat Dec 19 11:25:32 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DuplicateSignature: 
dkms:backport-iwlwifi-dkms:7841-ubuntu2~ubuntu18.04.1:/var/lib/dkms/backport-iwlwifi/7841/build/backport-include/linux/skbuff.h:208:12:
 error: ‘struct sk_buff’ has no member named ‘xmit_more’
InstallationDate: Installed on 2020-12-17 (2 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
PackageArchitecture: all
PackageVersion: 7841-ubuntu2~ubuntu18.04.1
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.12ubuntu0.2
SourcePackage: backport-iwlwifi-dkms
Title: backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1: backport-iwlwifi 
kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: backport-iwlwifi-dkms (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  backport-iwlwifi-dkms 7841-ubuntu2~ubuntu18.04.1: backport-iwlwifi
  kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1908802/+subscriptions

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

[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Sean Young]

Hello, the author of those commits here. It's not clear to me how those
commits broke things. Either something else changed, or there is
something subtle going on.

The following bits of information would be very useful.

1. Is the issue intermittent or consistent, i.e. does booting with a new kernel 
always cause some keys to fail and an older kernel all the keys always work 
fine?
2. What keymap are you loading?
3. Are you using a streamzap device?
3. How are you loading the keymap; i.e. how is ir-keytable run, and with what 
command line.
4. Once the system is booted, it would be useful to know what the output of the 
evtest command line tool is (after you select the device)

Ideally it would also be useful to know what happens if you revert those
commits.

Thank you

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

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

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

[Bug 1908554] Re: Standby problems solved only in specific kernel version

[Silicomancer]

Tried 5.10.1 and it works fine.

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

Title:
  Standby problems solved only in specific kernel version

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

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

[Bug 1908783] Re: fail to install to a newly bought computer

[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 :-

Dec 19 12:46:28 ubuntu kernel: [  511.004247] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Dec 19 12:46:28 ubuntu kernel: [  511.004250] SQUASHFS error: 
squashfs_read_data failed to read block 0x1e6256ff

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 note you had a successful SCAN of the media before install
"CasperMD5CheckResult: pass"
however the errors show trouble reading that media during install operation, 
which means issues with media, or if you were using a VM insufficient RAM was 
provided to the VM for reliable operation..

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

Thank you for helping make Ubuntu better.

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

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

Title:
  fail to install to a newly bought computer

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

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

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Mike Boruta]

Wow, this is great news! Thank you again for your hard work, and to all
who helped out :).

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

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

[Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2

[Andreas Herrmann]

I've installed mainline 5.10 and retried but the outcome was the same.
I've attached the corresponding dmesg log including the same kmsg
messages as before.

** Attachment added: "dmesg log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908139/+attachment/5445155/+files/kernel5.10.dmesg

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

Title:
  ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2

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

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

[Bug 1908080] Re: SRU micro to 2.0.1-1ubuntu0.1

[Raman Sarda]

** Description changed:

  [Impact]
+ Micro currently has the following issues in focal:
  
  1.
   * Creates a log.txt file in whichever directory it is opened.
   * Crashes if open in directories which don't have write permissions for
     the user. e.g: running
     micro /opt/testfile.txt to even read that file crashes it.
  
  2.
   * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
  1.
   * open any file using micro from terminal. A log.txt will be created in
     that folder.
  
   * Micro will crash giving an error saying:
     "error opening file: open log.txt: permission denied"
  
     If the user calling micro doesn't have write access to the folder of
     said file.
  
  2.
   * micro --version gives the output as:
     Version: 0.0.0-unknown
  
  [Where problems could occur]
+ The updated version 2.0.6-2 present in groovy fixes these issues. But
  
   * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
-    equal or above 1.4.8. Which means the package
-    golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
+    equal or above 1.4.8. Some important classes and methods which are
+updated are required. Which means the package
+    golang-github-zyedidia-tcell also needs to be updated in focal. The
     relevant SRU bug for the same can be found here:
     
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
- * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
+ * micro 2.0.6-2 might also FTBFS in focal as the
    debhelper-compat required version is 13 and focal has only 12. So it
    will need to be modified accordingly. Thus, the version of micro in
-   focal will be 2.0.1-1ubuntu0.1 after the SRU.
+   focal will be 2.0.1-1ubuntu0.1 after the SRU. but the contents will be
+   same as 2.0.6-2 from groocy.
  
  [Other Info]
  
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953400

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

Title:
  SRU micro to 2.0.1-1ubuntu0.1

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

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

[Bug 1908801] [NEW] Acer laptop internal keyboard & touchpad not working

[Joel Jakubovic]

Public bug reported:

A fresh install of 20.04 from the live USB doesn't see internal keyboard
or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private
investigation to no avail
(https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop-
internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert
this as a bug. I'll restate the relevant info here, but see the link for
a more chronological account. And I guess, for what it's worth, I would
also assert that this is reproducible by installing 20.04 on my specific
laptop model.

So, I boot up the laptop. I'm presented with GRUB boot menu. At this
point the keyboard works, and if I choose advanced options and boot into
a root shell I can type commands and do things that way as a last
resort. However, all the problems seem to begin right from the start of
the graphical session, even the login screen. This, in accordance with
the instruction of
https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is
why I've filed this as a bug in gdm3. As I couldn't run the graphical
bug program in Ubuntu, I ran the CLI in the root shell and attached the
apport file here. I've tried to follow the relevant steps, but this is
my first bug report so apologies if something is wrong.

I first noticed this problem a few weeks after upgrading 18.04 to 20.04.
Yes, for the first few weeks of using 20.04, there were no problems. And
then, one day, I booted up and the keyboard and touchpad spontaneously
stopped working. This was mysterious because to my memory I hadn't done
any major upgrade or change to any part of the system the previous day.

When the system is asleep / suspended, pressing a key or the touchpad
easily wakes it up -- after which, they refuse to work again.

The brightness key combos (Fn+←/→) and one that turns off the screen
(Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work.

I see all expected key output when I run `sudo libinput debug-events
--device /dev/input/event4 --show-keycodes` and type keys.

When I plug in an external USB keyboard and mouse, they work correctly
while the internal keyboard and touchpad remain the same.

Outside of those specific situations, absolutely no internal keyboard
input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone
ordinary typing -- has any effect, and same with the touchpad.

I had the following message in my `journalctl -b` logs:
```
The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning:  
Unsupported maximum keycode 569, clipping.
Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: >   X11 
cannot support keycodes above 255.
Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error:   Could 
not resolve keysym Invalid
Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are 
not fatal to the X server
```
This looks like it should have something to do with the keyboard issue. If it 
doesn't, then what is its significance?

When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112
in the boot menu, everything was fine again; keyboard and touchpad
working. I also found everything working fine on the install USB demo.
Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard
and touchpad did not work.

How can it be OK in the Live USB Demo but not the OS it installs? And
why did switching down to that old kernel version fix my problem if the
problems only happened in the GUI and not the root console? What on
earth is the connection between the kernel and GNOME's input handling
... on top of an apparently working libinput??

Ideally I'd want to know the different stages in the lifecycle of a
keystroke (post-libinput) and to find out at which stage the key event
is getting discarded. I literally went digging through the source code
of various GNOME packages and programs, xkb tools, etc. I got as far as
vaguely learning about Mutter or Clutter or something before deciding I
had better things to do with my evenings. I am lost and I need someone
who knows more about this.

One person on Ask Ubuntu gave some pessimistic sympathy, describing the
issue as "just a thing we have to live with" on this particular laptop
model. This is unacceptable, and I am able and willing to spend more
time looking into this myself, if I can get just some pointers.

Thank you for your consideration.

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


** Tags: gnome keyboard laptop touchpad

** Attachment added: "Results from running apport-cli -f -p gdm3"
   
https://bugs.launchpad.net/bugs/1908801/+attachment/5445154/+files/BUGREPORT.apport

** Summary changed:

- internal keyboard touchpad not working
+ Acer laptop internal keyboard & touchpad not working

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

Title:
  Ac

[Bug 1908141] Re: SRU to 1.4.4-1ubuntu0.1. Required for updating Micro.

[Raman Sarda]

** Description changed:

  [Impact]
  
   * Version 1.4.8 is required for updating the package named micro as the
     current version in focal (micro 2.0.1-1) has a couple of very important
-    bugs that are fixed in micro 2.0.6-2 which is present in groovy.
+    bugs that are fixed in micro 2.0.6-2 which is already present in
+groovy.
+ 
+  * Some classes and methods are changed in between 1.4.4 and 1.4.8 which
+are necessary for newer micro.
  
  [Test Case]
  
   * There are no bugs against golang-github-zyedidia-tcell currently. This
     SRU is more like a prerequisite for SRU of micro.
  
  [Where problems could occur]
  
   * One point where the package can fail to build from source in focal is
     due to the tighter dependency of debhelper = 13 in 1.4.8-2. Which can
     be easily handled with a small patch to change the debhelper-compat
     requirement to 12 only for focal builds. Thus, the version of this
-    package in focal will be 1.4.4-1ubuntu0.1 after SRU.
+    package in focal will be 1.4.4-1ubuntu0.1 after SRU but the contents
+will be simillar to 1.4.8-2 from groovy.
  
  * Other places of concern could be the reverse depends. But the package
     has no reverse dependencies.
  
  [Other Info]
  
   * Updated version 1.4.8-2 is already present in groovy and thoroughly
     tested. The only change needed to build it in focal is to modify the
     debhelper-compat requirement back to 12.

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

Title:
  SRU to 1.4.4-1ubuntu0.1. Required for updating Micro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1908080] Re: SRU micro to 2.0.1-1ubuntu0.1

[Raman Sarda]

** Summary changed:

- SRU micro to 2.0.6-3
+ SRU micro to 2.0.1-1ubuntu0.1

** Description changed:

  [Impact]
  
  1.
   * Creates a log.txt file in whichever directory it is opened.
   * Crashes if open in directories which don't have write permissions for
     the user. e.g: running
     micro /opt/testfile.txt to even read that file crashes it.
  
  2.
   * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
  1.
   * open any file using micro from terminal. A log.txt will be created in
     that folder.
  
   * Micro will crash giving an error saying:
     "error opening file: open log.txt: permission denied"
  
     If the user calling micro doesn't have write access to the folder of
     said file.
  
  2.
   * micro --version gives the output as:
     Version: 0.0.0-unknown
  
  [Where problems could occur]
  
   * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
     equal or above 1.4.8. Which means the package
     golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
     relevant SRU bug for the same can be found here:
     
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
  * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
    debhelper-compat required version is 13 and focal has only 12. So it
    will need to be modified accordingly. Thus, the version of micro in
-   focal will be 2.0.6-3 after the SRU.
+   focal will be 2.0.1-1ubuntu0.1 after the SRU.
  
  [Other Info]
  
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953400

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

Title:
  SRU micro to 2.0.1-1ubuntu0.1

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

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

[Bug 1908141] Re: SRU to 1.4.4-1ubuntu0.1. Required for updating Micro.

[Raman Sarda]

** Summary changed:

- SRU to 1.4.8-3. Required for updating Micro.
+ SRU to 1.4.4-1ubuntu0.1. Required for updating Micro.

** Description changed:

  [Impact]
  
   * Version 1.4.8 is required for updating the package named micro as the
-current version in focal (micro 2.0.1-1) has a couple of very important
-bugs that are fixed in micro 2.0.6-2 which is present in groovy.
+    current version in focal (micro 2.0.1-1) has a couple of very important
+    bugs that are fixed in micro 2.0.6-2 which is present in groovy.
  
  [Test Case]
  
   * There are no bugs against golang-github-zyedidia-tcell currently. This
     SRU is more like a prerequisite for SRU of micro.
  
  [Where problems could occur]
  
   * One point where the package can fail to build from source in focal is
-due to the tighter dependency of debhelper = 13 in 1.4.8-2. Which can
-be easily handled with a small patch to change the debhelper-compat
-requirement to 12 only for focal builds. Thus, the version of this
-package in focal will be 1.4.8-3 after SRU.
-  
+    due to the tighter dependency of debhelper = 13 in 1.4.8-2. Which can
+    be easily handled with a small patch to change the debhelper-compat
+    requirement to 12 only for focal builds. Thus, the version of this
+    package in focal will be 1.4.4-1ubuntu0.1 after SRU.
+ 
  * Other places of concern could be the reverse depends. But the package
     has no reverse dependencies.
  
  [Other Info]
  
   * Updated version 1.4.8-2 is already present in groovy and thoroughly
-tested. The only change needed to build it in focal is to modify the
-debhelper-compat requirement back to 12.
+    tested. The only change needed to build it in focal is to modify the
+    debhelper-compat requirement back to 12.

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

Title:
  SRU to 1.4.4-1ubuntu0.1. Required for updating Micro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1908080] Re: SRU Bug for #1870939 [WIP]

[Raman Sarda]

** Description changed:

  [Impact]
  
-  * Creates a log.txt file in whichever directory it is opened. 
-  * Crashes if open in directories which don't have write permissions for the 
user. e.g: running
-micro /opt/testfile.txt to even read that file crashes it.
+ 1.
+  * Creates a log.txt file in whichever directory it is opened.
+  * Crashes if open in directories which don't have write permissions for
+the user. e.g: running
+    micro /opt/testfile.txt to even read that file crashes it.
+ 
+ 2.
+  * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
-  * open any file using micro from terminal. A log.txt will be created in
- that folder.
+ 1.
+  * open any file using micro from terminal. A log.txt will be created in
+that folder.
  
-  * Micro will crash giving an error saying: "error opening file: open 
log.txt: permission denied" 
-if the user calling micro doesn't have write access to the folder of said 
file. 
+  * Micro will crash giving an error saying:
+"error opening file: open log.txt: permission denied"
+
+If the user calling micro doesn't have write access to the folder of
+said file.
+ 
+ 2.
+  * micro --version gives the output as:
+Version: 0.0.0-unknown
  
  [Where problems could occur][WIP]
  
-  * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+  * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
+equal or above 1.4.8. Which means the package
+golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
+relevant SRU bug for the same can be found here:
+
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
- 
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
- 
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+ * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
+   debhelper-compat required version is 13 and focal has only 12. So it
+   will need to be modified accordingly. Thus, the version of micro in
+   focal will be 2.0.6-3 after the SRU.
  
  [Other Info]
-  
-  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
-  *
+ 
+  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
+  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953400

** Summary changed:

- SRU Bug for #1870939 [WIP]
+ SRU micro to 2.0.6-3

** Changed in: micro (Ubuntu)
   Status: New => Fix Released

** Changed in: micro (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

  [Impact]
  
  1.
   * Creates a log.txt file in whichever directory it is opened.
   * Crashes if open in directories which don't have write permissions for
-the user. e.g: running
+    the user. e.g: running
     micro /opt/testfile.txt to even read that file crashes it.
  
  2.
-  * Micro thinks it's version is 0.0.0-unknown.
+  * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
  1.
   * open any file using micro from terminal. A log.txt will be created in
-that folder.
+    that folder.
  
   * Micro will crash giving an error saying:
-"error opening file: open log.txt: permission denied"
-
-If the user calling micro doesn't have write access to the folder of
-said file.
+    "error opening file: open log.txt: permission denied"
+ 
+    If the user calling micro doesn't have write access to the folder of
+    said file.
  
  2.
-  * micro --version gives the output as:
-Version: 0.0.0-unknown
+  * micro --version gives the output as:
+    Version: 0.0.0-unknown
  
- [Where problems could occur][WIP]
+ [Where problems could occur]
  
   * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
-equal or above 1.4.8. Which means the package
-golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
-relevant SRU bug for the same can be found here:
-
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
+    equal or above 1.4.8. Which means the package
+    golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
+    relevant SRU bug for the same can be found here:
+    
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
  * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
-   debhelper-compat required version is 13 and focal has only 12. So it
-   will need to be modified accordingly. Thus, the version of micro in
-   focal will be 2.0.6-3 af

[Bug 1908141] Re: SRU to 1.4.8-3. Required for updating Micro.

[Raman Sarda]

** Changed in: golang-github-zyedidia-tcell (Ubuntu)
Milestone: focal-updates => None

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

Title:
  SRU to 1.4.8-3. Required for updating Micro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1908141] Re: SRU to 1.4.8-2. Required for updating Micro.

[Raman Sarda]

** Description changed:

  [Impact]
  
-  * Version 1.4.8 is required for updating the package named micro to
-v2.0.6-2 as the current version in focal (2.0.1-1) has a couple of very
-important bugs that are fixed in 2.0.6-2 which is present in groovy.
+  * Version 1.4.8 is required for updating the package named micro as the
+current version in focal (micro 2.0.1-1) has a couple of very important
+bugs that are fixed in micro 2.0.6-2 which is present in groovy.
  
  [Test Case]
  
   * There are no bugs against golang-github-zyedidia-tcell currently. This
-STU is more like a prerequisite for SRU of micro.
+    SRU is more like a prerequisite for SRU of micro.
  
  [Where problems could occur]
  
-  * One point where the package can fail to build from source is due to the
-tighter dependency of debhelper = 13 in 1.4.8-2. Which can be easily
-handled with a small patch to change the debhelper-compat requirement
-to 12 only for focal builds.
-  * Other places of concern could be the reverse depends. But the package
-has no reverse dependencies.
+  * One point where the package can fail to build from source in focal is
+due to the tighter dependency of debhelper = 13 in 1.4.8-2. Which can
+be easily handled with a small patch to change the debhelper-compat
+requirement to 12 only for focal builds. Thus, the version of this
+package in focal will be 1.4.8-3 after SRU.
+  
+ * Other places of concern could be the reverse depends. But the package
+    has no reverse dependencies.
  
  [Other Info]
  
-  * Updated version is already present in groovy and thoroughly tested.
+  * Updated version 1.4.8-2 is already present in groovy and thoroughly
+tested. The only change needed to build it in focal is to modify the
+debhelper-compat requirement back to 12.

** Summary changed:

- SRU to 1.4.8-2. Required for updating Micro.
+ SRU to 1.4.8-3. Required for updating Micro.

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

Title:
  SRU to 1.4.8-3. Required for updating Micro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1908800] [NEW] Wireless card crashes daily on my XPS 13 9380

[Ben Bromley]

Public bug reported:

Hello all,

Daily, or multiple times per day, the wireless card on my XPS 13 9380
crashes, forcing me to shutdown my computer and then boot it back up. I
am on Ubuntu 20.04, and here is the results from dmesg -T right after
such a crash happens:

[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 
170ee3ba-1809-4276-9b34-9d4e37da0937)
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:143a
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 
tracing 1 dfs 0 testmode 0
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A 
crc32 4ac0889b
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to get memcpy hi 
address for firmware address 4: -16
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read firmware 
dump area: -16
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: Copy Engine register dump:
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [00]: 0x00034400  11  11   
3   3
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [01]: 0x00034800  23  23 
164 165
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [02]: 0x00034c00  31  30  
93  94
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [03]: 0x00035000  20  20  
22  20
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [04]: 0x00035400 4711 4707 
114  50
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  
64   0
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [06]: 0x00035c00   7   7  
12  12
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [07]: 0x00036000   1   0   
1   0
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read 
hi_board_data address: -28
[Sat Dec 19 15:08:59 2020] ieee80211 phy0: Hardware restart was requested
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: unsupported HTC service id: 
1536
[Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: device successfully 
recovered

lsb_release  -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.187.6
  Candidate: 1.187.6

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.6
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bsbrom 3384 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 19 15:21:02 2020
Dependencies:
 
InstallationDate: Installed on 2020-09-05 (105 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. XPS 13 9380
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wxgq6h@/vmlinuz-5.4.0-58-generic 
root=ZFS=rpool/ROOT/ubuntu_wxgq6h ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-58-generic N/A
 linux-backports-modules-5.4.0-58-generic  N/A
 linux-firmware1.187.6
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.0
dmi.board.name: 0KTW76
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd07/06/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Wireless card crashes daily on my XPS 13 9380

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

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

[Bug 1908796] Re: 20_linux_xen is missing the same treatments of 10_linux_zfs creating unbootable Ubuntu 20.04 ZFS systems with Xen

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-zfs-fix-LINUX_ROOT_DEVICE-when-grub-probe-
fails.patch" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** 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/1908796

Title:
  20_linux_xen is missing the same treatments of 10_linux_zfs creating
  unbootable Ubuntu 20.04 ZFS systems with Xen

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

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

[Bug 1899410] Re: VPN Stopped working after installing Ubuntu patch

[Gunnar Hjalmarsson]

Hmm.. While I wrote that comment, Tiziana provided valuable input.

** Package changed: ubuntu => network-manager-openvpn (Ubuntu)

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

Title:
  VPN Stopped working after installing Ubuntu patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1899410/+subscriptions

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

[Bug 1899410] Re: VPN Stopped working after installing Ubuntu patch

[Gunnar Hjalmarsson]

Please note that ubuntu-docs is a package for the Desktop user
documentation, and thus unrelated to the problem. Changed this report to
a generic bug for now, since it lacks information about which package is
the culprit.

I see that you also posted at .

** Package changed: ubuntu-docs (Ubuntu) => ubuntu

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

Title:
  VPN Stopped working after installing Ubuntu patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1899410/+subscriptions

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

[Bug 1899410] Re: VPN Stopped working after installing Ubuntu patch

[Tiziana]

It is a problem of conflicting packages I think.
I got it working by uninstalling network-manager-openvpn, 
network-manager-openvpn-gnome, and openvpn-systemd-resolved. This also gets rid 
of OpenVPN and Surfshark itself, so the two packages need to be reinstalled 
afterwards.

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

Title:
  VPN Stopped working after installing Ubuntu patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1899410/+subscriptions

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

[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)

[Olivier V]

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=210453
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth : No device found (rtl8822cu)

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

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

[Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

[Olivier V]

Hi,

This bug affects me too on rtl8822_cu.

Bisected here :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515

And reported here : https://bugzilla.kernel.org/show_bug.cgi?id=210453

** Bug watch added: Linux Kernel Bug Tracker #210453
   https://bugzilla.kernel.org/show_bug.cgi?id=210453

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

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

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug 1695343 )

[Eric Desrochers]

** Tags added: sts-sponsor-slashd

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

Title:
  lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug
  1695343 )

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

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

[Bug 1908141] Re: SRU to 1.4.8-2. Required for updating Micro. [WIP}

[Raman Sarda]

** Changed in: golang-github-zyedidia-tcell (Ubuntu)
Milestone: None => focal-updates

** Changed in: golang-github-zyedidia-tcell (Ubuntu)
   Status: New => Fix Released

** Changed in: golang-github-zyedidia-tcell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: golang-github-zyedidia-tcell (Ubuntu)
 Assignee: (unassigned) => Raman Sarda (theloudspeaker)

** Summary changed:

- SRU to 1.4.8-2. Required for updating Micro. [WIP}
+ SRU to 1.4.8-2. Required for updating Micro.

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

Title:
  SRU to 1.4.8-2. Required for updating Micro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1899410] Re: VPN Stopped working after installing Ubuntu patch

[Tiziana]

Same here, Ubuntu 20.04.
It worked previously, now it gives me the same message as above.
Not sure when this happened exactly, but it should be around the same time (end 
of September).

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

Title:
  VPN Stopped working after installing Ubuntu patch

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

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

[Bug 1908141] Re: SRU to 1.4.8-2. Required for updating Micro. [WIP}

[Raman Sarda]

** Description changed:

  [Impact]
  
-  * An explanation of the effects of the bug on users and
- 
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+  * Version 1.4.8 is required for updating the package named micro to
+v2.0.6-2 as the current version in focal (2.0.1-1) has a couple of very
+important bugs that are fixed in 2.0.6-2 which is present in groovy.
  
  [Test Case]
  
-  * detailed instructions how to reproduce the bug
- 
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+  * There are no bugs against golang-github-zyedidia-tcell currently. This
+STU is more like a prerequisite for SRU of micro.
  
  [Where problems could occur]
  
-  * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
- 
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
- 
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * One point where the package can fail to build from source is due to the
+tighter dependency of debhelper = 13 in 1.4.8-2. Which can be easily
+handled with a small patch to change the debhelper-compat requirement
+to 12 only for focal builds.
+  * Other places of concern could be the reverse depends. But the package
+has no reverse dependencies.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Updated version is already present in groovy and thoroughly tested.

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

Title:
  SRU to 1.4.8-2. Required for updating Micro. [WIP}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141/+subscriptions

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

[Bug 1908799] Re: could not do a dist upgrade from eoan

[Carl Leitner]

Fixed after removal:
 sudo apt-get remove postgresql-server-dev-11 
 sudo apt-get remove postgresql-server-dev-12

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

Title:
  could not do a dist upgrade from eoan

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

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

[Bug 1908799] [NEW] could not do a dist upgrade from eoan

[Carl Leitner]

Public bug reported:

Output of release upgrade:
sudo do-release-upgrade 
[sudo] password for litlfred: 
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

Get:1 Upgrade tool signature [1,554 B]  
  
Get:2 Upgrade tool [1,340 kB]   
  
Fetched 1,342 kB in 0s (0 B/s)  
  
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
extracting 'focal.tar.gz'

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Ign http://repos.azulsystems.com/ubuntu stable InRelease
  
Hit http://dl.google.com/linux/chrome/deb stable InRelease  
  
Hit http://repos.azulsystems.com/ubuntu stable Release  
  
Ign http://linux.dropbox.com/ubuntu disco InRelease 
  
Get:1 http://linux.dropbox.com/ubuntu disco Release [6,598 B]   
  
Hit https://downloads.plex.tv/repo/deb public InRelease 
  
Hit https://repos.azul.com/zulu/deb stable InRelease
  
Fetched 6,598 B in 0s (0 B/s)   
  
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Checking for installed snaps

Calculating snap size requirements

Updating repository information

Third party sources disabled

Some third party entries in your sources.list were disabled. You can 
re-enable them after the upgrade with the 'software-properties' tool 
or your package manager. 

To continue please press [ENTER]

Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]   
  
Hit http://archive.ubuntu.com/ubuntu focal InRelease
  
Get:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] 
  
Get:3 http://security.ubuntu.com/ubuntu focal-security/main amd64 DEP-11 
Metadata [24.3 kB]   
Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 DEP-11 Metadata 
[263 kB]  
Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main DEP-11 64x64 Icons 
[82.1 kB]
Fetched 593 kB in 0s (0 B/s)
  

Checking package manager
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Calculating the changes

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

This was likely caused by: 
* Unofficial software packages not provided by Ubuntu 
Please use the tool 'ppa-purge' from the ppa-purge 
package to remove software from a Launchpad PPA and 
try the upgrade again. 

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 


Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree  
Reading state information... Done

=

Tail of /var/log/dist-upgrade/apt.log is:
Broken dnsutils:amd64 Depends on liblwres161:amd64 < 
1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU > (= 
1:9.11.5.P4+dfsg-5.1ubuntu2.2)
  Considering liblwres161:amd64 0 as a solution to dnsutils:amd64 10002
  Added liblwres161:amd64 to the remove list
  Fixing dnsutils:amd64 via keep of libbind9-161:amd64
  MarkKeep libbind9-161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0
  Fixing dnsutils:amd64 via keep of libisccfg163:amd64
  MarkKeep libisccfg163:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii umU > FU=0
  Fixing dnsutils:amd64 via keep of liblwres161:amd64
  MarkKeep liblwres161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0
 Try to Re-Instate (2) liblwres161:amd64
  MarkKeep liblwres161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0
 Try to Re-Instate (2) libbind9-161:amd64
  MarkKeep libbind9-161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii ugU Ib > FU=0
 Try to Re-Instate (3) libisccfg163:amd64
  MarkKeep libisccfg163:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 
1:9.11.16+dfsg-3~ubuntu1 @ii umU > FU=0
Investigating 

[Bug 1899410] Re: VPN Stopped working after installing Ubuntu patch

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-docs (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/1899410

Title:
  VPN Stopped working after installing Ubuntu patch

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

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

[Bug 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all

[Deck Weiss]

Sound suddenly works again without doing anything.

I disabled unattended-upgrade since last time, so maybe it was not
related up updates in the first place.

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

Title:
  [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound
  at all

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

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

[Bug 1908757] Re: virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to build

[Gianfranco Costamagna]

There is already a pending fix and an open bug for this. Will be fixed
with the 6.1.16 version soon

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

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

Title:
  virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel
  module failed to build

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

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

[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Wes Newell]

I've emailed the person that commited them. With luck.

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

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

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

[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Wes Newell]

I have no idea how to do that.

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

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

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

[Bug 1908577] Re: QEMU crashed after last update

[Dan Streetman]

it appears to have crashed:
[   47.344271] qemu-system-x86[4696]: segfault at 28 ip 55d785304bcc sp 
7ffc93183670 error 6 in qemu-system-x86_64[55d7852e2000+4d5000]
[   47.344281] Code: 00 48 8d 3d 2d db 56 00 48 8b 08 31 c0 e8 3c bc ff ff 4c 
8b 2d 85 29 89 00 e9 42 ff ff ff 48 8d 3d a5 4b 61 00 e8 24 bb ff ff  40 28 
01 00 00 00 e9 73 fc ff ff 48 8d 35 71 50 4b 00 48 8d 3d

can you attach the coredump?

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

Title:
  QEMU crashed after last update

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

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

[Bug 1901195] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (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/1901195

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

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

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

[Bug 1901195] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1

[Emmanuel]

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

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

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

[Bug 1908796] Re: 20_linux_xen is missing the same treatments of 10_linux_zfs creating unbootable Ubuntu 20.04 ZFS systems with Xen

[Doug Goldstein]

** Patch added: "0001-zfs-fix-LINUX_ROOT_DEVICE-when-grub-probe-fails.patch"
   
https://bugs.launchpad.net/grub/+bug/1908796/+attachment/5445128/+files/0001-zfs-fix-LINUX_ROOT_DEVICE-when-grub-probe-fails.patch

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

Title:
  20_linux_xen is missing the same treatments of 10_linux_zfs creating
  unbootable Ubuntu 20.04 ZFS systems with Xen

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

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

[Bug 1907991] Re: Touchpad not working dynabook PORTEGE-X30L-G-10J

[Kai-Heng Feng]

Can you please test this kernel without any kernel parameter?
https://people.canonical.com/~khfeng/lp1907991/

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

Title:
  Touchpad not working dynabook PORTEGE-X30L-G-10J

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

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

[Bug 1908796] [NEW] 20_linux_xen is missing the same treatments of 10_linux_zfs creating unbootable Ubuntu 20.04 ZFS systems with Xen

[Doug Goldstein]

Public bug reported:

If you install Xen on your Ubuntu 20.04 system with ZFS, the system
becomes unbootable because the adjustments made by Canonical to GRUB by
providing 10_linux_zfs to override 10_linux aren't done to 20_linux_xen
as well. I'm not asking for the same level of zys integration with a Xen
system, I'm just asking for a bootable system. The following patch was
posted to the GRUB mailing list and it would be good to backport it so
that people don't experience systems that don't boot.

https://lists.gnu.org/archive/html/grub-devel/2020-12/msg00239.html

Other people have experienced this as well based on
https://askubuntu.com/questions/1271948/ubuntu-20-04-with-zfs-root-
fails-to-boot-after-installing-xen

** Affects: grub
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: GNU Savannah Bug Tracker #59614
   http://savannah.gnu.org/bugs/?59614

** Also affects: grub via
   http://savannah.gnu.org/bugs/?59614
   Importance: Unknown
   Status: Unknown

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

Title:
  20_linux_xen is missing the same treatments of 10_linux_zfs creating
  unbootable Ubuntu 20.04 ZFS systems with Xen

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

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

[Bug 1908796] Re: 20_linux_xen is missing the same treatments of 10_linux_zfs creating unbootable Ubuntu 20.04 ZFS systems with Xen

[Doug Goldstein]

Relates to bug #1632694, but the issue that user reported is fixed
because of the changes Canonical made to include 10_linux_zfs.

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

Title:
  20_linux_xen is missing the same treatments of 10_linux_zfs creating
  unbootable Ubuntu 20.04 ZFS systems with Xen

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

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

[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions

[Gunnar Hjalmarsson]

On 2020-12-19 18:48, Matthew Wilson wrote:
> Are there plans to backport this fix to 20.04 and 20.10?

Yes. The fix has been uploaded to the focal and groovy queues for stable
release updates.

** Also affects: mutter (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: gnome-shell (Ubuntu Focal)

** No longer affects: gnome-shell (Ubuntu Groovy)

** Changed in: mutter (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: mutter (Ubuntu Focal)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mutter (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: mutter (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Groovy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Input device settings not applied on hotplug/reconnect/resume in Xorg
  sessions

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

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

[Bug 1908779] Re: Usb doens't work with kernel 5.4.0-56 -58

[lan]

# uname -a
Linux meteo 5.10.0-051000-generic #202012132330 SMP Sun Dec 13 23:33:36 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

# lsusb 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 
Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 0fde:ca01 Oregon Scientific WMRS200 weather station
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@meteo:/home/lan# 

It work!

You need other tests/informations ?

There is also on-going a patch for my old kernel or I need to use this?

Thank you!

Leo

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

Title:
  Usb doens't work with  kernel 5.4.0-56 -58

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

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

[Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[Kai-Heng Feng]

Ok, so it's likely a kernel regression. What was the last kernel version
doesn't have this issue?

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

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

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

[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions

[Matthew Wilson]

Are there plans to backport this fix to 20.04 and 20.10?  Or do we have
to put up with broken mice until 21.04?

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

Title:
  Input device settings not applied on hotplug/reconnect/resume in Xorg
  sessions

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

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

[Bug 1908554] Re: Standby problems solved only in specific kernel version

[Kai-Heng Feng]

FWIW I've never worked on a system that support S1...

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

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

Title:
  Standby problems solved only in specific kernel version

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

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

[Bug 1908554] Re: Standby problems solved only in specific kernel version

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/amd64/

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

Title:
  Standby problems solved only in specific kernel version

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

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

[Bug 1908779] Re: Usb doens't work with kernel 5.4.0-56 -58

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/amd64/

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

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

Title:
  Usb doens't work with  kernel 5.4.0-56 -58

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

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

[Bug 1904866] Re: Software updater fails to update with errors

[Leó Kolbeinsson]

Received again testing Xubuntu Hirsute daily iso 
http://cdimage.ubuntu.com/xubuntu/daily-live/20201219/hirsute-desktop-amd64.iso
on machine running VirtualBox

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

Title:
  Software updater fails to update with errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1904866/+subscriptions

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

[Bug 1908322] Re: Dell WD19 upgrade issue

[Kai-Heng Feng]

Ok, let's wait for TBT maintainer's fix.

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

Title:
  Dell WD19 upgrade issue

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

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

[Bug 1905179] Re: SDcard show wrong date (one month ahead)

[Kai-Heng Feng]

Ok, please use kernel 5.7+ for kernel space exfat support.

For 20.04, this can be achieved by 
$ sudo apt install linux-generic-hwe-20.04-edge

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

Title:
  SDcard show wrong date (one month ahead)

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

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

[Bug 1908794] [NEW] update-manager-core: hwe-support-status recommends 18.04 on 20.04

[h]

Public bug reported:

/usr/bin/hwe-support-status recommends installing the hwe of 18.04 when
on 20.04

The system got upgraded from 14.04 to 16.04 to 18.04 to 20.04.


# uname -a
Linux intern 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename:   focal
# cat /usr/lib/os-release 
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
# /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
# /usr/bin/hwe-support-status 

You have packages from the Hardware Enablement Stack (HWE) installed that
are going out of support on 2025-04-30.

To upgrade to a supported (or longer-supported) configuration:

* Upgrade from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS by running:
sudo do-release-upgrade -p

OR

* Switch to the current security-supported stack by running:
sudo apt-get install 

and reboot your system.

EXPECTED

There shouldn't be an advice to install hwe of 18.04 being on 20.04.

"sudo apt-get install" and "sudo do-release-upgrade -p" do nothing and
they don't change the message.

** Affects: update-manager (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/1908794

Title:
  update-manager-core: hwe-support-status recommends 18.04 on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908794/+subscriptions

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

[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Kai-Heng Feng]

Thanks. That boils down to two commits:
9af0c46a761293ef04c57f001cc2641d4ec1add3 media: rc: uevent sysfs file races 
with rc_unregister_device()
bff924ee40ae3857e7373536fdda203378795e3c media: rc: do not access device via 
sysfs after rc_unregister_device()

Can you please try which one breaks it?

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

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

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

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

[Bug 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.9-2ubuntu1.1~20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Backport packages for 20.04.2 HWE stack

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

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

[Bug 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: xorg-server (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Backport packages for 20.04.2 HWE stack

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

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

[Bug 1908699] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  New bugfix release 20.2.6

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

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

[Bug 1908699] Re: New bugfix release 20.2.6

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

** Changed in: mesa (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  New bugfix release 20.2.6

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

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

[Bug 1632694] Re: update-grub fails to detect zfs pool name

[Doug Goldstein]

I've submitted a more permanent fix to the upstream project.
https://lists.gnu.org/archive/html/grub-devel/2020-12/msg00239.html

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

Title:
  update-grub fails to detect zfs pool name

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

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

[Bug 1908787] [NEW] Weather widget can't be configured

[Len Ovens]

Public bug reported:

The weather applet/widget shows a question mark symbol and hover over
says please configure. It was configured and working fine before.
Configure screen shows my city location ok but if I use the choose box
and type a city in and hit search... it stays busy forever. It seems not
using environment Canada does work

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: plasma-widgets-addons 4:5.18.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73
Uname: Linux 5.4.0-58-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sat Dec 19 07:24:24 2020
InstallationDate: Installed on 2020-04-23 (240 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422)
SourcePackage: kdeplasma-addons
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kdeplasma-addons (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Weather widget can't be configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdeplasma-addons/+bug/1908787/+subscriptions

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

[Bug 1889665] Re: Apache2 is not running after charm config changed

[Erik Ilavsky]

placement #15 , focal

** Also 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/1889665

Title:
  Apache2 is not running after charm config changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-octavia/+bug/1889665/+subscriptions

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

[Bug 1725941] Re: hotCorner modification breaks official apps-menu extension

[Denis Gorodnichev]

** Changed in: gnome-shell-extensions (Ubuntu)
 Assignee: Denis Gorodnichev (d-g) => (unassigned)

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

Title:
  hotCorner modification breaks official apps-menu extension

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

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

[Bug 1899800] Re: Runtime deadlock: pthread_cond_signal failed to wake up pthread_cond_wait due to a bug in undoing stealing

[Michael Bacarella]

Thanks for this.  Tested for about 20 hours on groovy-proposed.  Neither
the repro nor my OCaml application has deadlocked.

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

Title:
  Runtime deadlock: pthread_cond_signal failed to wake up
  pthread_cond_wait due to a bug in undoing stealing

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

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

[Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Pattapong]

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Pattapong (apattapong)

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

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

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

[Bug 1908785] [NEW] gui glitch

[Imre Péntek]

Public bug reported:

When I click the előzmények (preliminary/previously/history) tab in
Noteszgép akkumlátor (battery of the laptop) and then click back to
Hálózati csatlakozó (mains power) the right hand side goes empty.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-power-manager 3.32.0-2
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 19 15:42:46 2020
InstallationDate: Installed on 2019-11-23 (392 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
UpgradeStatus: Upgraded to focal on 2020-06-03 (199 days ago)

** Affects: gnome-power-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  gui glitch

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

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

[Bug 1908785] Re: gui glitch

[Imre Péntek]

** Attachment added: "Screencast 2020-12-19 15:45:25.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1908785/+attachment/5445092/+files/Screencast%202020-12-19%2015%3A45%3A25.mp4

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

Title:
  gui glitch

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

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