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

2020-09-26 Thread wangjun
@Coiby Xu (coiby)

my machine is MSFT0001:00 04F3:3140;

i tested the patch on fedora 32 kernel 5.8.11 .

the touchpad worked.

but the original patch not compile :

thread_hid  undeclared

then i add one line:

static struct task_struct *thread_hid = NULL;


many thanks to your hard work!

i am in in expectation of your final version patch.

-- 
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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 

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

2020-09-26 Thread wangjun
sorry for my poor english!

非常感谢!

-- 
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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  

[Kernel-packages] [Bug 1888059] Re: Touchpad hp pavilion 15-ec0457ng

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888059

Title:
  Touchpad hp pavilion 15-ec0457ng

Status in linux package in Ubuntu:
  Expired

Bug description:
  : Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name="ETPS/2 Elantech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input6
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  I: Bus=0019 Vendor= Product= Version=
  N: Name="HP Wireless hotkeys"
  P: Phys=hpq6001/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=rfkill kbd event8 
  B: PROP=0
  B: EV=3
  B: KEY=80 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="ST LIS3LV02DL Accelerometer"
  P: Phys=lis3lv02d/input0
  S: Sysfs=/devices/platform/lis3lv02d/input/input11
  U: Uniq=
  H: Handlers=event9 js0 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="HP WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input12
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=33
  B: KEY=40 0 10007 2102400 0 0
  B: MSC=10
  B: SW=22

  I: Bus=0003 Vendor=0408 Product=5365 Version=0002
  N: Name="HP TrueVision HD Camera: HP Tru"
  P: Phys=usb-:05:00.4-1/button
  S: 
Sysfs=/devices/pci:00/:00:08.1/:05:00.4/usb5/5-1/5-1:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0018 Vendor=04f3 Product=30fd Version=0100
  N: Name="ELAN0718:01 04F3:30FD Mouse"
  P: Phys=i2c-ELAN0718:01
  S: 
Sysfs=/devices/platform/AMDI0010:01/i2c-0/i2c-ELAN0718:01/0018:04F3:30FD.0001/input/input14
  U: Uniq=
  H: Handlers=mouse1 event10 
  B: PROP=0
  B: EV=17
  B: KEY=3 0 0 0 0
  B: REL=3
  B: MSC=10

  I: Bus=0018 Vendor=04f3 Product=30fd Version=0100
  N: Name="ELAN0718:01 04F3:30FD Touchpad"
  P: Phys=i2c-ELAN0718:01
  S: 
Sysfs=/devices/platform/AMDI0010:01/i2c-0/i2c-ELAN0718:01/0018:04F3:30FD.0001/input/input16
  U: Uniq=
  H: Handlers=mouse2 event11 
  B: PROP=5
  B: EV=1b
  B: KEY=e520 1 0 0 0 0
  B: ABS=2e08003
  B: MSC=20

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.1/:05:00.6/sound/card1/input17
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.1/:05:00.6/sound/card1/input18
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.1/:01:00.1/sound/card0/input19
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: SW=140

  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  

[Kernel-packages] [Bug 1888068] Re: kernel tried to execute NX-protected page - exploit attempt

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888068

Title:
  kernel tried to execute NX-protected page - exploit attempt

Status in linux package in Ubuntu:
  Expired

Bug description:
  On ubuntu 20.04 I have been plagued by soft/hard lockups on my ryzen 5 3600 
for a while now.
  This one is a new error however that led to a series of soft/hard lockups. 
See attached log.

  using kernel: 
  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2590 F pulseaudio
   /dev/snd/controlC0:  martin 2590 F pulseaudio
   /dev/snd/controlC2:  martin 2590 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-12-08 (224 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash idle=nomwait 
processor.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (86 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888068/+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 1888034] Re: Trackpad stops working

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888034

Title:
  Trackpad stops working

Status in linux package in Ubuntu:
  Expired

Bug description:
  I left my computer idle when I went to sleep, and the next morning the
  mouse trackpad stopped working. This is not the first time the bug has
  happened. It usually happens when my computer has been left idle for a
  long time.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadav  1560 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 18 10:22:01 2020
  InstallationDate: Installed on 2020-07-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Vostro 3559
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=3727f494-6348-4f0e-9846-66e72d6ffc76 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 047TR1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/02/2015:svnDellInc.:pnVostro3559:pvr:rvnDellInc.:rn047TR1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3559
  dmi.product.sku: 06C2
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888034/+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 1888648] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1a3b:2231] network-manager crashes: "NetworkManager needs to be running"

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888648

Title:
  Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1a3b:2231] network-
  manager crashes: "NetworkManager needs to be running"

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi. Sometimes network-manager crashes and I can't connect to any
  network. Restarting the network manager service via terminal hangs and
  even restarting the OS hangs and I have to force shutdown via power
  button.

  When I open settings > Wi-Fi it says: "Oops, something has gone wrong.
  Please contact your software vendor. NetworkManager needs to be
  running".

  I'm not facing the problem right now as I just restarted my laptop so
  if there's any information that I need to gather while this problem is
  happening, let me know. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 14:07:57 2020
  InstallationDate: Installed on 2020-06-20 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.36 metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION CON-UUID  
CON-PATH   
   wlp2s0  wifi  connected limited   limited   
/org/freedesktop/NetworkManager/Devices/2  neverlookaway  
7b44595b-b6bc-4add-9873-a7af7393c65d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp2s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  -- --
-- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  -- --
--
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.22.10  connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888648/+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 1888116] Re: kernel 5.4.0-42-generic looping amdgpu errors

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888116

Title:
  kernel 5.4.0-42-generic looping amdgpu errors

Status in linux package in Ubuntu:
  Expired

Bug description:
  After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
  several hundred system-log similar entires per minute are thrown at
  log:

  kernelamdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 
ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
  kernelamdgpu :09:00.0: amdgpu:   in page starting at address 
0xfffba000 from client 18
  kernelamdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
  kernelamdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf
  kernelamdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0
  kernelamdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5
  kernelamdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: RW: 0x1

  System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu
  with opencl installed (via amdgpu-
  pro-20.20-1089974-ubuntu-20.04.tar.xz from amd.com)

  Nevertheless no system freezes or graphic bugs happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888116/+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 1888151] Re: Touchpad not detected in Obsidian N141ZU

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888151

Title:
  Touchpad not detected in Obsidian N141ZU

Status in linux package in Ubuntu:
  Expired

Bug description:
  Touchpad not detected in Obsidian N141ZU after fresh install of Ubuntu 20.04.
  Touchpad does not show up in /proc/bus/input/devices (file attached).
  USB Mouse works correctly.

  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
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  riccardo   1454 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 19 21:29:26 2020
  InstallationDate: Installed on 2020-07-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: OBSIDIAN-PC N13_N140ZU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=bfa60060-8b72-4cea-a496-e88f2b99bdb7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N13_N140ZU
  dmi.board.vendor: OBSIDIAN-PC
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OBSIDIAN-PC
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd12/21/2018:svnOBSIDIAN-PC:pnN13_N140ZU:pvrNotApplicable:rvnOBSIDIAN-PC:rnN13_N140ZU:rvrNotApplicable:cvnOBSIDIAN-PC:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N13_N140ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: OBSIDIAN-PC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888151/+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 1888324] Re: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE)

2020-09-26 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1888324

Title:
  Kernel oops in kvm host if using vhost_net in guest (18.04 HWE)

Status in linux package in Ubuntu:
  Expired

Bug description:
  If I run a KVM guest with a network using the vhost_net driver, I get a 
kernel oops with a NULL reference error. It happens randomly. I run a GPU 
passthrough setup with windows 10 but I can leave that up 24/7 as I am passing 
through a raw ethernet card. Any other virtual machine using the vhost_net 
driver will result in a crash in 12 hours or less. I've attached the dmesg that 
I captured with kdump. I am not sure when this bug was introduced.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   3876 F pulseaudio
   /dev/snd/controlC1:  luke   3876 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-10-30 (629 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on 
kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 
kvm.allow_unsafe_assigned_interrupts=1 
vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G 
crashkernel=768M
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.70
  dmi.board.name: X399 Professional Gaming
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+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 1897392] Re: Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

2020-09-26 Thread Daniel Letzeisen
Please update to latest BIOS and see if the errors persist.

-- 
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/1897392

Title:
  Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lenovo IdeaPad S540, 13-ARE
  AMD Ryzen 4800U, 16GB dual channel RAM, 13.3" 2560x1600 screen. 
  Note this laptop is a lot like the Lenovo Slim 7, it seems this laptop UEFI 
Bios does advertise S3 sleep, the Slim 7 only advertises S2idle. 

  The errors are related to AMD Ryzen 4000 series.

  Clean (no dual boot) Ubuntu Budgie 20.04.1 with kernel upgraded to
  5.8.11.

  Full dmesg: https://pastebin.com/nFbHB22d
  Journalclt after boot: https://pastebin.com/bcpw8Vhc

  erros only from dmesg:
  $ sudo dmesg -l err
  [2.686094] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
  [4.818164] I2C multi instantiate pseudo device driver INT3515:00: IRQ 
index 1 not found
  [4.836122] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0
  [4.971650] ACPI Error: No handler for Region [ECSI] (e6d23662) 
[EmbeddedControl] (20200528/evregion-127)
  [4.971933] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20200528/exfldio-261)
  [4.972172] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.972447] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.972736] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
  [5.871695] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) 
failed: -517
  [6.127547] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.128334] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.128558] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.938706] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed 
to add display topology, DTM TA is not initialized.

  $ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal
  Linux Idefix 5.8.11-050811-generic #202009230858 SMP Wed Sep 23 13:06:55 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897392/+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 1897392] Re: Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

2020-09-26 Thread Daniel Letzeisen
A lot of these errors sound like BIOS issues. For example,  "AMD-Vi:
Unable to read/write to IOMMU perf" is a very common error on modern AMD
systems due to lack of documentation on it.

Note that you are running older BIOS (F0CN17WW and latest is F0CN24WW).

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

Title:
  Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lenovo IdeaPad S540, 13-ARE
  AMD Ryzen 4800U, 16GB dual channel RAM, 13.3" 2560x1600 screen. 
  Note this laptop is a lot like the Lenovo Slim 7, it seems this laptop UEFI 
Bios does advertise S3 sleep, the Slim 7 only advertises S2idle. 

  The errors are related to AMD Ryzen 4000 series.

  Clean (no dual boot) Ubuntu Budgie 20.04.1 with kernel upgraded to
  5.8.11.

  Full dmesg: https://pastebin.com/nFbHB22d
  Journalclt after boot: https://pastebin.com/bcpw8Vhc

  erros only from dmesg:
  $ sudo dmesg -l err
  [2.686094] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
  [4.818164] I2C multi instantiate pseudo device driver INT3515:00: IRQ 
index 1 not found
  [4.836122] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0
  [4.971650] ACPI Error: No handler for Region [ECSI] (e6d23662) 
[EmbeddedControl] (20200528/evregion-127)
  [4.971933] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20200528/exfldio-261)
  [4.972172] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.972447] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.972736] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
  [5.871695] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) 
failed: -517
  [6.127547] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.128334] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.128558] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.938706] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed 
to add display topology, DTM TA is not initialized.

  $ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal
  Linux Idefix 5.8.11-050811-generic #202009230858 SMP Wed Sep 23 13:06:55 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897392/+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 1897392] [NEW] Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

2020-09-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Lenovo IdeaPad S540, 13-ARE
AMD Ryzen 4800U, 16GB dual channel RAM, 13.3" 2560x1600 screen. 
Note this laptop is a lot like the Lenovo Slim 7, it seems this laptop UEFI 
Bios does advertise S3 sleep, the Slim 7 only advertises S2idle. 

The errors are related to AMD Ryzen 4000 series.

Clean (no dual boot) Ubuntu Budgie 20.04.1 with kernel upgraded to
5.8.11.

Full dmesg: https://pastebin.com/nFbHB22d
Journalclt after boot: https://pastebin.com/bcpw8Vhc

erros only from dmesg:
$ sudo dmesg -l err
[2.686094] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
[4.818164] I2C multi instantiate pseudo device driver INT3515:00: IRQ index 
1 not found
[4.836122] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0
[4.971650] ACPI Error: No handler for Region [ECSI] (e6d23662) 
[EmbeddedControl] (20200528/evregion-127)
[4.971933] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20200528/exfldio-261)
[4.972172] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error 
(AE_NOT_EXIST) (20200528/psparse-529)
[4.972447] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error 
(AE_NOT_EXIST) (20200528/psparse-529)
[4.972736] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
[5.871695] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: 
-517
[6.127547] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
[6.128334] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
[6.128558] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
[6.938706] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed 
to add display topology, DTM TA is not initialized.

$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename:   focal
Linux Idefix 5.8.11-050811-generic #202009230858 SMP Wed Sep 23 13:06:55 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

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


** Tags: bot-comment
-- 
Ryzen 4800u, kernel 5.8.11 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)
https://bugs.launchpad.net/bugs/1897392
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 317781] Re: Ext4 data loss

2020-09-26 Thread Kai Mast
Feel free to close this. The bug has not affected me in over a decade.

-- 
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/317781

Title:
  Ext4 data loss

Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Jaunty:
  Invalid
Status in linux source package in Jaunty:
  Fix Released

Bug description:
  I recently installed Kubuntu Jaunty on a new drive, using Ext4 for all
  my data.

  The first time i had this problem was a few days ago when after a
  power loss ktimetracker's config file was replaced by a 0 byte version
  . No idea if anything else was affected.. I just noticed ktimetracker
  right away.

  Today, I was experimenting with some BIOS settings that made the system crash 
right after loading the desktop. After a clean reboot pretty much any file 
written to by any application (during the previous boot) was 0 bytes.
  For example Plasma and some of the KDE core config files were reset. Also 
some of my MySQL databases were killed...

  My EXT4 partitions all use the default settings with no performance
  tweaks. Barriers on, extents on, ordered data mode..

  I used Ext3 for 2 years and I never had any problems after power
  losses or system crashes.

  Jaunty has all the recent updates except for the kernel that i don't
  upgrade because of bug #315006

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-4-generic 2.6.28-4.6
  ProcCmdLine: root=UUID=81942248-db70-46ef-97df-836006aad399 ro 
rootfstype=ext4 vga=791 all_generic_ide elevator=anticipatory
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-4.6-generic
  SourcePackage: linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/317781/+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 317781] Re: Ext4 data loss

2020-09-26 Thread Patola
Shouldn't this problem be closed by now if this bug was fixed?

-- 
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/317781

Title:
  Ext4 data loss

Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Jaunty:
  Invalid
Status in linux source package in Jaunty:
  Fix Released

Bug description:
  I recently installed Kubuntu Jaunty on a new drive, using Ext4 for all
  my data.

  The first time i had this problem was a few days ago when after a
  power loss ktimetracker's config file was replaced by a 0 byte version
  . No idea if anything else was affected.. I just noticed ktimetracker
  right away.

  Today, I was experimenting with some BIOS settings that made the system crash 
right after loading the desktop. After a clean reboot pretty much any file 
written to by any application (during the previous boot) was 0 bytes.
  For example Plasma and some of the KDE core config files were reset. Also 
some of my MySQL databases were killed...

  My EXT4 partitions all use the default settings with no performance
  tweaks. Barriers on, extents on, ordered data mode..

  I used Ext3 for 2 years and I never had any problems after power
  losses or system crashes.

  Jaunty has all the recent updates except for the kernel that i don't
  upgrade because of bug #315006

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-4-generic 2.6.28-4.6
  ProcCmdLine: root=UUID=81942248-db70-46ef-97df-836006aad399 ro 
rootfstype=ext4 vga=791 all_generic_ide elevator=anticipatory
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-4.6-generic
  SourcePackage: linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/317781/+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

2020-09-26 Thread Kai Mast
Found this in my syslog but no indication of why it happens.

`[ 4231.104191] usb 5-1.3: reset low-speed USB device number 15 using
xhci_hcd`

-- 
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: :0e:00.0  

[Kernel-packages] [Bug 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]

2020-09-26 Thread Chris Schadl
Just thought that I would chime in here and say that this is definitely
a WiFi interference issue.  On my Dell XPS 9550 (bcm20703a1 bluetooth
chipset) I would get really bad choppy, de-synced audio sometimes.  I
finally figured out that whenever it was happening, I was connected to a
2.4 GHz WiFi network.  Connecting to a 5GHz WiFi network solved the
problem.

-- 
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/1825639

Title:
  Pulseaudio skips some time in the audio buffer, causing a bluetooth
  delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth
  4.0]

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  This is the same problem in
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and
  even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem
  persists (this T430 laptop has inbuilt Bluetooth).

  This makes listening to music or any audio over Bluetooth almost
  unbearable - while it is temporarily fixed by running `pactl suspend-
  sink 1 && pactl suspend-sink 0` it soon returns. I have even updated
  the BIOS but the problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 20 13:10:59 2019
  InstallationDate: Installed on 2018-11-26 (144 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349G4G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB9WW (2.79 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349G4G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349G4G
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 24:FD:52:8C:5D:82  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:65823 acl:64 sco:0 events:9052 errors:0
TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+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

2020-09-26 Thread Kai Mast
Just to clarify. My peripherals are still powered on, show up in lsusb,
and /proc/bus/input/devices, but no input is captured by my desktop.
Happens on both Wayland and X11.

Should I open a new bug for this? Seems to be related to the USB hub in
the TB16.

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

  

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2020-09-26 Thread Kai Mast
Setting thunderbolt to No Security on my device (XPS 9500 with Ubuntu 20.10) 
fixes the random disconnect, but input devices still randomly stop working. 
The only way to fix this is to unplug them and plug them back in. 

When they stop working there is no disconnect message, or any other
message, in my dmesg.

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

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

2020-09-26 Thread 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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] WifiSyslog.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414571/+files/WifiSyslog.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] ProcInterrupts.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414566/+files/ProcInterrupts.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] ProcCpuinfoMinimal.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414564/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] CurrentDmesg.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414560/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] ProcEnviron.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414565/+files/ProcEnviron.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] PulseList.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414568/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] Lspci.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1897416/+attachment/5414562/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] ProcCpuinfo.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414563/+files/ProcCpuinfo.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] UdevDb.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1897416/+attachment/5414570/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] IwConfig.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414561/+files/IwConfig.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] RfKill.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1897416/+attachment/5414569/+files/RfKill.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] CRDA.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1897416/+attachment/5414559/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] ProcModules.txt

2020-09-26 Thread Seiichi Nakashima
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414567/+files/ProcModules.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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
  dmi.board.asset.tag: Default string
  dmi.board.name: EZbook
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1897416] Re: grub 2.04 could not boot from iso at UEFI native environment

2020-09-26 Thread Seiichi Nakashima
apport information

** Tags added: apport-collected bionic

** Description changed:

  Dear everyone
  
  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.
  
  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.
  
  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.17
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nakasima   1542 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-05-29 (120 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Jumper EZbook
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
+ ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-48-generic N/A
+  linux-backports-modules-5.4.0-48-generic  N/A
+  linux-firmware1.173.19
+ Tags:  bionic
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/01/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
+ dmi.board.asset.tag: Default string
+ dmi.board.name: EZbook
+ dmi.board.vendor: Jumper
+ dmi.board.version: Default string
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
+ dmi.product.family: Default string
+ dmi.product.name: EZbook
+ dmi.product.sku: Default string
+ dmi.product.version: Default string
+ dmi.sys.vendor: Jumper

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1897416/+attachment/5414558/+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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1542 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-05-29 (120 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   

[Kernel-packages] [Bug 1897416] [NEW] grub 2.04 could not boot from iso at UEFI native environment

2020-09-26 Thread Seiichi Nakashima
Public bug reported:

Dear everyone

I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
grub 2.04 can boot from iso file.
and I use ubuntu-18.04.5 at my UEFI native environment note PC.
grub 2.02 can boot from iso file.

I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
I power on note PC, and selecting boot device to use UEFI boot manager.
then grub 2.04 boot menu displayed.

I change Boot from next volume to iso boot.
iso boot step as same as grub 2.02 definition.
but grub 2.04 could not boot from iso, display black screen.
I power off note PC.

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

-- 
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/1897416

Title:
  grub 2.04 could not boot from iso at UEFI native environment

Status in linux package in Ubuntu:
  New

Bug description:
  Dear everyone

  I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
  grub 2.04 can boot from iso file.
  and I use ubuntu-18.04.5 at my UEFI native environment note PC.
  grub 2.02 can boot from iso file.

  I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
  I power on note PC, and selecting boot device to use UEFI boot manager.
  then grub 2.04 boot menu displayed.

  I change Boot from next volume to iso boot.
  iso boot step as same as grub 2.02 definition.
  but grub 2.04 could not boot from iso, display black screen.
  I power off note PC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2020-09-26 Thread John Hoff
@PowerKiKi

PowerKiKi, I had to reload my pc for another project, and after
reloading I found that same lack of stickiness...  Not wanting to go
backwards, I felt I had to chase down the full fix.  This should fix
your issue (caused by pulse) if you want to skip the background audio
file...I also improved the Daemon script to ensure later execution and
added a second daemon to run the script on suspend/restore.  With this
setup I have not had to manually run the script in a week or so.  Its
like sound just works normally now...


Fresh Install Setup Steps

sudo apt-get install alsa-tools
Rename alsa-base to bkup/etc/modprobe.d/alsa-base.conf
placed TO912.sh script with verbs and set as 777 +x
create and placed $ sudo chmod 664 /etc/systemd/system/ionsound.service 


[Unit]
Description=Custom Sound

[Service]
Type=idle
ExecStart=/home/ion420/Hoff/Linux_Files/Ion_Audio/TO912.sh

[Install]
WantedBy=multi-user.target

create and placed $ sudo chmod 664 
/etc/systemd/system/ionsoundsleep.service

[Unit]
Description=Custom Sound Sleep Fix

[Service]
Type=idle
ExecStart=/home/ion420/Hoff/Linux_Files/Ion_Audio/TO912.sh

[Install]
WantedBy=suspend.target

activate
sudo systemctl daemon-reload
sudo systemctl enable ionsound.service  
sudo systemctl enable ionsoundsleep.service 

turn off pulse idle
sudo gedit /etc/pulse/default.pa
Add comments to ### load-module module-suspend-on-idle

verify script runs at boot and sound 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/1851518

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  

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

2020-09-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "polling_pin_state_touchpad.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

-- 
You received this bug notification because you are a member of 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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 

[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2020-09-26 Thread Michael
Only workaround is to not use suspend to ram, but suspend to disk.

-- 
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/1612916

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

Status in linux package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New
Status in linux package in Debian:
  New

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1897404] Status changed to Confirmed

2020-09-26 Thread 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/1897404

Title:
  Elantech Touchpad not working w/ Synaptics Driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 20.04.1 LTS

  2) Package linux-image-5.4.0-48-generic

  3) Expected to upgrade to 20.04 with existing hardware already
  supported

  4) Upgraded with odd, erratic behavior from laptop touchpad
  (Elantech). Tap to click did not work, but scrolling did. After toying
  with settings, tap to click starting working, but scrolling stopped
  working.

  I found a link which provided a fix for me, which was uninstalling the
  xorg-input-synaptics package, and forcing the system to use libinput
  instead. the user Pilot6 suggested this was a kernel bug and to file a
  bug report accordingly.

  https://askubuntu.com/questions/1250841/ubuntu-20-04-elantech-
  touchpad-not-working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  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.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1391 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 26 13:48:29 2020
  InstallationDate: Installed on 2013-05-22 (2683 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire 5755
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5c6346b5-949b-4636-8e99-fb4002e2e81d ro acpi_osi=Linux 
acpi_backlight=vendor libata.allow_tpm=1
  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-09-26 (0 days ago)
  dmi.bios.date: 09/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV51_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd09/07/2011:svnAcer:pnAspire5755:pvrV1.14:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.14:
  dmi.product.name: Aspire 5755
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-05-16T07:56:07.188547

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897404/+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 1897404] [NEW] Elantech Touchpad not working w/ Synaptics Driver

2020-09-26 Thread T Parys
Public bug reported:

1) Ubuntu 20.04.1 LTS

2) Package linux-image-5.4.0-48-generic

3) Expected to upgrade to 20.04 with existing hardware already supported

4) Upgraded with odd, erratic behavior from laptop touchpad (Elantech).
Tap to click did not work, but scrolling did. After toying with
settings, tap to click starting working, but scrolling stopped working.

I found a link which provided a fix for me, which was uninstalling the
xorg-input-synaptics package, and forcing the system to use libinput
instead. the user Pilot6 suggested this was a kernel bug and to file a
bug report accordingly.

https://askubuntu.com/questions/1250841/ubuntu-20-04-elantech-touchpad-
not-working

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
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.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tim1391 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Sep 26 13:48:29 2020
InstallationDate: Installed on 2013-05-22 (2683 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire 5755
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5c6346b5-949b-4636-8e99-fb4002e2e81d ro acpi_osi=Linux 
acpi_backlight=vendor libata.allow_tpm=1
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-09-26 (0 days ago)
dmi.bios.date: 09/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JV51_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.14
dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd09/07/2011:svnAcer:pnAspire5755:pvrV1.14:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.14:
dmi.product.name: Aspire 5755
dmi.product.version: V1.14
dmi.sys.vendor: Acer
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2015-05-16T07:56:07.188547

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


** Tags: amd64 apport-bug 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/1897404

Title:
  Elantech Touchpad not working w/ Synaptics Driver

Status in linux package in Ubuntu:
  New

Bug description:
  1) Ubuntu 20.04.1 LTS

  2) Package linux-image-5.4.0-48-generic

  3) Expected to upgrade to 20.04 with existing hardware already
  supported

  4) Upgraded with odd, erratic behavior from laptop touchpad
  (Elantech). Tap to click did not work, but scrolling did. After toying
  with settings, tap to click starting working, but scrolling stopped
  working.

  I found a link which provided a fix for me, which was uninstalling the
  xorg-input-synaptics package, and forcing the system to use libinput
  instead. the user Pilot6 suggested this was a kernel bug and to file a
  bug report accordingly.

  https://askubuntu.com/questions/1250841/ubuntu-20-04-elantech-
  touchpad-not-working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  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.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1391 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 26 13:48:29 2020
  InstallationDate: Installed on 2013-05-22 (2683 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire 5755
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5c6346b5-949b-4636-8e99-fb4002e2e81d ro acpi_osi=Linux 
acpi_backlight=vendor libata.allow_tpm=1
  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-09-26 (0 days ago)
  dmi.bios.date: 09/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV51_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd09/07/2011:svnAcer:pnAspire5755:pvrV1.14:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.14:
  dmi.product.name: Aspire 5755
  dmi.product.version: V1.14
  

[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45

2020-09-26 Thread Ami
@ishinberg0, as achille-fouilleul wrote, this is probably a different bug.
A few questions you can ask to make sure of that:

- Do you get any error message at all? 
- Which nvme items do you see in /dev when in BusyBox, and which ones when you 
boot normally using kernels that work for you?
- Do you see the problematic controller when running lspci (see crysman's 
comment)?

Good luck!

-- 
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/1894378

Title:
  Cannot boot after updating kernel to version 5.4.0-45

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After the kernel update from version 5.4.0-42 to version 5.4.0-45 a
  few days ago, the boot process is ending in a BusyBox shell.
  Apparently it cannot properly identify my M.2 NMVe SSD device where my
  root partition is. Indeed, it is not listed in /dev (precisely: nvme0
  is listed in /dev, but nvme0n1 and its partitions are not). For now,
  I'm solving this problem by booting the previous kernel, 5.4.0-42.
  This works fine.

  Also, an earlier attempt ended in a different shell that presented the
  error message "Gave up on waiting for root file system device". The
  UUID it indicated as missing is the correct UUID of my root partition,
  which also appears on /etc/fstab.

  I tried to re-build initrd.img-5.4.0-45-generic, but to no avail.

  Let me also mention that in another computer with a non-M.2 SSD,
  kernel 5.4.0-45 boots properly.

  This bug seems to be the one mentioned in the following "Unix & Linux" forum 
question:
  
https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update

  Many thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ami3801 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Sep  5 17:42:26 2020
  HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea
  InstallationDate: Installed on 2017-10-04 (1066 days ago)
  InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma
   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
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: System manufacturer System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3807
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+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 1894613] Re: risc-v 5.8 kernel oops on ftrace tests

2020-09-26 Thread Colin Ian King
git bisect good
cfafe260137418d0265d0df3bb18dc494af2b43e is the first bad commit
commit cfafe260137418d0265d0df3bb18dc494af2b43e
Author: Atish Patra 
Date:   Tue Mar 17 18:11:43 2020 -0700

RISC-V: Add supported for ordered booting method using HSM

Currently, all harts have to jump Linux in RISC-V. This complicates the
multi-stage boot process as every transient stage also has to ensure all
harts enter to that stage and jump to Linux afterwards. It also obstructs
a clean Kexec implementation.

SBI HSM extension provides alternate solutions where only a single hart
need to boot and enter Linux. The booting hart can bring up secondary
harts one by one afterwards.

Add SBI HSM based cpu_ops that implements an ordered booting method in
RISC-V. This change is also backward compatible with older firmware not
implementing HSM extension. If a latest kernel is used with older
firmware, it will continue to use the default spinning booting method.

Signed-off-by: Atish Patra 
Reviewed-by: Anup Patel 
Signed-off-by: Palmer Dabbelt 

 arch/riscv/kernel/Makefile  |  3 ++
 arch/riscv/kernel/cpu_ops.c | 10 -
 arch/riscv/kernel/cpu_ops_sbi.c | 81 +
 arch/riscv/kernel/head.S| 26 +
 arch/riscv/kernel/smpboot.c |  2 +-
 arch/riscv/kernel/traps.c   |  2 +-
 6 files changed, 121 insertions(+), 3 deletions(-)
 create mode 100644 arch/riscv/kernel/cpu_ops_sbi.c

-- 
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/1894613

Title:
  risc-v 5.8 kernel oops on ftrace tests

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
   5.8.0-1-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu
  10.2.0-5ubuntu2) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35)
  #1-Ubuntu SMP Thu Aug 27 19:51:38 UTC 2020 (Ubuntu 5.8.0-1.1-generic
  5.8.4

  
  18:30:06 DEBUG| [stdout] # selftests: ftrace: ftracetest^M^M
  18:30:07 DEBUG| [stdout] # === Ftrace unit tests ===^M^M
  18:30:10 DEBUG| [stdout] # [1] Basic trace file check   [PASS]^M^M
  [17433.113458] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.113533] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.113552] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.113573] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.113591] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.114290] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.114306] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.114315] Oops [#1]^M^M
  [17433.114630] Unable to handle kernel NULL pointer dereference at virtual 
address ^M^M
  [17433.114690] Modules linked in: virtio_rng binfmt_misc uio_pdrv_genirq uio 
drm sch_fq_codel drm_panel_orientation_quirks backlight ip_tables x_tables 
autofs4 virtio_net net_failover virtio_blk failover [last unloaded: 
signpost]^M^M
  [17433.115296] CPU: 1 PID: 15 Comm: migration/1 Tainted: GW  OE 
5.8.0-1-generic #1-Ubuntu^M^M
  [17433.115419] epc:  ra :  sp : 
ffe1f5c67d90^M^M
  [17433.115442]  gp : ffe001722298 tp : ffe1f5c3ae00 t0 : 
^M^M
  [17433.115459]  t1 : 6000 t2 : 000bbc00 s0 : 
0022^M^M
  [17433.115475]  s1 : ffe0002b7c12 a0 : ffe000963a64 a1 : 
0022^M^M
  [17433.115491]  a2 :  a3 :  a4 : 
^M^M
  [17433.115507]  a5 : ffe1fec95580 a6 : 00ff a7 : 
0001^M^M
  [17433.115523]  s2 : 0001 s3 : ffe9d580 s4 : 
ffe001724210^M^M
  [17433.115540]  s5 : ffe1fec9a3b8 s6 :  s7 : 
0001^M^M
  [17433.115556]  s8 : ffe0016f07cb s9 : ffe1e909bb80 s10: 
ffe0002b7ba6^M^M
  [17433.115573]  s11: ffe1e909bba8 t3 : 006c t4 : 
002c73ba^M^M
  [17433.115586]  t5 : 001f7fa8 t6 : ffe000c02d1c^M^M
  [17433.115603] status: 0120 badaddr:  cause: 
000c^M^M

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894613/+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

2020-09-26 Thread Coiby Xu
Hi,

I've found out that there is something wrong with the GPIO interrupt
controller under Linux. For the details, you can check
https://www.spinics.net/lists/linux-input/msg69267.html.  While I'm
still working on the ultimate solution, you may be interested in the
patch as attached which makes the touchpad work by polling HID reports
from the touchpad.

I've tested the patch for the Synaptics touchpad (MSFT0001:00
06CB:7F28). I guess it will also work for the Elan touchpad (MSFT0001:00
04F3:3140) based on the ACPI DSDT. If not, could you share the following
info with me,

1) dsdt.dsl

Use the following commands to get dsdt.dsl (you need to install acpica
which provides iasl)

 a) sudo acpidump > acpidata.out
 b) acpixtract -sSSDT acpidata.out
 c) acpixtract -sDSDT acpidata.out
 d) iasl -da dsdt.dat ssdt*.dat

2) dmesg dump when booting kernel with the following command line
parameters

i2c-designware-core.dyndbg=+p i2c-hid.debug=1

Thank you!


** Patch added: "polling_pin_state_touchpad.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5414497/+files/polling_pin_state_touchpad.patch

-- 
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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 

[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45

2020-09-26 Thread Achille Fouilleul
@ishinberg0

The issue ami, crysman and I had was related to a specific NVMe
controller (PCI IDs 126f:2263). 5.4.0-48 fixed it for ami and I at
least. I guess your issue is different; I suggest you file a new bug
report with details about your system (dmesg, lspci output etc.).

-- 
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/1894378

Title:
  Cannot boot after updating kernel to version 5.4.0-45

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After the kernel update from version 5.4.0-42 to version 5.4.0-45 a
  few days ago, the boot process is ending in a BusyBox shell.
  Apparently it cannot properly identify my M.2 NMVe SSD device where my
  root partition is. Indeed, it is not listed in /dev (precisely: nvme0
  is listed in /dev, but nvme0n1 and its partitions are not). For now,
  I'm solving this problem by booting the previous kernel, 5.4.0-42.
  This works fine.

  Also, an earlier attempt ended in a different shell that presented the
  error message "Gave up on waiting for root file system device". The
  UUID it indicated as missing is the correct UUID of my root partition,
  which also appears on /etc/fstab.

  I tried to re-build initrd.img-5.4.0-45-generic, but to no avail.

  Let me also mention that in another computer with a non-M.2 SSD,
  kernel 5.4.0-45 boots properly.

  This bug seems to be the one mentioned in the following "Unix & Linux" forum 
question:
  
https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update

  Many thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ami3801 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Sep  5 17:42:26 2020
  HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea
  InstallationDate: Installed on 2017-10-04 (1066 days ago)
  InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma
   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
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: System manufacturer System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3807
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+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 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45

2020-09-26 Thread Idan Shinberg
Sorry to be a buzz kill but this bug started affecting **after** upgrading to 
5.4.0-48.
5.4.0-47 works fine. I'm running on top of Dell XPS 9700.

Any ideas/help are much advised.

-- 
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/1894378

Title:
  Cannot boot after updating kernel to version 5.4.0-45

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After the kernel update from version 5.4.0-42 to version 5.4.0-45 a
  few days ago, the boot process is ending in a BusyBox shell.
  Apparently it cannot properly identify my M.2 NMVe SSD device where my
  root partition is. Indeed, it is not listed in /dev (precisely: nvme0
  is listed in /dev, but nvme0n1 and its partitions are not). For now,
  I'm solving this problem by booting the previous kernel, 5.4.0-42.
  This works fine.

  Also, an earlier attempt ended in a different shell that presented the
  error message "Gave up on waiting for root file system device". The
  UUID it indicated as missing is the correct UUID of my root partition,
  which also appears on /etc/fstab.

  I tried to re-build initrd.img-5.4.0-45-generic, but to no avail.

  Let me also mention that in another computer with a non-M.2 SSD,
  kernel 5.4.0-45 boots properly.

  This bug seems to be the one mentioned in the following "Unix & Linux" forum 
question:
  
https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update

  Many thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ami3801 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Sep  5 17:42:26 2020
  HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea
  InstallationDate: Installed on 2017-10-04 (1066 days ago)
  InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma
   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
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: System manufacturer System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3807
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+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 1826403] Re: Ethernet won't connect when cable is plugged in at boot

2020-09-26 Thread Amine Bouyzem
Ubuntu 20.04

** Changed in: linux (Ubuntu)
   Status: Invalid => 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/1826403

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826403/+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 1897389] Status changed to Confirmed

2020-09-26 Thread 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/1897389

Title:
  Touchpad not detected in Lenovo Thinkbook

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=275d Product=0ba6 Version=0111
  N: Name="USB OPTICAL MOUSE "
  P: Phys=usb-:00:14.0-3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:275D:0BA6.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=5986 Product=2130 Version=5609
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-6/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hans   1750 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 26 16:23:26 2020
  InstallationDate: Installed on 2020-09-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20SL
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=6b85afff-021d-4aa5-9738-5c8720860630 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN17WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1897389] [NEW] Touchpad not detected in Lenovo Thinkbook

2020-09-26 Thread Hans Terwisscha-Dekker
Public bug reported:

hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=275d Product=0ba6 Version=0111
N: Name="USB OPTICAL MOUSE "
P: Phys=usb-:00:14.0-3/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:275D:0BA6.0001/input/input4
U: Uniq=
H: Handlers=mouse0 event4 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5
U: Uniq=
H: Handlers=rfkill kbd event5 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0003 Vendor=5986 Product=2130 Version=5609
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-6/button
S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
U: Uniq=
H: Handlers=event7 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=4

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hans   1750 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 26 16:23:26 2020
InstallationDate: Installed on 2020-09-26 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20SL
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=6b85afff-021d-4aa5-9738-5c8720860630 ro recovery nomodeset
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN17WW
dmi.board.name: LVAC/LVAD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 14-IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
dmi.product.family: Thinkbook 14-IIL
dmi.product.name: 20SL
dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
dmi.product.version: Lenovo ThinkBook 14-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug 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/1897389

Title:
  Touchpad not detected in Lenovo Thinkbook

Status in linux package in Ubuntu:
  New

Bug description:
  hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: 

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

2020-09-26 Thread 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/1897387

Title:
  package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is occuring error report

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irfan  2090 F pulseaudio
  Date: Sat Sep 26 18:43:30 2020
  DuplicateSignature: 
package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=c3cf625d-eb7d-40d2-adbe-ad521bc8dd86
  InstallationDate: Installed on 2020-09-26 (0 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: LENOVO 20074
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=3441b8a6-77ee-44c6-83fd-1db74d87007e ro 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: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2020-09-26 (0 days ago)
  dmi.bios.date: 06/13/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3CCN09WW
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr3CCN09WW:bd06/13/2010:svnLENOVO:pn20074:pvrLenovo-S10-3c:rvnLENOVO:rn:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: 20074
  dmi.product.version: Lenovo-S10-3c
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897387/+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 1897387] BOT: Examined VarLogDistupgradeApttermlog.gz

2020-09-26 Thread Ubuntu Kernel Bot
update-initramfs: deferring update (hook will be called later)
   Failed to symbolic-link boot/initrd.img-3.13.0-32-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-3.13.0-32-generic.postinst line 629.
   dpkg: error processing package linux-image-3.13.0-32-generic (--configure):

   Failed to symbolic-link boot/initrd.img-3.13.0-32-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-3.13.0-32-generic.postinst line 629.
   dpkg: error processing package linux-image-3.13.0-32-generic (--configure):
subprocess installed post-installation script returned error exit status 17


** Tags added: varlogdistupgradeapttermlog-examined

-- 
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/1897387

Title:
  package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is occuring error report

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irfan  2090 F pulseaudio
  Date: Sat Sep 26 18:43:30 2020
  DuplicateSignature: 
package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=c3cf625d-eb7d-40d2-adbe-ad521bc8dd86
  InstallationDate: Installed on 2020-09-26 (0 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: LENOVO 20074
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=3441b8a6-77ee-44c6-83fd-1db74d87007e ro 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: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2020-09-26 (0 days ago)
  dmi.bios.date: 06/13/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3CCN09WW
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr3CCN09WW:bd06/13/2010:svnLENOVO:pn20074:pvrLenovo-S10-3c:rvnLENOVO:rn:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: 20074
  dmi.product.version: Lenovo-S10-3c
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897387/+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 1897387] [NEW] package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

2020-09-26 Thread Irfan Reza
Public bug reported:

This is occuring error report

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  irfan  2090 F pulseaudio
Date: Sat Sep 26 18:43:30 2020
DuplicateSignature: 
package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed 
post-installation script returned error exit status 17
ErrorMessage: subprocess installed post-installation script returned error exit 
status 17
HibernationDevice: RESUME=UUID=c3cf625d-eb7d-40d2-adbe-ad521bc8dd86
InstallationDate: Installed on 2020-09-26 (0 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
MachineType: LENOVO 20074
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=3441b8a6-77ee-44c6-83fd-1db74d87007e ro 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: grub-pc 2.02~beta2-9ubuntu1.17
SourcePackage: linux
Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
UpgradeStatus: Upgraded to trusty on 2020-09-26 (0 days ago)
dmi.bios.date: 06/13/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 3CCN09WW
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvr3CCN09WW:bd06/13/2010:svnLENOVO:pn20074:pvrLenovo-S10-3c:rvnLENOVO:rn:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: 20074
dmi.product.version: Lenovo-S10-3c
dmi.sys.vendor: LENOVO

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


** Tags: apport-package dist-upgrade i386 need-duplicate-check trusty 
varlogdistupgradeapttermlog-examined

-- 
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/1897387

Title:
  package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is occuring error report

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irfan  2090 F pulseaudio
  Date: Sat Sep 26 18:43:30 2020
  DuplicateSignature: 
package:linux-image-3.13.0-32-generic:3.13.0-32.57:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=c3cf625d-eb7d-40d2-adbe-ad521bc8dd86
  InstallationDate: Installed on 2020-09-26 (0 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: LENOVO 20074
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=3441b8a6-77ee-44c6-83fd-1db74d87007e ro 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: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-32-generic 3.13.0-32.57 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2020-09-26 (0 days ago)
  dmi.bios.date: 06/13/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3CCN09WW
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr3CCN09WW:bd06/13/2010:svnLENOVO:pn20074:pvrLenovo-S10-3c:rvnLENOVO:rn:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: 20074
  dmi.product.version: Lenovo-S10-3c
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

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

2020-09-26 Thread Solomon Thatcher
Would it be possible to replace the track-pad with a different one from
a supported manufacturer?

-- 
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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 

[Kernel-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

2020-09-26 Thread Amine Bouyzem
Hello everyone
I don't know if this thread is still active but I'm facing the same problem 
with Ubuntu 20.04
I can provide all the necessary informations but I don't know what you will 
need.
Best regards

-- 
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/1826403

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826403/+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

2020-09-26 Thread wangjun
lenovo release new bios

EUCN26WW

-- 
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:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  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.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  

[Kernel-packages] [Bug 1894017] Re: Keyboard not working

2020-09-26 Thread Carlos
I can confirm both the bug and it being fixed in 5.4.18. 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/1894017

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The laptop keyboard doesn't work at login or in the de. If I
  ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
  keyboard works. An external usb keyboard works everywhere. The
  laptop's keyboard does work everywhere with the previous kernel
  5.4.0.42.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
  Uname: Linux 5.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Sep  3 03:09:49 2020
  InstallationDate: Installed on 2019-08-07 (392 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency 
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-lowlatency N/A
   linux-backports-modules-5.4.0-45-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.57
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.sku: M0B61EA#ACQ
  dmi.product.version: 097710405F00010420180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1798166] Re: “Mouse battery low” notification can't be disabled

2020-09-26 Thread Florian 'rephlex' Panzer
Clarification: this bug ist not about wrong battery Level measurements
(Nobody reported that), it's about users being unable to disable
notifications. The notification is shown even when in DND mode.

-- 
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/1798166

Title:
  “Mouse battery low” notification can't be disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

  ---

  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
    Installed: (none)
    Candidate: 0.9.35+16.04.20160415-0ubuntu2
    Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+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