[Kernel-packages] [Bug 1916573] Re: display can not wake up from sleeping.

[nullshaw]

Anyone has the same problem?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1916573

Title:
  display can not wake up from sleeping.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  os system: ubuntu 20.04.2 LTS

  when I press the keyboard, I saw new log from ssh terminal.

  /var/log/kern.log

  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.303887] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.307888] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.346636] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.350790] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917234] UdevDb.txt

[sessetessu2021]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1917234/+attachment/5471260/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917234

Title:
  HP Printer Assistant inks status ubuntu LTS HP deskjet 2600 series

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HP Printer Assistant inks status ubuntu LTS
  HP deskjet 2600 series inks status HP printer assistant
  HP printers inks status HP printers assistant inks status
  informations ubuntu 21.04 LTS and ubuntu LTS 22.04 LTS
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessetessu   1398 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME

[Kernel-packages] [Bug 1885085] [NEW] Suspend is not deep

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After a fresh Ubuntu 20.04 installation, the suspend is not "deep" but it is 
"idle".
Deep is very important, otherwise the laptop/notebook might over heat (!) if 
you put it into a sleeve or bag while suspended. Which happened to my notebook.

How to reproduce:

1) install Ubuntu 20.04 on a notebook/laptop
2) suspend via lid close or suspend button or gnome shell system menu
3) wake up from suspend and type
sudo journalctl | grep "PM: suspend" | tail -2
4) find the message "PM: suspend entry (s2idle)"

How to fix the issue:

1) sudo nano /etc/default/grub
2) Replace the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
3) recreate grub with
sudo grub-mkconfig -o /boot/grub/grub.cfg
4) reboot
5) suspend via lid close or suspend button or gnome shell system menu
6) wake up from suspend and run
sudo journalctl | grep "PM: suspend" | tail -2
7) find the message "PM: suspend entry (deep)"

This fixes your suspend and makes your laptop go into deep sleep, which
greatly increases suspended battery uptime and greatly decreases the
heat the notebook creates.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 25 09:14:57 2020
InstallationDate: Installed on 2020-06-23 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal
-- 
Suspend is not deep
https://bugs.launchpad.net/bugs/1885085
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1885085] Re: Suspend is not deep

[Julian Andres Klode]

** Package changed: grub2 (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885085

Title:
  Suspend is not deep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh Ubuntu 20.04 installation, the suspend is not "deep" but it is 
"idle".
  Deep is very important, otherwise the laptop/notebook might over heat (!) if 
you put it into a sleeve or bag while suspended. Which happened to my notebook.

  How to reproduce:

  1) install Ubuntu 20.04 on a notebook/laptop
  2) suspend via lid close or suspend button or gnome shell system menu
  3) wake up from suspend and type
  sudo journalctl | grep "PM: suspend" | tail -2
  4) find the message "PM: suspend entry (s2idle)"

  How to fix the issue:

  1) sudo nano /etc/default/grub
  2) Replace the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  3) recreate grub with
  sudo grub-mkconfig -o /boot/grub/grub.cfg
  4) reboot
  5) suspend via lid close or suspend button or gnome shell system menu
  6) wake up from suspend and run
  sudo journalctl | grep "PM: suspend" | tail -2
  7) find the message "PM: suspend entry (deep)"

  This fixes your suspend and makes your laptop go into deep sleep,
  which greatly increases suspended battery uptime and greatly decreases
  the heat the notebook creates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 25 09:14:57 2020
  InstallationDate: Installed on 2020-06-23 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1906384] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-03-01 03:50 EDT---
IBM Bugzilla status->closed, Problem could currently not reproduced. Therefore 
-> close. If problem reoccur a new ticket will be opened.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906384

Title:
  [UBUNTU 18.04] lvm boot failure

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  boot failure with LVM root disk
   
  ---uname output---
  4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x 
s390x GNU/Linux
   
  Machine Type = 8561 LT1 
   
  ---System Hang---
   Boot failure with LVM root disk and enter emergency shell
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   boot the system
   
  *Additional Instructions for Chee Ye/y...@cn.ibm.com:
  -Attach:
/proc/partitions
/proc/mounts/
/etc/lvm/lvm.conf
dmsetup ls
dmsetup table
dmsetup targets
dmsetup version
lvm version

  
  During boot, got below error message and then entered emergency shell. I am 
attaching part of the console log from HMC. 

  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices."
  done.
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: error opening /dev/md?*: No such file or directory"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  done.
  "Gave up waiting for root file system device.  Common problems:"
  "- Boot args (cat /proc/cmdline)"
  "- Check rootdelay= (did the system wait long enough?)"
  "- Missing modules (cat /proc/modules; ls /dev)"
  "chvt: can't open console"
  "ALERT!  /dev/mapper/ISVCL1--vg-root does not exist.  Dropping to a shell!"
  "Couldn't get a file descriptor referring to the console"
  "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such 
device o"
  "r address"
  "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device 
or ad"
  dress
  "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device 
or"
  address
  "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such 

[Kernel-packages] [Bug 1906384] Re: [UBUNTU 18.04] lvm boot failure

[Frank Heimes]

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

** Changed in: ubuntu-z-systems
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906384

Title:
  [UBUNTU 18.04] lvm boot failure

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  boot failure with LVM root disk
   
  ---uname output---
  4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x 
s390x GNU/Linux
   
  Machine Type = 8561 LT1 
   
  ---System Hang---
   Boot failure with LVM root disk and enter emergency shell
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   boot the system
   
  *Additional Instructions for Chee Ye/y...@cn.ibm.com:
  -Attach:
/proc/partitions
/proc/mounts/
/etc/lvm/lvm.conf
dmsetup ls
dmsetup table
dmsetup targets
dmsetup version
lvm version

  
  During boot, got below error message and then entered emergency shell. I am 
attaching part of the console log from HMC. 

  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn 
be"
  "cause device was seen first."
  "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices."
  done.
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: error opening /dev/md?*: No such file or directory"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  "mdadm: No arrays found in config file or automatically"
  done.
  "Gave up waiting for root file system device.  Common problems:"
  "- Boot args (cat /proc/cmdline)"
  "- Check rootdelay= (did the system wait long enough?)"
  "- Missing modules (cat /proc/modules; ls /dev)"
  "chvt: can't open console"
  "ALERT!  /dev/mapper/ISVCL1--vg-root does not exist.  Dropping to a shell!"
  "Couldn't get a file descriptor referring to the console"
  "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such 
device o"
  "r address"
  "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device 
or ad"
  dress
  "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device 
or"
  address
  "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device 
or ad"
  dress
  "/scripts/panic/console_setup: line 1: can't create /dev/tty3

[Kernel-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

[Sebastien Bacher]

Removing block-proposed, the idea was to deal with the regression but
that's not happening and we need to land the hirsute update anyway now
that we are past feature freeze

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1905627

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

[Łukasz Zemczak]

Just a quick question regarding the virtualbox failures, what I'd like
to know: why did the tests pass with the old dkms package version? If
you check the ADT test history for groovy for instance, the tests for
non-amd64 arches only fail with the new dkms. I understand they might
not be meant to work for non-x86, but I'm just curious why suddenly they
are now failing.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1915051

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  Fix Committed
Status in dkms source package in Focal:
  Fix Committed
Status in dkms source package in Groovy:
  Fix Committed
Status in dkms source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917275] Re: MSI MS-7817 desktop linux kernel 5.4

[Colin Watson]

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

** This bug has been marked a duplicate of bug 1917274
   MSI MS-7817 desktop linux kernel 5.4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917275

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 working
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1913187] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for iproute2 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1913187

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1913187] Re: iproute2 segfaults when filtering sockets

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.15.0-2ubuntu1.3

---
iproute2 (4.15.0-2ubuntu1.3) bionic; urgency=medium

  * Fix: NULL dereference when rendering without header (LP: #1913187)
- d/p/lp1913187-ss-fix-NULL-dereference-when-rendering.patch

 -- Rafael David Tinoco   Tue, 26 Jan 2021
13:33:08 +

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1913187

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917275] Re: MSI MS-7817 desktop linux kernel 5.4

[sessetessu2021]

** This bug is no longer a duplicate of bug 1917274
   MSI MS-7817 desktop linux kernel 5.4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917275

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 working
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917274] Re: MSI MS-7817 desktop linux kernel 5.4

[sessetessu2021]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => sessetessu2021 (sessetessu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Coiby Xu]

On Fri, Feb 26, 2021 at 02:28:24PM -, Marton Danko wrote:
>Hi Coiby,
>
>Thanks, it seems that correctly telling which hardware button do I press.
>Right:
>-event18  POINTER_BUTTON   +0.174s  BTN_RIGHT (273) pressed, seat count: 1
> event18  POINTER_BUTTON   +0.318s  BTN_RIGHT (273) released, seat count: 0
>Middle:
> event18  POINTER_BUTTON   +3.086s  BTN_MIDDLE (274) pressed, seat count: 1
> event18  POINTER_BUTTON   +3.362s  BTN_MIDDLE (274) released, seat count: > 0
>Left:
> event18  POINTER_BUTTON   +5.132s  BTN_LEFT (272) pressed, seat count: 1
> event18  POINTER_BUTTON   +5.271s  BTN_LEFT (272) released, seat count: 0
>
>And in the mentioned bug report the following resolution works:
>"Apparently it's a change they did in GNOME 3.28 and can be fixed by switching 
>to Area mouse click emulation in GNOME Tweaks."
>

Good to know that:)

>Thanks for your help, and now I need to go to the corner to cry again,
>why such a stupid default configuration is shipped with the system...
>

You are welcome!

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does n

[Kernel-packages] [Bug 1917309] [NEW] i can not find touch pad

[gehadmohammed]

Public bug reported:

i can not find touch pad

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-66-generic 5.4.0-66.74
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gehad  2056 F pulseaudio
 /dev/snd/controlC0:  gehad  2056 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  1 14:00:48 2021
InstallationDate: Installed on 2020-04-11 (323 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: HP HP Pavilion Notebook
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=4837c49a-1c9f-4f9e-a0d6-e8ab0d6dd2a6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-66-generic N/A
 linux-backports-modules-5.4.0-66-generic  N/A
 linux-firmware1.187.9
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-14 (321 days ago)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.17
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 80B5
dmi.board.vendor: HP
dmi.board.version: 81.29
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.17:bd03/09/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: P1Q16EA#A2N
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917309

Title:
  i can not find touch pad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i can not find touch pad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-66-generic 5.4.0-66.74
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gehad  2056 F pulseaudio
   /dev/snd/controlC0:  gehad  2056 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 14:00:48 2021
  InstallationDate: Installed on 2020-04-11 (323 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=4837c49a-1c9f-4f9e-a0d6-e8ab0d6dd2a6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-14 (321 days ago)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B5
  dmi.board.vendor: HP
  dmi.board.version: 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.17:bd03/09/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: P1Q16EA#A2N
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917309] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917309

Title:
  i can not find touch pad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i can not find touch pad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-66-generic 5.4.0-66.74
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gehad  2056 F pulseaudio
   /dev/snd/controlC0:  gehad  2056 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 14:00:48 2021
  InstallationDate: Installed on 2020-04-11 (323 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=4837c49a-1c9f-4f9e-a0d6-e8ab0d6dd2a6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-14 (321 days ago)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B5
  dmi.board.vendor: HP
  dmi.board.version: 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.17:bd03/09/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: P1Q16EA#A2N
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-460/460.56-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: nvidia-graphics-drivers-460 (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level te

[Kernel-packages] [Bug 1916908] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460-server/460.32.03-0ubuntu0.20.10.2 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan.
  - Fixed

[Kernel-packages] [Bug 1915935] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-460/460.56-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: nvidia-graphics-drivers-460-server (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  New
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Verification of this is handled via
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460/+bug/1916908 .

** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy)
   Status: New => Fix Committed

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  New
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460-server/460.32.03-0ubuntu0.20.10.2 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  New
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-450/450.102.04-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-450 (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
    

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-450/450.102.04-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-450 (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

[Marcelo Cerri]

Hi, Łukasz.

I believe they were passing simply because the DKMS tests weren't being
triggered. Those past tests were run with the old version of dkms-
autopkgtest (from dkms) and thus only binary packages with names ending
with "-dkms" were tested by it (whick is not the case for virtualbox-
hwe).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1915051

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  Fix Committed
Status in dkms source package in Focal:
  Fix Committed
Status in dkms source package in Groovy:
  Fix Committed
Status in dkms source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Guilherme G. Piccoli]

Hi Jarno, can you please confirm if that behavior you observed is not
explained by
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885085 ?

Thnaks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Alberto Milone]

** Tags removed: block- proposed-groovy
** Tags added: block-proposed-groovy verification-needed-bionic 
verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan.
  - Fixed a bug where calls to vkCreateDevice could fail on Ampere
    GPUs when ray tracing extensions were enabled and the
    application was running within the Steam Linux Runtime.
  - Fixed a regression that could cause display corruption when
    using a scaled resolution after resuming from power management
    suspend.
    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
  - Advertise support for cuda-11.2-1.

  == 460-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
    * debian/templates/dkms_nvidia.conf.in,
  debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch:
  - Add support for Linux 5.11 (LP: #1916908).

  == 450 / 450-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
    * debian/templates

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-450-server/450.102.04-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-450-server (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for t

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-450-server/450.102.04-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-450-server (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-390 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-390 (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
   

[Kernel-packages] [Bug 1915935] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-390 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.2 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  New
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1909369] Re: linux-headers-5.10.3-051003-generic is not supported

[Rod Smith]

I can confirm that the PPA described in post #2, above, works on a
MacBook Air 6,2. Please get this fixed prior to Hirsute's final release!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1909369

Title:
  linux-headers-5.10.3-051003-generic is not supported

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  > $  lsb_release -rd  
 
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  > $  sudo apt-cache policy bcmwl-kernel-source
 
  bcmwl-kernel-source:
Installé : (aucun)
Candidat : 6.30.223.271+bdcom-0ubuntu5
   Table de version :
   6.30.223.271+bdcom-0ubuntu5 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 
Packages

  Hello,

  I tried to install a wireless network adapter broadcom BCM4360, i nned to 
install the package bcmwl-kernel-source but when i try to install it i have the 
following error : "ERROR (dkms apport): kernel package 
linux-headers-5.10.3-051003-generic is not supported
  Error! Bad return status for module build on kernel: 5.10.3-051003-generic 
(x86_64)
  "

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source (not installed)
  Uname: Linux 5.10.3-051003-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 26 21:16:07 2020
  InstallationDate: Installed on 2020-01-05 (356 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-418-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418-server/418.181.07-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-418-server (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support f

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-418-server into groovy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418-server/418.181.07-0ubuntu0.20.10.2 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: nvidia-graphics-drivers-418-server (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  New
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1787396] Re: ss crashes when using --no-header

[Simon Déziel]

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

** This bug has been marked a duplicate of bug 1913187
   iproute2 segfaults when filtering sockets

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1787396

Title:
  ss crashes when using --no-header

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Listen on port 8989:
  $ nc -l 8989 &

  2) Check that ss can list this listener:
  $ ss --no-header -nto state listening 'sport = 8989'
  010.0.0.0:8989  0.0.0.0:*

  3) Ask ss to list listeners on a port where nothing listens
  $ kill %1 # stops nc
  $ ss --no-header -nto state listening 'sport = 8989'
  Segmentation fault (core dumped)

  In the above, removing "--no-header" avoids the segfault.

  
  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 08:17:52 2018
  InstallationDate: Installed on 2018-07-15 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916570] Re: BlueZ 5.56 release

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.56-0ubuntu1

---
bluez (5.56-0ubuntu1) hirsute; urgency=medium

  * New upstream release 5.56 (LP: #1916570)
- Fix issue with setting AVDTP disconnect timer.
- Fix issue with AVDTP not sending GetCapabilities.
- Fix issue with AVDTP connecting using streaming mode.
- Fix issue with handling A2DP and remote SEP disappearing.
- Fix issue with handling session of A2DP channels.
- Fix issue with GATT and handling device removal.
- Fix issue with GATT not accepting multiple requests.
- Fix issue with HID report value callback registration.
- Add support for new advertising management command.
- Add support for battery D-Bus interface.
  * Refreshed patches:
- 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch
- 0001-obex-Use-GLib-helper-function-to-manipulate-paths.patch
- 0002-hostname-handle-chassis-type-handset.patch
- bluetooth.conf.patch
- change_path_of_hogsuspend.patch
- raspi-bcm43xx-3wire.patch
- raspi-bcm43xx-load-firmware.patch
- raspi-cypress-305-bdaddr.patch
  * Removed packaging of deprecated files bccmd*
  * debian/libbluetooth3.symbols: Added new function bt_malloc0
  * Dropped patch migrate_scripts_python3.patch because nobody was maintaining
or using it, and it caused conflicts. If you want to run tests using
python3 then please propose it upstream. Otherwise we do still package
bluez-tests, and if you really need to run them then use your own python2.

 -- Daniel van Vugt   Tue, 23 Feb 2021
17:58:00 +0800

** Changed in: bluez (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1916570

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917210] [NEW] Dell XPS 13 2in1 wakes from sleep when moved on 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS.

Laptop suspends and wakes up when lid is closed and opened, respectively.
Laptop erroneously wakes up also in following conditions:

 1. lid is closed and laptop is moved/rotated.
 2. lid is open, suspended manually (via power button), and laptop is 
moved/rotated.

Until I found out about case 2, I assumed that the hall sensor triggered on 
slight opening
of the lid. However, case 2 shows that this is unlikely a hard ware 
defect/sensitivity.
I suspect that the accelaration sensor triggers waking up from sleep.

I can confirm that the problem persist after stopping the iio-sensor-prox 
service via systemctl.
I did not find which kernel module is reponsible for tracking this sensor. 
Suggestions?

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


** Tags: bot-comment
-- 
Dell XPS 13 2in1 wakes from sleep when moved on 20.04
https://bugs.launchpad.net/bugs/1917210
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04

[Brian Murray]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917210

Title:
  Dell XPS 13 2in1 wakes from sleep when moved on 20.04

Status in linux package in Ubuntu:
  New

Bug description:
  Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS.

  Laptop suspends and wakes up when lid is closed and opened, respectively.
  Laptop erroneously wakes up also in following conditions:

   1. lid is closed and laptop is moved/rotated.
   2. lid is open, suspended manually (via power button), and laptop is 
moved/rotated.

  Until I found out about case 2, I assumed that the hall sensor triggered on 
slight opening
  of the lid. However, case 2 shows that this is unlikely a hard ware 
defect/sensitivity.
  I suspect that the accelaration sensor triggers waking up from sleep.

  I can confirm that the problem persist after stopping the iio-sensor-prox 
service via systemctl.
  I did not find which kernel module is reponsible for tracking this sensor. 
Suggestions?

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917210] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1917210

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917210

Title:
  Dell XPS 13 2in1 wakes from sleep when moved on 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS.

  Laptop suspends and wakes up when lid is closed and opened, respectively.
  Laptop erroneously wakes up also in following conditions:

   1. lid is closed and laptop is moved/rotated.
   2. lid is open, suspended manually (via power button), and laptop is 
moved/rotated.

  Until I found out about case 2, I assumed that the hall sensor triggered on 
slight opening
  of the lid. However, case 2 shows that this is unlikely a hard ware 
defect/sensitivity.
  I suspect that the accelaration sensor triggers waking up from sleep.

  I can confirm that the problem persist after stopping the iio-sensor-prox 
service via systemctl.
  I did not find which kernel module is reponsible for tracking this sensor. 
Suggestions?

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Jarno Suni]

Hi Guilherme, I have mixed result:

$ LC_ALL=C sudo journalctl | grep "PM: suspend" | tail -n 17
Sep 22 11:19:52 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend exit
Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend entry (s2idle)
Sep 22 11:20:36 jarnos-OptiPlex-745 kernel: PM: suspend exit
Sep 22 11:21:26 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Sep 22 11:30:00 jarnos-OptiPlex-745 kernel: PM: suspend exit
Dec 04 15:53:23 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Dec 04 17:50:48 jarnos-OptiPlex-745 kernel: PM: suspend exit
Dec 04 18:40:19 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Dec 04 18:50:02 jarnos-OptiPlex-745 kernel: PM: suspend exit
Dec 04 19:35:56 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Dec 05 01:07:52 jarnos-OptiPlex-745 kernel: PM: suspend exit
Feb 14 14:52:33 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Feb 20 22:59:47 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Feb 21 14:21:38 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Feb 21 18:43:59 jarnos-OptiPlex-745 kernel: PM: suspend exit
Feb 28 23:32:29 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Guilherme G. Piccoli]

Thanks Jarno. Can you run a test with them? Force one method to be used (like 
"deep"), following the commnad-line option in LP #1885085, and run 10 tests...5 
of them after a reboot.
After that, force the other and re-run the tests. Let's see if we can narrow 
your issue to one suspend method.

Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460 into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-460/460.56-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: nvidia-graphics-drivers-460 (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
     

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460 into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-460/460.56-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: nvidia-graphics-drivers-460 (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  New
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Jarno Suni]

According to above, exiting suspend has failed only in deep mode, but I
wonder why there is one s2idle mode. Maybe later I rub some tests.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Luis]

Issue:

- I can switch profiles, but when I chose HSP/HFP I get no sound and the 
microphone doesn't work.
- I didn't have this issue in 18.04 LTS or 16.04 LTS (same hardware)

Environment:

- Kernel: Linux 5.8.0-44-generic
- OS: Ubuntu 20.04.1 LTS
- Headset: WC-CH500
- BT Dongle: Plugable USB Bluetooth 4.0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key

[Martin Jansa]

Not sure if this is the right place to report this, but these changes
seem to cause automated mainline kernel builds to fail.

e.g.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.1/amd64/log
shows
make[3]: *** No rule to make target 'debian/canonical-certs.pem', needed by 
'certs/x509_certificate_list'.  Stop.

possibly because changes from this ticket were only partially migrated
there e.g. in:

https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git
/mainline-
crack/commit/?h=cod/mainline/v5.11.1&id=4508c61e1cf702e70308f1c1fbb0f26a45d0b853

which updated the configs, but not the rule for debian/canonical-
certs.pem in debian/rules.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1898716

Title:
  Please trust Canonical Livepatch Service kmod signing key

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-gcp source package in Focal:
  Confirmed
Status in linux-kvm source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-gcp source package in Groovy:
  New
Status in linux-kvm source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * Currently Canonical Livepatch service is signing kernel modules
  that are not trusted by the default Ubuntu kernels

   * to make Canonical Livepatch service out of the box compatible with
  SecureBoot, please add Canonical Livepatch service key as trusted in
  the kernel by default

   * if user wants to distrust the key, they can remove it via mokx,
  dbx, and we can revoke it by signing revocation with 'canonical master
  ca'.

  [Test Case]

   * Boot kernel
   * Check the built-in keyring to ensure that Livepatch key is trusted by the 
built-in keyring

  Bad:
  $ sudo keyctl list %:.builtin_trusted_keys
  1 key in keyring:
  204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 4182e0d0113d4a8f460783380c9e618ef1597bf5

  Good:
  $ sudo keyctl list %:.builtin_trusted_keys
  2 keys in keyring:
  637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc
  1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch 
Signing: 14df34d1a87cf37625abec039ef2bf521249b969

  [Regression Potential]

   * Kernel keyring size will increase by one key. And thus kernel image
  will too.

  [Other Info]

   * Current livepatch key fingerprints

  mokutil uses der format

  $ openssl x509 -inform der -in 
/snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint 
-sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  kernel use pem format

  $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout 
-fingerprint -sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  [Target kernels]

  bionic and up, across the board, but maybe excluding fips kernels?!

  [Patch]

  https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1917283] Re: "The following packages have been kept back:" bionic requesting focal downloads

[Michael F Winthrop]

Chris,

I did not know the multiple support places that might be involved. I 
followed the "advice" to report this problem from the updater, which led 
me to the Kernel group. I use apt, apt-get, and aptitude (depending on 
the difficulty) for updating. I did spend a long time (from the latest 
bionic kernel update to now) trying to find a solution for this. I 
searched all the forums via duckduckgo and none were about a mislaid 
update element (focal dependencies in bionic distro). I thought that the 
problem might have been caused by the kernel dependencies list when the 
kernel was updated. An incidental "solution" may well relate to the 
other resources you suggest, however, this problem only occurred on 
update of the kernel to 136 from 135. In that update, the packages did 
not (from my pea brained memory) include the ones in the bug report. I 
did note that libc6 was listed as a dependency from 27 to 29 for some of 
the focal components when I did a build-dep request in apt-get. Since I 
am not adept at the specific kernel ancillary dependencies that are met 
to perform the update, and since the problem started with the update, I 
thought the bug was properly made. I have kubuntu (kde) version of 
ubuntu which is oriented towards audio elements. Some kernel items (I am 
guessing) include MIDI devices, audio steam control and linking 
[pulseaudio], etc. Are distro kernel dependencies verified for release 
compatibility? That is, are the elements that use the kernel in a given 
distribution verified anywhere as specific to that kernel long term 
release, and by whom? The applications looking for focal dependencies 
may/may-not be focal release. I do not know. Right now this is a bag of 
worms for me.

*Yours in Lionism,

Michael F Winthrop
Member: Sterling Lions Club, VA
Member: EAA Chapter 186, Manassas Apt. KHEF *
On 3/1/21 2:24 AM, Chris Guiver wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Bug reporting is mostly about finding & fixing problems thus preventing
> future users from hitting the same bug.
>
> I suspect a Support site would be more appropriate, eg.
> https://answers.launchpad.net/ubuntu. You can also find help with your
> problem in the support forum of your local Ubuntu community
> http://loco.ubuntu.com/ or asking at https://askubuntu.com or
> https://ubuntuforums.org, or for more support options please look at
> https://discourse.ubuntu.com/t/community-support/709
>
> (Note: you've filed this is as a kernel bug (against the linux kernel)
> but mention release-upgrade so I wonder if your intended package should
> be ubuntu-release-upgrader, but a quick scan of your mentioned packages
> shows numerous 3rd party packages that I don't see matching any
> supported release of Ubuntu; so I'd suggest seeking support & possibly
> using ppa-purge, but your description doesn't appear to be about a
> kernel issue so I'm confused).
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917283

Title:
  "The following packages have been kept back:" bionic requesting focal
  downloads

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am happily running Bionic 18.04 Kubuntu (all previous bugs
  resolved). I decided to upgrade to Focal 20.04 and got a failure for
  an unsolvable conflict. I discovered a ppa for xenial was the cause. I
  removed that and then retried. (All my ppa were now for Bionic so it
  seemed safe)

  sudo do-release-upgrade
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgrading.

  On "sudo apt update" I discovered that numerous pulseaudio
  applications and dependencies were a problem:"The following packages
  have been kept back:"

  dad@dad314159:~$ sudo apt list -a --upgradable
  Listing... Done
  libpulse-dev/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 
1:11.1-1ubuntu7.11]
  libpulse-dev/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 
[installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1]
  libpulse-dev/bionic 1:11.1-1ubuntu7 amd64

  libpulse-mainloop-glib0/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 
[upgradable from: 1:11.1-1ubuntu7.11]
  libpulse-mainloop-glib0/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 
amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1]
  libpulse-mainloop-glib0/bionic 1:11.1-1ubuntu7 amd64

  libpulse0/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 
1:11.1-1ubuntu7.11]
  libpulse0/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 
[installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1]
  libpulse0/bionic 1:11.1-1ubuntu7 amd64

  libpulsedsp/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 
1:11.1-1ubuntu7.11]
  libpulsedsp/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 
[installed,upgradable to: 1:13.99.1-1ubuntu3.7+kx

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Guilherme G. Piccoli]

Can you also attach the syslog? Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460-server/460.32.03-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-460-server (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support f

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-460-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460-server/460.32.03-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-460-server (Ubuntu Focal)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  New
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  New
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917265] Re: Suspending to RAM freezes computer

[Jarno Suni]

I tried a couple of times. It does not work no matter which mode I use.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917265

Title:
  Suspending to RAM freezes computer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to suspend, it does not work: fans keep spinning, but just
  screen blanks and computer does not respond to keyboard. 'journalctl
  -b -1' does not tell anything suspicious after shut down - start. This
  used to work. Might not be reproduceable always.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-65-generic 5.4.0-65.73
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarnos 1014 F pulseaudio
   /dev/snd/controlC2:  jarnos 1014 F pulseaudio
   /dev/snd/controlC0:  jarnos 1014 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb 28 23:57:02 2021
  InstallationDate: Installed on 2020-05-03 (301 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450 into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-450/450.102.04-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-450 (Ubuntu Focal)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450 into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-450/450.102.04-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-450 (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following

[Kernel-packages] [Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04

[Guilherme G. Piccoli]

Hi Ariel, thanks for your report! So, let me clarify: now your system is 
freezing on boot, you don't need to run "lspci" to observe the freeze anymore?
Can you try adding "ignore_loglevel" in the kernel command-line on Grub, and 
observe the boot progressing? If so, then please  take a screenshot/photo when 
it freezes, so we can see the last messages observed. 

If machine is booting fine with the USB stick, can you perform such boot and 
try lspci from the live Ubuntu image? If lspci is a reproducer, it is worth to 
collect a dmesg while the problem happens, so we can investigate if any message 
pops during the event.
Thanks,


Guilherme

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917194

Title:
  [Dell G5 5590] lspci freezes computer on Ubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 18.04 to 20.04 my computer started to
  freeze when running lspci.

  I ended up noticing that it happened when trying to query device
  '1f:00.0' a USB port. After some kernel and bios updates the problem
  got worse. Now the computer freezes ~5 seconds after booting up.

  I tried:
  1) Running in recovery mode, also freezes
  2) Running an older kernel version (5.4.0-66-generic), also freezes
  3) Removing nvidia drivers (just in case), also freezes
  4) Running all combinations nodemodeset, acpi=off an nouveau blacklisting
  5) Updating all drivers

  The computer freezes for ever, I can't switch TTYs, move the mouse,
  anything, the only way to leave was to force shutdown. On the last
  cases after switching to a tty I could see this messages before the
  freeze ocurred:

  kernel: xhci_hcd :1f:00.0: PCI post-resume error -19!
  kernel: xhci_hcd :1f:00.0: HC died; cleaning up

  Running Ubuntu 20.04 from a USB sticks works fine, as well as doing a fresh 
install.
  All logs were obtained by chrooting to the faulty partition from a fresh 
install, if there are any more logs that would be helpful, let me know.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1385113

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-450-server/450.102.04-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-450-server (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this b

[Kernel-packages] [Bug 1916908] Proposed package upload rejected

[Łukasz Zemczak]

An upload of nvidia-graphics-drivers-390 to focal-proposed has been
rejected from the upload queue for the following reason: "There seem to
be some patch conflict tags in the debian/ parts being updated? Lo".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan.
  - Fixed a bug where calls to vkCreateDevice could fail on Ampere
    GPUs when ray tracing extensions were enabled and the
    application was running within the Steam Linux Runtime.
  - Fixed a regression that could cause display corruption when
    using a scaled resolution after resuming from power management
    suspend.
    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
  - Advertise support for cuda-11.2-1.

  == 460-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
    * debian/templates/dkms_nvidia.conf.in,
  debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch:
  - Add support for Linux 5.11 (LP: #1916908).

  == 450 / 450-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Łukasz Zemczak]

Ok, got cut here, what I meant to say is: "There seem to be some patch
conflict tags in the debian/ parts being updated? Looks like something
didn't apply cleanly. Please check and re-upload."

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan.
  - Fixed a bug where calls to vkCreateDevice could fail on Ampere
    GPUs when ray tracing extensions were enabled and the
    application was running within the Steam Linux Runtime.
  - Fixed a regression that could cause display corruption when
    using a scaled resolution after resuming from power management
    suspend.
    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
  - Advertise support for cuda-11.2-1.

  == 460-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
    * debian/templates/dkms_nvidia.conf.in,
  debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch:
  - Add support for Linux 5.11 (LP: #1916908).

  == 450 / 450-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia

[Kernel-packages] [Bug 1916908] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-418-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418-server/418.181.07-0ubuntu0.20.04.2 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 Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1916908

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan

[Kernel-packages] [Bug 1915935] Proposed package upload rejected

[Łukasz Zemczak]

An upload of nvidia-graphics-drivers-390 to focal-proposed has been
rejected from the upload queue for the following reason: "There seem to
be some patch conflict tags in the debian/ parts being updated? Lo".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Ok, got cut here, what I meant to say is: "There seem to be some patch
conflict tags in the debian/ parts being updated? Looks like something
didn't apply cleanly. Please check and re-upload."

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-418-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418-server/418.181.07-0ubuntu0.20.04.2 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 Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-450-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-450-server/450.102.04-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-450-server (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1915935

Title:
  Switching between NVIDIA drivers fails

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-450 source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-460 source package in Bionic:
  New
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Trying to install nvidia-driver-450-server over nvidia-driver-450
  triggers the following error:

  Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-e75h80/01-libnvidia-common-
  450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.102.04-k
  ey-documentation', which is also in package libnvidia-common-450 
450.102.04-0ubu
  ntu0.20.04.1
  ...
  Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1915552] Re: Fix oops in skb_segment for Bionic series

[Guilherme G. Piccoli]

An user who reported the issue confirmed the kernel with the patches hereby 
proposed is not reproducing anymore; also, I checked in the Bionic git tree, 
patches are indeed there.
Cheers,


Guilherme

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1915552

Title:
  Fix oops in skb_segment for Bionic series

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  * It was reported upstream [0] that an eBPF NAT64 filter caused an oops due 
to bad handling of GRO headers length on SKB segmentation path; the discussion 
is rich in details, and eventually the reporter sent a fix patch for that [1], 
as well as a test scenario in test_bpf kernel module that reproduces the issue.

  [0] 
https://lore.kernel.org/netdev/9265b93f-253d-6b8c-f2b8-4b54eff18...@fb.com/
  [1] https://lore.kernel.org/netdev/20180321233104.2142764-1-...@fb.com/

  * The fix patch landed on v4.17 and for some reason didn't reach the
  stable kernels; by testing our Bionic v4.15 kernel I was able to
  reproduce the issue, observing the following stack trace (details in
  the testing section below):

  kernel BUG at net/core/skbuff.c:3703!
  Modules linked in: test_bpf(E+) isofs nls_iso8859_1 dm_multipath scsi_dh_rdac 
scsi_dh_emc ...
  RIP: 0010:skb_segment+0xa34/0xce0
  [...]
  Call Trace:
   test_bpf_init.part.7+0x767/0x7d1 [test_bpf]
   test_bpf_init+0xfc/0x82f [test_bpf]
   do_one_initcall+0x52/0x19f
  [...]

  * Interesting to mention that this fix is not complete in the sense
  there was another corner case reported after that [2], which was fixed
  by another patch [3], this one released in kernel v5.3 and present in
  the stable tree (hence backported to our Bionic 4.15 kernels).

  [2] https://lore.kernel.org/netdev/20190826170724.25ff616f@pixies/
  [3] http://git.kernel.org/linus/3dcbdb134f32 ("net: gso: Fix skb_segment 
splat when splitting gso_size mangled skb having linear-headed frag_list")

  * So we are hereby backporting both the original fix patch [4] as well
  as the test_bpf patch (and a fix for it) [5] [6] for Ubuntu Bionic
  v4.15-based kernels

  [4] http://git.kernel.org/linus/13acc94eff12 ("net: permit skb_segment on 
head_frag frag_list skb")
  [5] http://git.kernel.org/linus/76db8087c4c9 ("net: bpf: add a test for 
skb_segment in test_bpf module")
  [6] http://git.kernel.org/linus/99fe29d3a25f ("test_bpf: Fix NULL vs IS_ERR() 
check in test_skb_segment()")

  [Test Case]
  * One could use a NAT64 filter, but with the aforementioned patches [5] [6] 
hereby backported, one can also use the kernel infrastructure, by loading the 
test_bpf module:

  insmod /lib/modules/$(uname -r)/kernel/lib/test_bpf.ko

  If patches [5] [6] are included and kernel doesn't contain the fix
  [4], an oops will be observed.

  [Where problems could occur]
  * The backported patches are present upstream since v4.17, and no fixes were 
released for them (other than [6], included here), so from the testing 
point-of-view, these patches are being exercised for a while with no issues.

  * That said, if a problem would be triggered by these patches,
  hypothetically it would affect SKB segmentation, the net/core code - a
  bad check could case an oops in this code or they could present a
  pretty small overhead due to more checks in the hot path.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1914830] Re: Mellanox Patches To Prevent Kernel Hang In MLX4

[Guilherme G. Piccoli]

** Changed in: linux-azure (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Groovy)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1914830

Title:
  Mellanox Patches To Prevent Kernel Hang In MLX4

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure source package in Groovy:
  Fix Committed

Bug description:
  We have had customer reports of kernel hangs related to MLX4.
  Mellanox has addressed the issue with the following two patches:

  fed91613c9dd ("net/mlx4_en: Avoid scheduling restart task if it is already 
running")
  ba603d9d7b12 ("net/mlx4_en: Handle TX error CQE")

  Microsoft would like to request these two commits in all releases
  supported on Azure.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917275] Re: MSI MS-7817 desktop linux kernel 5.4

[Alex Hung]

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

** This bug has been marked a duplicate of bug 1917274
   MSI MS-7817 desktop linux kernel 5.4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917275

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 working
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Piotr Tomaszewski]

Tested Ubuntu 20.04.2/20.10 with all updates. Touchpad not working...
How to make it works?

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(cus

[Kernel-packages] [Bug 1893703] Re: CPU: 2 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260

[Waldmeisda]

Hi,

I had the same issue, what happend is that the network went down and the
server flooded the switch with traffic.

Mar  1 19:51:08 microserver kernel: [76180.035137] [ cut here 
]
Mar  1 19:51:08 microserver kernel: [76180.035142] NETDEV WATCHDOG: eno1 (tg3): 
transmit queue 0 timed out
Mar  1 19:51:08 microserver kernel: [76180.035172] WARNING: CPU: 1 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260
Mar  1 19:51:08 microserver kernel: [76180.035174] Modules linked in: vhost_net 
vhost tap xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle nf_tables nfnetlink ip6table_filter 
ip6_tables aufs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 iptable_filter bpfilter wireguard ip6_udp_tunnel udp_tunnel 
overlay bridge stp llc binfmt_misc intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm mgag200 
crct10dif_pclmul drm_vram_helper ipmi_ssif ghash_clmulni_intel ttm aesni_intel 
crypto_simd drm_kms_helper cryptd glue_helper i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt rapl intel_cstate serio_raw hpilo joydev 
ipmi_si input_leds ipmi_devintf ie31200_edac ipmi_msghandler mac_hid 
acpi_power_meter sch_fq_codel parport_pc drm ppdev lp parport sunrpc ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0
Mar  1 19:51:08 microserver kernel: [76180.035222]  multipath linear 
hid_generic usbhid hid gpio_ich crc32_pclmul lpc_ich psmouse ahci libahci tg3
Mar  1 19:51:08 microserver kernel: [76180.035231] CPU: 1 PID: 0 Comm: 
swapper/1 Not tainted 5.4.0-66-generic #74-Ubuntu
Mar  1 19:51:08 microserver kernel: [76180.035232] Hardware name: HP ProLiant 
MicroServer Gen8, BIOS J06 04/04/2019
Mar  1 19:51:08 microserver kernel: [76180.035235] RIP: 
0010:dev_watchdog+0x258/0x260
Mar  1 19:51:08 microserver kernel: [76180.035238] Code: 85 c0 75 e5 eb 9f 4c 
89 ff c6 05 ae 8f e7 00 01 e8 0d b2 fa ff 44 89 e9 4c 89 fe 48 c7 c7 58 a3 83 
a1 48 89 c2 e8 c3 c3 70 ff <0f> 0b eb 80 0f 1f 40 00 66 66 66 66 90 55 48 89 e5 
41 57 49 89 d7
Mar  1 19:51:08 microserver kernel: [76180.035240] RSP: 0018:b90fc02b0e30 
EFLAGS: 00010286
Mar  1 19:51:08 microserver kernel: [76180.035242] RAX:  RBX: 
8eaa762bf500 RCX: 0006
Mar  1 19:51:08 microserver kernel: [76180.035243] RDX: 0007 RSI: 
0096 RDI: 8eaa7aa578c0
Mar  1 19:51:08 microserver kernel: [76180.035244] RBP: b90fc02b0e60 R08: 
03ea R09: 0004
Mar  1 19:51:08 microserver kernel: [76180.035245] R10:  R11: 
0001 R12: 0005
Mar  1 19:51:08 microserver kernel: [76180.035246] R13:  R14: 
8eaa762ea480 R15: 8eaa762ea000
Mar  1 19:51:08 microserver kernel: [76180.035248] FS:  () 
GS:8eaa7aa4() knlGS:
Mar  1 19:51:08 microserver kernel: [76180.035250] CS:  0010 DS:  ES:  
CR0: 80050033
Mar  1 19:51:08 microserver kernel: [76180.035251] CR2: 0ffe09da5000 CR3: 
0001b1e0a004 CR4: 000626e0
Mar  1 19:51:08 microserver kernel: [76180.035252] Call Trace:
Mar  1 19:51:08 microserver kernel: [76180.035255]  
Mar  1 19:51:08 microserver kernel: [76180.035259]  ? 
pfifo_fast_enqueue+0x150/0x150
Mar  1 19:51:08 microserver kernel: [76180.035264]  call_timer_fn+0x32/0x130
Mar  1 19:51:08 microserver kernel: [76180.035267]  
__run_timers.part.0+0x180/0x280
Mar  1 19:51:08 microserver kernel: [76180.035270]  ? timerqueue_add+0x68/0xb0
Mar  1 19:51:08 microserver kernel: [76180.035272]  ? enqueue_hrtimer+0x3d/0x90
Mar  1 19:51:08 microserver kernel: [76180.035277]  ? 
recalibrate_cpu_khz+0x10/0x10
Mar  1 19:51:08 microserver kernel: [76180.035279]  ? ktime_get+0x3e/0xa0
Mar  1 19:51:08 microserver kernel: [76180.035282]  run_timer_softirq+0x2a/0x50
Mar  1 19:51:08 microserver kernel: [76180.035285]  __do_softirq+0xe1/0x2d6
Mar  1 19:51:08 microserver kernel: [76180.035288]  ? 
hrtimer_interrupt+0x13b/0x220
Mar  1 19:51:08 microserver kernel: [76180.035291]  irq_exit+0xae/0xb0
Mar  1 19:51:08 microserver kernel: [76180.035293]  
smp_apic_timer_interrupt+0x7b/0x140
Mar  1 19:51:08 microserver kernel: [76180.035296]  
apic_timer_interrupt+0xf/0x20
Mar  1 19:51:08 microserver kernel: [76180.035297]  
Mar  1 19:51:08 microserver kernel: [76180.035301] RIP: 
0010:cpuidle_enter_state+0xc2/0x450
Mar  1 19:51:08 microserver kernel: [76180.035303] Code: 66 90 31 ff e8 ff aa 
80 ff 80 7d c7 00 74 17 9c 58 66 66 90 66 90 f6 c4 02 0f 85 65 03 00 00 31 ff 
e8 e2 16 87 ff fb 66 66 90 <66> 66 90 45 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 
7d d0 4c 2b 7d
Mar  1 19:51:08 microserver kernel: [76180.035304] RSP: 0018:b90fc0083e38 
EFLAGS: 0246 ORIG_RAX: ff13
Mar  1 19:51:08 microserver kernel: [76180.03530

[Kernel-packages] [Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[Alex Hung]

Suravee's patch (commit 6778ff5b21bd8e78) is now in mainline kernel. It
is more appropriate to backport it to Ubuntu kernels.

Let's wait for hirsute to rebase to 5.11 and send a SRU.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This boot warning (concealed by grub not taking over the fbcon console
  on a solo installation but always present on a multi-boot) has been
  bothering Linux users of AMD Ryzen machines for some time.

  The problem is currently under discussion at kernel level
  .

  One solution proposed by Suravee Suthikulpanit

  works but inserts a boot-up delay of (at least) 100 msec. A second
  option by Alexander Monakov 
   also works but
  inserts no delay and more-or-less just moves one line of code.

  I've tried both solutions with kernel rebuilds for both Breezy kernel
  5.8.18 and Hirsute kernel 5.10.11 and both work on my AMD Ryzen 2400G.
  Could I encourage your kernel experts to evaluate the situation (I
  think SuSE folk already are).

  My suggestion (as a humble user :-) ) would be to fold Alex's simple
  patch into your own list of kernel tweeks and get the correction out
  with the upcoming Hirsute release.

  Best regards and all respect!

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917164] Re: ubuntu 20.04 LTS and ubuntu 20.10 linux kernel 5.8 problems

[Alex Hung]

Please be specific on what problems you have.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917164

Title:
  ubuntu 20.04 LTS and ubuntu 20.10 linux kernel 5.8 problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 0b)
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 0b)
  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 0b)
  00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC 
[8086:9c31] (rev 04)
  00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 
[8086:9c3a] (rev 04)
  00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller 
[8086:9c20] (rev 04)
  00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 1 
[8086:9c10] (rev e4)
  00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 2 
[8086:9c12] (rev e4)
  00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 3 
[8086:9c14] (rev e4)
  00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 
[8086:9c16] (rev e4)
  00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 
[8086:9c26] (rev 04)
  00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller 
[8086:9c43] (rev 04)
  00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 
[AHCI mode] [8086:9c03] (rev 04)
  00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] 
(rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader [10ec:5229] (rev 01)
  08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
  09:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43142 
802.11b/g/n [14e4:4365] (rev 01)

  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:08:00.0
     logical name: enp8s0
     version: 10
     serial: f0:76:1c:67:6e:c6
     capacity: 1Gbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp mii 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168g-3_0.0.1 04/23/13 latency=0 link=no multicast=yes port=MII
     resources: irq:18 ioport:3000(size=256) memory:b2504000-b2504fff 
memory:b250-b2503fff
    *-network UNCLAIMED
     description: Network controller
     product: BCM43142 802.11b/g/n
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:09:00.0
     version: 01
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list
     configuration: latency=0
     resources: memory:b240-b2407fff
    *-network
     description: Wireless interface
     physical id: 1
     bus info: usb@2:3
     logical name: wlx0023cdb814f3
     serial: 00:23:cd:b8:14:f3
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=carl9170 
driverversion=5.4.0-60-generic firmware=1.9.6 ip=192.168.8.109 link=yes 
multicast=yes wireless=IEEE 802.11
  WARNING: output may be incomplete or inaccurate, you should run this program 
as super-user.

  linux-firmware/focal-updates,focal-updates 1.187.7 all versio: 1.187.2]
  linux-generic-hwe-20.04/focal-updates,focal-security 5.8.0.36.40~20.04.21 
amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-generic/focal-updates,focal-security 5.4.0.60.63 amd64 [päivitettävissä 
versiosta: 5.4.0.42.46]
  linux-headers-generic-hwe-20.04/focal-updates,focal-security 
5.8.0.36.40~20.04.21 amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-headers-generic/focal-updates,focal-security 5.4.0.60.63 amd64 
[päivitettävissä versiosta: 5.4.0.42.46]
  linux-image-generic-hwe-20.04/focal-updates,focal-security 
5.8.0.36.40~20.04.21 amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-image-generic/focal-updates,focal-security 5.4.0.60.63 amd64 
[päivitettävissä versiosta: 5.4.0.42.46]
  linux-libc-dev/focal-updates,focal-security 5.4.0-60.67 amd64 
[päivitettävissä versiosta: 5.4.0-42.46]
  util-linux/focal-updates 2.34-0.1ubuntu9.1 amd64
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1418 F pu

[Kernel-packages] [Bug 1917138] Re: kernel 4.15.0-136 causes dosemu2 with kvm freezes

[Guilherme G. Piccoli]

Thanks for the report! Are you using nested virtualization (a virtual machine 
inside another virtual machine) or you run dosbox directly in your 
host/bare-metal system?
Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138

Title:
  kernel 4.15.0-136 causes dosemu2 with kvm freezes

Status in Dosemu2:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
  16.04, dosemu2 with kvm  freezes boot.

  dosemu2 source: https://github.com/dosemu2/dosemu2

  dosemu2 package can be obtained from
  https://launchpad.net/~dosemu2/+archive/ubuntu/ppa

  1. ubuntu version
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2. package version
  $ apt-cache policy dosemu2
  dosemu2:
Installed: (none)
Candidate: (none)
Version table:
   2.0~pre8-2 -1
  100 /var/lib/dpkg/status

  3. What is expected to happen: The dosemu program runs fine as in previous 
kernel version
  4. What happened instead: The dosemu freezes on loading

  I have also reported this problem to dosemu2 developer, here is my bug report:
  https://github.com/dosemu2/dosemu2/issues/1404

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Full name]

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

Can't switch to HSP profile with my Aftershokz.  Says: "Failed to change
profile to headset_head_unit"

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Helmut Stult]

https://linux-hardware.org/?probe=ea049102ec

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR

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

[Helmut Stult]

This is the working kernel 5.11

https://linux-hardware.org/?probe=fbcb409c56

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

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

[Helmut Stult]

@Coiby Xu (coiby)

My touchpad MSFT0001:00 04F3:3140 works fine with Kernel 5.11, but stops 
working with the new 5.12-rc1
So far I haven't found the cause.

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineTyp

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Adrian Wilkins]

Been running -460 for ages, my syslog occupies 80GB of disk space and
out of 526M log lines, 99.996% of them mention "Nautilus".

** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1846374

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[Alex Hung]

@david,

I cherry-picked 6778ff5b21bd8e78 and built a test kernel @
https://people.canonical.com/~alexhung/LP1917203/. I tested on an AMD
Ryzen 5 2500U

Before
[0.975812] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.

After:
[1.006639] pci :00:00.2: AMD-Vi: IOMMU performance counters supported

It would be great if you can give it a try and update the results.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This boot warning (concealed by grub not taking over the fbcon console
  on a solo installation but always present on a multi-boot) has been
  bothering Linux users of AMD Ryzen machines for some time.

  The problem is currently under discussion at kernel level
  .

  One solution proposed by Suravee Suthikulpanit

  works but inserts a boot-up delay of (at least) 100 msec. A second
  option by Alexander Monakov 
   also works but
  inserts no delay and more-or-less just moves one line of code.

  I've tried both solutions with kernel rebuilds for both Breezy kernel
  5.8.18 and Hirsute kernel 5.10.11 and both work on my AMD Ryzen 2400G.
  Could I encourage your kernel experts to evaluate the situation (I
  think SuSE folk already are).

  My suggestion (as a humble user :-) ) would be to fold Alex's simple
  patch into your own list of kernel tweeks and get the correction out
  with the upcoming Hirsute release.

  Best regards and all respect!

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917138] Re: kernel 4.15.0-136 causes dosemu2 with kvm freezes

[Guilherme G. Piccoli]

Thanks again Bambang and Hans-Christian for the report, it seems indeed
a bug in the kernel. I think I know what's going on, but I'd like to ask
you to perform some testing in order we can prove that, and then fix it.

So, first it'll be 2 tests - depending on the result, a third test will be 
necessary.
Please be sure to try both (1) and (2) with dos2emu using the KVM mode:

(1) For the first test, please get the Bionic proposed kernel (see [0]
for information on how to do it) - the current proposed version is
4.15.0-137. Try to reproduce with that version - I expect it to
reproduce.

(2) Now, get the build I made for you in 
https://kernel.ubuntu.com/~gpiccoli/lp1917138/ - observe that if you have the 
"linux-modules-extra" and "linux-headers" already installed on your system 
after test (1), please also install them from my build or else you might have 
issues in the boot process. To install the packages, download them from the 
link above to some directory and then run "dpkg -i *.deb" (supposing no other 
.deb file is present in that directory).
Reboot the system after a successful installation and try to reproduce the 
issue - I suspect it won't reproduce, dosemu2 should work fine even in KVM mode.

Thanks in advance,


Guilherme


[0] https://wiki.ubuntu.com/Testing/EnableProposed
(don't forget to disable the proposed repository after your tests)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138

Title:
  kernel 4.15.0-136 causes dosemu2 with kvm freezes

Status in Dosemu2:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
  16.04, dosemu2 with kvm  freezes boot.

  dosemu2 source: https://github.com/dosemu2/dosemu2

  dosemu2 package can be obtained from
  https://launchpad.net/~dosemu2/+archive/ubuntu/ppa

  1. ubuntu version
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2. package version
  $ apt-cache policy dosemu2
  dosemu2:
Installed: (none)
Candidate: (none)
Version table:
   2.0~pre8-2 -1
  100 /var/lib/dpkg/status

  3. What is expected to happen: The dosemu program runs fine as in previous 
kernel version
  4. What happened instead: The dosemu freezes on loading

  I have also reported this problem to dosemu2 developer, here is my bug report:
  https://github.com/dosemu2/dosemu2/issues/1404

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Wes Newell]

last kernel upgrade to 5.4.0-66 is still broken.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap
  in /etc/rc_keymaps to correctly map buttons on my IR remote.  The
  above kernel seems to break custom keymap loading for my remote
  (certain buttons no longer work in mythtv).  Reverting to kernel
  5.4.0-48 corrects the problem.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  linux-image-5.4.0-52-generic:
Installed: 5.4.0-52.57
Candidate: 5.4.0-52.57
Version table:
   *** 5.4.0-52.57 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  belongs to the linux source package

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pdaniel1552 F pulseaudio
   /dev/snd/controlC0:  pdaniel1552 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Oct 22 16:16:58 2020
  InstallationDate: Installed on 2017-04-17 (1284 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7792
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (164 days ago)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FM2-A75IA-E53 (MS-7792)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7792
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917093] Re: Bionic update: upstream stable patchset 2021-02-26

[Kelsey Skunberg]

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917093

Title:
  Bionic update: upstream stable patchset 2021-02-26

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2021-02-26

  Ported from the following upstream stable releases:
  v4.14.218, v4.19.171
 v4.19.172

     from git://git.kernel.org/

  i2c: bpmp-tegra: Ignore unknown I2C_M flags
  ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
  ALSA: hda/via: Add minimum mute flag
  ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
  mmc: sdhci-xenon: fix 1.8v regulator stabilization
  dm: avoid filesystem lookup in dm_get_dev_t()
  drm/atomic: put state on error path
  ASoC: Intel: haswell: Add missing pm_ops
  scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
  xen: Fix event channel callback via INTX/GSI
  drm/nouveau/bios: fix issue shadowing expansion ROMs
  drm/nouveau/privring: ack interrupts the same way as RM
  drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
  i2c: octeon: check correct size of maximum RECV_LEN packet
  can: dev: can_restart: fix use after free bug
  can: vxcan: vxcan_xmit: fix use after free bug
  iio: ad5504: Fix setting power-down state
  irqchip/mips-cpu: Set IPI domain parent chip
  intel_th: pci: Add Alder Lake-P support
  stm class: Fix module init return on allocation failure
  ehci: fix EHCI host controller initialization sequence
  USB: ehci: fix an interrupt calltrace error
  usb: udc: core: Use lock when write to soft_connect
  usb: bdc: Make bdc pci driver depend on BROKEN
  UBUNTU: [Config] updateconfigs for USB_BDC_PCI
  xhci: make sure TRB is fully written before giving it to the controller
  xhci: tegra: Delay for disabling LFPS detector
  compiler.h: Raise minimum version of GCC to 5.1 for arm64
  netfilter: rpfilter: mask ecn bits before fib lookup
  sh: dma: fix kconfig dependency for G2_DMA
  sh_eth: Fix power down vs. is_opened flag ordering
  skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
  udp: mask TOS bits in udp_v4_early_demux()
  ipv6: create multicast route with RTPROT_KERNEL
  net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
  net: dsa: b53: fix an off by one in checking "vlan->vid"
  gpio: mvebu: fix pwm .get_state period calculation
  Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
  futex: Ensure the correct return value from futex_lock_pi()
  futex: Replace pointless printk in fixup_owner()
  futex: Provide and use pi_state_update_owner()
  rtmutex: Remove unused argument from rt_mutex_proxy_unlock()
  futex: Use pi_state_update_owner() in put_pi_state()
  futex: Simplify fixup_pi_state_owner()
  futex: Handle faults correctly for PI futexes
  tracing: Fix race in trace_open and buffer resize call
  fs: move I_DIRTY_INODE to fs.h
  writeback: Drop I_DIRTY_TIME_EXPIRE
  fs: fix lazytime expiration handling in __writeback_single_inode()
  mmc: core: don't initialize block size from ext_csd if not present
  scsi: qedi: Correct max length of CHAP secret
  riscv: Fix kernel time_init()
  HID: Ignore battery for Elan touchscreen on ASUS UX550
  clk: tegra30: Add hda clock default rates to clock driver
  drm/nouveau/mmu: fix vram heap sizing
  scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression
  can: peak_usb: fix use after free bugs
  serial: mvebu-uart: fix tx lost characters at power off
  driver core: Extend device_is_dependent()
  net_sched: reject silly cell_log in qdisc_get_rtab()
  tools: Factor HOSTCC, HOSTLD, HOSTAR definitions
  UBUNTU: upstream stable to v4.14.218, v4.19.172

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1916731] Re: [SRU][F/G/H] add AMD GPU green sardine firmware

[AaronMa]

** No longer affects: linux-firmware (Ubuntu Groovy)

** Summary changed:

- [SRU][F/G/H] add AMD GPU green sardine firmware
+ [SRU][F/H] add AMD GPU green sardine firmware

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1916731

Title:
  [SRU][F/H] add AMD GPU green sardine firmware

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Hirsute:
  New

Bug description:
  SRU justification:

  [Impact]
  AMD new gpu can not work without proper firmware.

  [Fix]
  Add new firmwares of AMD GPU green sardine.
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.

  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.

  [Where problems could occur]
  Introducs the new firmware to enable support on new GPU.
  GFX can be failed if it is wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1916731/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

[Kai Mast]

I still experience this on 21.04 unfortunately. It might be a different
bug though.

For me now, it mostly happens when suspending the laptop while connected
to the Dock. After resuming I get constant resets...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766076

Title:
  USB over thunderbolt turns off every once in a while

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

   
  [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus 
number 3
 
  [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 
0x100 quirks 0x1410 

  [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 

   
  [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1  
 
  [279389.949982] usb usb3: Product: xHCI Host Controller   

   
  [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd  

   
  [279389.949983] usb usb3: SerialNumber

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

[Helmut Stult]

https://linux-hardware.org/?probe=8d8e17d95e

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR

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

[Helmut Stult]

Works again - have to set CONFIG_I2C_HID_ACPI=m in config

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=

[Kernel-packages] [Bug 1916573] Re: display can not wake up from sleeping.

[Kai-Heng Feng]

Please follow #2 and upload log, thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1916573

Title:
  display can not wake up from sleeping.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  os system: ubuntu 20.04.2 LTS

  when I press the keyboard, I saw new log from ssh terminal.

  /var/log/kern.log

  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.303887] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.307888] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.346636] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.350790] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1914411] Re: Fix broken efifb on graphics device without driver

[Kai-Heng Feng]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914411

Title:
  Fix broken efifb on graphics device without driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  New

Bug description:
  [Impact]
  EFIFB stops working after graphics device is runtime suspended in
  D3cold.

  [Fix]
  Prevent the graphics device from being runtime suspended.

  [Test]
  With the patch applied, using efifb on graphics device without driver
  always work, because the device stays at D0 all the time.

  [Where problems could occur]
  Potentially this can affect power consumption, if user expects to put
  graphics device to D3cold, and is fine to get a broken efifb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1914604] Re: Add support for new Realtek ethernet NIC

[Kai-Heng Feng]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914604

Title:
   Add support for new Realtek ethernet NIC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  New Realtek ethernet NIC doesn't work.

  [Fix]
  Add support for new Realtek NIC.

  [Test]
  With the patch applied, network interface is created, and can reach 1G
  speed.

  [Where problems could occur]
  This patch doesn't bring any functional change, and it doesn't touch any
  older hardwares. So there's no chance to bring regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1914604/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917164] Re: ubuntu 20.04 LTS and ubuntu 20.10 linux kernel 5.8 problems

[sessetessu2021]

linux kernels 5.8 jammed and freeze MSI MS 7817 desktop


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => sessetessu2021 (sessetessu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917164

Title:
  ubuntu 20.04 LTS and ubuntu 20.10 linux kernel 5.8 problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 0b)
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 0b)
  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 0b)
  00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC 
[8086:9c31] (rev 04)
  00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 
[8086:9c3a] (rev 04)
  00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller 
[8086:9c20] (rev 04)
  00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 1 
[8086:9c10] (rev e4)
  00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 2 
[8086:9c12] (rev e4)
  00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 3 
[8086:9c14] (rev e4)
  00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 
[8086:9c16] (rev e4)
  00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 
[8086:9c26] (rev 04)
  00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller 
[8086:9c43] (rev 04)
  00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 
[AHCI mode] [8086:9c03] (rev 04)
  00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] 
(rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader [10ec:5229] (rev 01)
  08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
  09:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43142 
802.11b/g/n [14e4:4365] (rev 01)

  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:08:00.0
     logical name: enp8s0
     version: 10
     serial: f0:76:1c:67:6e:c6
     capacity: 1Gbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp mii 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168g-3_0.0.1 04/23/13 latency=0 link=no multicast=yes port=MII
     resources: irq:18 ioport:3000(size=256) memory:b2504000-b2504fff 
memory:b250-b2503fff
    *-network UNCLAIMED
     description: Network controller
     product: BCM43142 802.11b/g/n
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:09:00.0
     version: 01
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list
     configuration: latency=0
     resources: memory:b240-b2407fff
    *-network
     description: Wireless interface
     physical id: 1
     bus info: usb@2:3
     logical name: wlx0023cdb814f3
     serial: 00:23:cd:b8:14:f3
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=carl9170 
driverversion=5.4.0-60-generic firmware=1.9.6 ip=192.168.8.109 link=yes 
multicast=yes wireless=IEEE 802.11
  WARNING: output may be incomplete or inaccurate, you should run this program 
as super-user.

  linux-firmware/focal-updates,focal-updates 1.187.7 all versio: 1.187.2]
  linux-generic-hwe-20.04/focal-updates,focal-security 5.8.0.36.40~20.04.21 
amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-generic/focal-updates,focal-security 5.4.0.60.63 amd64 [päivitettävissä 
versiosta: 5.4.0.42.46]
  linux-headers-generic-hwe-20.04/focal-updates,focal-security 
5.8.0.36.40~20.04.21 amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-headers-generic/focal-updates,focal-security 5.4.0.60.63 amd64 
[päivitettävissä versiosta: 5.4.0.42.46]
  linux-image-generic-hwe-20.04/focal-updates,focal-security 
5.8.0.36.40~20.04.21 amd64 [päivitettävissä versiosta: 5.4.0.42.46]
  linux-image-generic/focal-updates,focal-security 5.4.0.60.63 amd64 
[päivitettävissä versiosta: 5.4.0.42.46]
  linux-libc-dev/focal-updates,focal-security 5.4.0-60.67 amd64 
[päivitettävissä versiosta: 5.4.0-42.46]
  util-linux/focal-updates 2.34-0.1ubuntu9.1 amd64
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  

Re: [Kernel-packages] [Bug 1917138] Re: kernel 4.15.0-136 causes dosemu2 with kvm freezes

[Bambang Pranoto]

Dear Guilherme,

Thank you very much for your reply.

On Tue, Mar 2, 2021 at 3:00 AM Guilherme G. Piccoli <
1917...@bugs.launchpad.net> wrote:

> Thanks for the report! Are you using nested virtualization (a virtual
> machine inside another virtual machine) or you run dosbox directly in your
> host/bare-metal system?
>
>
I run it directly on the real hardware/bare-metal system.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138

Title:
  kernel 4.15.0-136 causes dosemu2 with kvm freezes

Status in Dosemu2:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
  16.04, dosemu2 with kvm  freezes boot.

  dosemu2 source: https://github.com/dosemu2/dosemu2

  dosemu2 package can be obtained from
  https://launchpad.net/~dosemu2/+archive/ubuntu/ppa

  1. ubuntu version
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2. package version
  $ apt-cache policy dosemu2
  dosemu2:
Installed: (none)
Candidate: (none)
Version table:
   2.0~pre8-2 -1
  100 /var/lib/dpkg/status

  3. What is expected to happen: The dosemu program runs fine as in previous 
kernel version
  4. What happened instead: The dosemu freezes on loading

  I have also reported this problem to dosemu2 developer, here is my bug report:
  https://github.com/dosemu2/dosemu2/issues/1404

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1917138] Re: kernel 4.15.0-136 causes dosemu2 with kvm freezes

[Bambang Pranoto]

Dear Guilherme,

I will try and come back to you later.

Thanks again.

On Tue, Mar 2, 2021 at 4:56 AM Guilherme G. Piccoli <
1917...@bugs.launchpad.net> wrote:

> Thanks again Bambang and Hans-Christian for the report, it seems indeed
> a bug in the kernel. I think I know what's going on, but I'd like to ask
> you to perform some testing in order we can prove that, and then fix it.
>
> So, first it'll be 2 tests - depending on the result, a third test will be
> necessary.
> Please be sure to try both (1) and (2) with dos2emu using the KVM mode:
>
> (1) For the first test, please get the Bionic proposed kernel (see [0]
> for information on how to do it) - the current proposed version is
> 4.15.0-137. Try to reproduce with that version - I expect it to
> reproduce.
>
> (2) Now, get the build I made for you in
> https://kernel.ubuntu.com/~gpiccoli/lp1917138/ - observe that if you have
> the "linux-modules-extra" and "linux-headers" already installed on your
> system after test (1), please also install them from my build or else you
> might have issues in the boot process. To install the packages, download
> them from the link above to some directory and then run "dpkg -i *.deb"
> (supposing no other .deb file is present in that directory).
> Reboot the system after a successful installation and try to reproduce the
> issue - I suspect it won't reproduce, dosemu2 should work fine even in KVM
> mode.
>
> Thanks in advance,
>
>
> Guilherme
>
>
> [0] https://wiki.ubuntu.com/Testing/EnableProposed
> (don't forget to disable the proposed repository after your tests)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1917138
>
> Title:
>   kernel 4.15.0-136 causes dosemu2 with kvm freezes
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dosemu2/+bug/1917138/+subscriptions
>


-- 
Bambang P
http://bpranoto.blogspot.com

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138

Title:
  kernel 4.15.0-136 causes dosemu2 with kvm freezes

Status in Dosemu2:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
  16.04, dosemu2 with kvm  freezes boot.

  dosemu2 source: https://github.com/dosemu2/dosemu2

  dosemu2 package can be obtained from
  https://launchpad.net/~dosemu2/+archive/ubuntu/ppa

  1. ubuntu version
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2. package version
  $ apt-cache policy dosemu2
  dosemu2:
Installed: (none)
Candidate: (none)
Version table:
   2.0~pre8-2 -1
  100 /var/lib/dpkg/status

  3. What is expected to happen: The dosemu program runs fine as in previous 
kernel version
  4. What happened instead: The dosemu freezes on loading

  I have also reported this problem to dosemu2 developer, here is my bug report:
  https://github.com/dosemu2/dosemu2/issues/1404

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1917274] Re: MSI MS-7817 desktop linux kernel 5.4

[sessetessu2021]

apport information

** Description changed:

  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  snowden1427 F pulseaudio
+  /dev/snd/controlC0:  snowden1427 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-02-15 (14 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp2s0no wireless extensions.
+ MachineType: MSI MS-7817
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fi_FI.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-66-generic N/A
+  linux-backports-modules-5.4.0-66-generic  N/A
+  linux-firmware1.187.9
+ RfKill:
+  
+ Tags:  focal
+ Uname: Linux 5.4.0-66-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/21/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: V10.9
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: B85M-E45 (MS-7817)
+ dmi.board.vendor: MSI
+ dmi.board.version: 2.0
+ dmi.chassis.asset.tag: To be filled by O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: MSI
+ dmi.chassis.version: 2.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: MS-7817
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: 2.0
+ dmi.sys.vendor: MSI

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUs

[Kernel-packages] [Bug 1917274] Lspci.txt

[sessetessu2021]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1917274/+attachment/5471638/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/

[Kernel-packages] [Bug 1917274] Lspci-vt.txt

[sessetessu2021]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1917274/+attachment/5471639/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchp

[Kernel-packages] [Bug 1917274] CurrentDmesg.txt

[sessetessu2021]

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help

[Kernel-packages] [Bug 1917274] Lsusb-v.txt

[sessetessu2021]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1917274/+attachment/5471642/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad

[Kernel-packages] [Bug 1917274] CRDA.txt

[sessetessu2021]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1917274/+attachment/5471636/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/Li

[Kernel-packages] [Bug 1917274] ProcCpuinfoMinimal.txt

[sessetessu2021]

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1917274] PulseList.txt

[sessetessu2021]

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launc

[Kernel-packages] [Bug 1917274] UdevDb.txt

[sessetessu2021]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1917274/+attachment/5471648/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.ne

[Kernel-packages] [Bug 1917274] acpidump.txt

[sessetessu2021]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1917274/+attachment/5471650/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchp

[Kernel-packages] [Bug 1917274] Lsusb.txt

[sessetessu2021]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1917274/+attachment/5471640/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917274

Title:
  MSI MS-7817 desktop linux kernel 5.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MSI MS-7817 desktop linux kernel 5.4 is working 
  MSI MS 7817 desktop is linux kernels 5.4 
  installed is working linux kernel 5.4 working
  linux ubuntu 20.04 LTS MSI MS-7817 desktop
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1427 F pulseaudio
   /dev/snd/controlC0:  snowden1427 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/