from:"Owen"

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  unable to detect touchpad for asus A450L

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

Bug description:
  Touchpad able to detect using window but doesnt shows up in
  proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 04:02:04 2021
  InstallationDate: Installed on 2021-02-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1915873/+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 1911085] Re: no touchpad available in devices

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  no touchpad available in devices

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

Bug description:
  chris@jones-ideapad-il:~$ 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=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/input4
  U: Uniq=
  H: Handlers=rfkill kbd event4 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=5986 Product=1135 Version=5408
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0003 Vendor=046d Product=4002 Version=0111
  N: Name="Logitech K750"
  P: Phys=usb-:00:14.0-2/input2:1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0003/0003:046D:4002.0004/input/input22
  U: Uniq=4002-09-1b-c4-72
  H: Handlers=sysrq kbd event6 leds 
  B: PROP=0
  B: EV=12001f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 
7bfad941dfff ffbeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  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/LNXVIDEO:00/input/input23
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=046d Product=4082 Version=0111
  N: Name="Logitech MX Master 3"
  P: Phys=usb-:00:14.0-2/input2:2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0003/0003:046D:4082.0005/input/input24
  U: Uniq=4082-04-68-de-4f
  H: Handlers=sysrq kbd mouse0 event8 leds 
  B: PROP=0
  B: EV=120017
  B: KEY= 10007 ff9f207ac14057ff febeffdfffef 
fffe
  B: REL=1943
  B: MSC=10
  B: LED=1f

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input25
  U: Uniq=
  H: Handlers=event9 
  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/input26
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input27
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input28
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input29
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input30
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=

[Kernel-packages] [Bug 1913634] Re: Touchpad not working with 20.04 on ThinkBook 13s IML

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not working with 20.04 on ThinkBook 13s IML

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

Bug description:
  After installing current 20.04 on ThinkBook 13s IML I have found that
  its touchpad is not recognized on boot and not working at all.

  $ dmesg |grep i2c
  [0.817823] i2c /dev entries driver
  [1.038337] i2c i2c-0: 1/1 memory slots populated (from DMI)
  [1.044114] i2c_hid i2c-CUST0001:00: supply vdd not found, using dummy 
regulator
  [1.044161] i2c_hid i2c-CUST0001:00: supply vddl not found, using dummy 
regulator
  [1.199246] i2c_hid i2c-CUST0001:00: failed to retrieve report from device.
  [1.199281] input: CUST0001:00 06CB:CD98 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input5
  [1.199393] input: CUST0001:00 06CB:CD98 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input6
  [1.199449] hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 
Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00
  [   12.714228] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [   13.742776] i2c_designware i2c_designware.0: controller timed out
  [   13.742785] i2c_hid i2c-CUST0001:00: failed to retrieve report from device.
  [   13.742844] input: CUST0001:00 06CB:CD98 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input10
  [   13.742950] input: CUST0001:00 06CB:CD98 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input11
  [   13.743015] hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID 
v1.00 Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00
  [   14.766780] i2c_designware i2c_designware.0: controller timed out
  [   14.766793] i2c_hid i2c-CUST0001:00: failed to set a report to device.
  [   15.791022] i2c_designware i2c_designware.0: controller timed out
  [   15.791060] i2c_hid i2c-CUST0001:00: failed to set a report to device.
  [   16.815119] i2c_designware i2c_designware.0: controller timed out
  [   17.838959] i2c_designware i2c_designware.0: controller timed out
  [   17.838978] i2c_hid i2c-CUST0001:00: failed to set a report to device.
  [   18.863103] i2c_designware i2c_designware.0: controller timed out
  [   19.887102] i2c_designware i2c_designware.0: controller timed out
  [   20.98] i2c_designware i2c_designware.0: controller timed out
  [   21.938779] i2c_designware i2c_designware.0: controller timed out
  [   22.958772] i2c_designware i2c_designware.0: controller timed out
  [   23.982770] i2c_designware i2c_designware.0: controller timed out
  [   25.006802] i2c_designware i2c_designware.0: controller timed out
  [   26.03] i2c_designware i2c_designware.0: controller timed out
  [   27.055015] i2c_designware i2c_designware.0: controller timed out
  [   28.078885] i2c_designware i2c_designware.0: controller timed out
  [   29.103159] i2c_designware i2c_designware.0: controller timed out
  [   30.127106] i2c_designware i2c_designware.0: controller timed out
  [   31.151129] i2c_designware i2c_designware.0: controller timed out
  [   32.175108] i2c_designware i2c_designware.0: controller timed out
  [   32.175146] i2c_hid i2c-CUST0001:00: failed to set a report to device.
  [   33.199020] i2c_designware i2c_designware.0: controller timed out
  [   34.222805] i2c_designware i2c_designware.0: controller timed out
  [   35.246821] i2c_designware i2c_designware.0: controller timed out
  [   36.274763] i2c_designware i2c_designware.0: controller timed out
  [   37.294764] i2c_designware i2c_designware.0: controller timed out
  [   38.318808] i2c_designware i2c_designware.0: controller timed out
  [   39.342999] i2c_designware i2c_designware.0: controller timed out
  [   40.366798] i2c_designware i2c_designware.0: controller timed out
  [   41.391007] i2c_designware i2c_designware.0: controller timed out
  [   42.415123] i2c_designware i2c_designware.0: controller timed out
  [   43.437697] i2c_designware i2c_designware.0: controller timed out

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 28 22:35:50 2021
  InstallationDate: Installed on 2020-10-29 (91 days ago)

[Kernel-packages] [Bug 1917013] Re: Touchpad not working Ubuntu 20.4 Lenovo

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not working Ubuntu 20.4 Lenovo

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

Bug description:
  After installing Ubuntu 20.4 Kernel 5.8, my touchpad does not work. I have a 
dualboot laptop and its working in Windows. And the USB mouse is also working 
in Ubuntu. I have listed the hardware in the terminal, but the touchpad is not 
listed. Tried to reinstall the driver, also not working. Have tried almost all 
suggested solutions currently mentioned on the internet, to no avail :-(
  I see you have numerous bugs related to this touchpad issue on your bug list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917013/+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 1918032] Re: Lenovo Ideapad 5 touchpad not responding and not in /proc/bus/input/devices

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Lenovo Ideapad 5 touchpad not responding and not in
  /proc/bus/input/devices

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

Bug description:
  touchpad does not respond to any input.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  6 20:44:04 2021
  InstallationDate: Installed on 2021-03-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1918032/+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 1910453] Re: Touchpad not recognized on Lenovo Laptop

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not recognized on Lenovo Laptop

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

Bug description:
  I was following the instructions in the following link:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#Some_general_work_flow_for_Triagers

  After entering xinput in the terminal the expected out did not appear.

  Release info:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Package version:
  unable to find package version according to the terminal output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  6 23:05:52 2021
  InstallationDate: Installed on 2021-01-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910453/+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 1923307] Re: trackpad wont work after ubuntu installation

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  trackpad wont work after ubuntu installation

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  ideapad 3 15IIL05
  model name: 81WE
  S/N : PF2EG8KR

  I just erased windows 10 off this laptop to replace with the latest
  version of Ubuntu LTS and as soon as i booted up Ubuntu the trackpad
  stopped working. i had to plug in a wireless mouse to continue
  installing Ubuntu. i ran a command in the terminal and my trackpad did
  not show up, but my logitech mouse did.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 10 08:24:03 2021
  InstallationDate: Installed on 2021-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1923307/+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 1912378] Re: Elan touchpad not working

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Elan touchpad not working

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

Bug description:
  The touch pad worked once and not sure what made it to work. But after that 
it just stopped working. The touchpad was not recognized by ubuntu till I 
edited default/grub added GRUB_CMD_LINUXDEFAULT="quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop"
  Which made the driver to be present now I can see it in xinput --list( wasn't 
present before )
  But now I still cant use the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jan 19 20:25:08 2021
  InstallationDate: Installed on 2021-01-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912378/+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 1921413] Re: Touchpad never worked

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad never worked

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Installed ubuntu for the first time and touchpad doesn't work. PC is
  Lenova V15IIL.

  Attached is cat /proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 25 16:55:08 2021
  InstallationDate: Installed on 2021-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1921413/+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 1922522] Re: Touchpad not detected on ASUS Q325UA

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not detected on ASUS Q325UA

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 20.04.2 LTS on my ASUS Q325UA, I could not use
  the touchpad. I plugged in a mouse and it worked afterwards, but when
  another user logged on, the touchpad functionality disappeared.

  I followed the guide:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection, and didn't get
  anything for touchpad after running cat /proc/bus/input/devices for
  the TouchPad.

  According to the article there seems to be a linux kernel error.

  Oddly enough, I keep getting a keyboard battery low message, and there
  is no barry-powered keyboard attached to this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  4 17:10:40 2021
  InstallationDate: Installed on 2021-02-26 (37 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1922522/+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 1920629] Re: My touchpad is not working at all since installation, (external mouse is working peoperly).

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  My touchpad is not working at all since installation,(external mouse
  is working peoperly).

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

Bug description:
  My touchpad is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 20 23:17:17 2021
  InstallationDate: Installed on 2021-03-15 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920629/+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 1926067] Re: [Fujitsu UH-X] track pad/touch pad is not detected

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  [Fujitsu UH-X] track pad/touch pad is not detected

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Laptop: Fujitsu UH-X, Intel I5-1135G7
  OS: Ubuntu 20.4
  Kernel: 5.8.0-50-generic
  The track pad is not detected
  xinput list:

   Virtual core pointer id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ CX 2.4G Receiver Consumer Control   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ CX 2.4G Receiver Mouse  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ CX 2.4G Receiverid=9[slave  
keyboard (3)]
  ↳ CX 2.4G Receiver System Control id=11   [slave  
keyboard (3)]
  ↳ FJ Camera: FJ Cameraid=13   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=14   [slave  
keyboard (3)]
  ↳ Intel HID 5 button arrayid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ CX 2.4G Receiver Consumer Control   id=17   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 18:12:47 2021
  InstallationDate: Installed on 2021-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926067/+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 1932994] Re: Touchpad not detected

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not detected

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

Bug description:
  My Elan Touchpad never worked on Ubuntu. I have an HP Pavilion laptop,
  and I have dualbooted Ubuntu 20.04 and Windows 10. I can use my
  touchpad to move the cursor around, but I can't click , right click or
  do anything else. On top of that, If I touch my touchpad, my external
  mouse faces the same issue  until I switch to text mode (`Ctrl + Alt +
  F7`) and then back to the GUI (`Ctrl + Alt + F2`). When I list the
  devices connected to my system, it doesn't even show up. My touchpad
  works perfectly fine on Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 19 11:46:29 2021
  InstallationDate: Installed on 2020-11-29 (202 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1932994/+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 1929422] Re: The touchpad doesn't work in my Laptop ThinkBook 15-IML with Ubuntu 20

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  The touchpad doesn't work in my Laptop ThinkBook 15-IML with Ubuntu 20

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

Bug description:
  I've executed a "cat /proc/bus/input/devices" and theres is not an entry for 
my devices.
  Reading at the wiki.ubuntu.com the suggestion is that the bug is in the kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 24 10:27:05 2021
  InstallationDate: Installed on 2021-05-20 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929422/+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 1926272] Re: Touhpad driver missing

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touhpad driver missing

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  I installed a fresh ubnutu 21.04 LTS , after installing there is no
  touchpad driver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 27 14:06:23 2021
  InstallationDate: Installed on 2021-04-17 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926272/+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 1925679] Re: Laptops Trackpad not working whilst using Linux but a normal mouse is

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Laptops Trackpad not working whilst using Linux but a normal mouse is

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ cat /proc/bus/input/devices
  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/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 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/input2
  U: Uniq=
  H: Handlers=event2 
  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/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
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/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input6
  U: Uniq=
  H: Handlers=rfkill kbd event6 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 10 0
  B: MSC=10

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

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

  I: Bus=0003 Vendor=0bda Product=57b3 Version=0321
  N: Name="VGA Webcam: VGA Webcam"
  P: Phys=usb-:00:12.0-1.4/button
  S: 
Sysfs=/devices/pci:00/:00:12.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0003 Vendor=046d Product=c018 Version=0111
  N: Name="Logitech Logitech USB Optical Mouse"
  P: Phys=usb-:00:12.0-1.1/input0
  S: 
Sysfs=/devices/pci:00/:00:12.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C018.0001/input/input10
  U: Uniq=
  H: Handlers=mouse0 event10 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: fail
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 22 20:41:10 2021
  LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1925679/+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 1930435] Re: [Lenovo slim 3] Cannot use touchpad

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  [Lenovo slim 3] Cannot use touchpad

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  I dual booted my laptop lenovo slim 3 and with the dual boot, my
  touchpad is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  1 23:32:29 2021
  InstallationDate: Installed on 2021-06-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1930435/+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 1933824] Re: Touchpad not detected in ASUS-TUF-Gaming-F15-FX506HM

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Touchpad not detected in ASUS-TUF-Gaming-F15-FX506HM

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Touchpad is not being detected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 16:39:26 2021
  InstallationDate: Installed on 2021-06-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933824/+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 1931787] Re: Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

** Description changed:

- After I recently replaced broken screen on HP Spectre x360 G2, keyboard and 
touchpad became irresponsive - but only after booting. Booting with old kernel 
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control 
(but one wants to see battery level so this hack is insufficient). Evidently, 
it is not  hardwear problem.
+ I recently replaced broken screen on HP Spectre x360 G2, and upgraded to 5.8 
(Ubuntu 20.04). Keyboard and touchpad became unresponsive - but only after 
booting. Booting with old kernel (e.g. 5.4.0-42) restored full control. Also, 
disabling acpi restored control (but one wants to see battery level indicator 
so this hack is insufficient). Evidently, it is not  a hardware problem.
  Works fine with external keyboard and mouse.
  
  A similar bug from previous distro:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125
  
  This issue, including my troubleshooting, is otherwise documented here:
  
https://askubuntu.com/questions/1345402/is-there-a-proper-solution-to-keyboard-and-mouse-not-working-after-boot-proble
+ 
+ 
+ 
+ Seems many others had similar issues with 20.04 upgrade - some with only 
touchpad issues. (Many now marked as duplicates)
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:15:43 2021
  InstallationDate: Installed on 2021-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Bug description:
  I recently replaced broken screen on HP Spectre x360 G2, and upgraded to 5.8 
(Ubuntu 20.04). Keyboard and touchpad became unresponsive - but only after 
booting. Booting with old kernel (e.g. 5.4.0-42) restored full control. Also, 
disabling acpi restored control (but one wants to see battery level indicator 
so this hack is insufficient). Evidently, it is not  a hardware problem.
  Works fine with external keyboard and mouse.

  A similar bug from previous distro:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125

  This issue, including my troubleshooting, is otherwise documented here:
  
https://askubuntu.com/questions/1345402/is-there-a-proper-solution-to-keyboard-and-mouse-not-working-after-boot-proble


  
  Seems many others had similar issues with 20.04 upgrade - some with only 
touchpad issues. (Many now marked as duplicates)



  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:15:43 2021
  InstallationDate: Installed on 2021-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931787/+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 1931787] Re: Keyboard/touchpad unresponsive after 5.8 upgrade

** Summary changed:

- Keyboard and touchpad absent after booting, but not before
+ Keyboard/touchpad unresponsive after 5.8 upgrade

** Summary changed:

- Keyboard/touchpad unresponsive after 5.8 upgrade
+ Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Title:
  Keyboard/touchpad unresponsive after 5.8/20.04 upgrade

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

Bug description:
  I recently replaced broken screen on HP Spectre x360 G2, and upgraded to 5.8 
(Ubuntu 20.04). Keyboard and touchpad became unresponsive - but only after 
booting. Booting with old kernel (e.g. 5.4.0-42) restored full control. Also, 
disabling acpi restored control (but one wants to see battery level indicator 
so this hack is insufficient). Evidently, it is not  a hardware problem.
  Works fine with external keyboard and mouse.

  A similar bug from previous distro:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125

  This issue, including my troubleshooting, is otherwise documented here:
  
https://askubuntu.com/questions/1345402/is-there-a-proper-solution-to-keyboard-and-mouse-not-working-after-boot-proble


  
  Seems many others had similar issues with 20.04 upgrade - some with only 
touchpad issues. (Many now marked as duplicates)



  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:15:43 2021
  InstallationDate: Installed on 2021-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931787/+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 1917120] Re: Cannot detech my laptop's touchpad

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  Cannot detech my laptop's touchpad

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 Focal cannot detect my laptop Lenovo V15-IIL touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 27 14:32:47 2021
  InstallationDate: Installed on 2021-02-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917120/+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 1917177] Re: HP Pavilion, trackpad stopped working.

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  HP Pavilion, trackpad stopped working.

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  The track pad was working fine, and suddlenly stopped working.

  I followed the instructions
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo and it
  suggested executing cat /proc/bus/input/devices but my trackpad
  doesn't appear.

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  
  apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 27 23:00:06 2021
  InstallationDate: Installed on 2020-12-13 (76 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917177/+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 1914917] Re: trackpad not recognised

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  trackpad not recognised

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  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/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=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 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/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 10 0
  B: MSC=10

  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/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

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

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

  I: Bus=0003 Vendor=1241 Product= Version=0100
  N: Name="HID 1241:"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:1241:.0001/input/input9
  U: Uniq=
  H: Handlers=mouse0 event9 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0003 Vendor=064e Product=9404 Version=0100
  N: Name="VGA Webcam: VGA Webcam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input10
  U: Uniq=
  H: Handlers=kbd event10 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Feb  7 11:15:17 2021
  InstallationDate: Installed on 2021-02-07 (0 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1914917/+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 1912851] Re: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  Dell 5530: Trackpad, wifi and thunderbolt screen stop working after
  upgrade from kernel v5.4 to v5.8

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

Bug description:
  After installing the v5.8 kernel, my laptop becomes unusable with
  multiple issues:

  * Trackpad stops working
  * External screen connected over USB-C stops working
  * Wifi stops working

  I collected the apport report to file and then rebooted in v5.4 to
  send it. On v5.4 this laptop is pretty stable with all three of the
  above working reliably.

  Interestingly, the USB hub itself in the monitor works fine because I
  can use the keyboard through the monitor.  It's only the graphics that
  stops working.  Screen stays off when I plug it in.

  I also noticed that the laptop screen runs in a different resolution
  rather than the one I selected while v5.4 was installed.  I run the
  screen at half-res to match the DPI of my external screen but it
  booted in full res so everything was tiny.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 22 20:50:57 2021
  InstallationDate: Installed on 2018-12-11 (773 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: Upgraded to focal on 2020-05-02 (265 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-10-15T09:26:41.949637

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+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 1931288] Re: Touchpad doesn't work in 'Ideapad 5 14ALC05' after OS installation restart.

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  Touchpad doesn't work in 'Ideapad 5 14ALC05' after OS installation
  restart.

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  Started Ubuntu 20.04.2 LTS installation right after receiving my new 'Lenovo 
Ideapad 5 14ALC05'.
  Everything worked fine during installation.
  However, after the installations restart, touchpad doesn't work at all.
  Keyboard and other peripherals like wireless mouse work fine.
  Running 'cat /proc/bus/input/devices' and 'xinput' it seems that the touchpad 
isn't recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  8 19:40:27 2021
  InstallationDate: Installed on 2021-06-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931288/+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 1910834] Re: touchpad not working. Never did.

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  touchpad not working. Never did.

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

Bug description:
  I read here: https://wiki.ubuntu.com/DebuggingTouchpadDetection
  That I should send you this:

  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=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/input4
  U: Uniq=
  H: Handlers=rfkill kbd event4 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=0737 Version=0111
  N: Name="Microsoft Compact Optical Mouse 500"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:045E:0737.0001/input/input5
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0003 Vendor=174f Product=1176 Version=0028
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  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/LNXVIDEO:00/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 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/input8
  U: Uniq=
  H: Handlers=event8 
  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/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=10"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=11"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
  U: Uniq=
  H: Handlers=event15 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=12"
  P: Phys=ALSA
  S:

[Kernel-packages] [Bug 1931787] Re: Keyboard and touchpad absent after booting, but not before

** Description changed:

- After I recently replaced broken screen on HP Spectre x360 G2, keyboard and 
touchpad became irresponsive - but only after booting. Booting with old kernel 
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control 
(but one wants to see battery level...). Evidently, it is not  hardwear problem.
+ After I recently replaced broken screen on HP Spectre x360 G2, keyboard and 
touchpad became irresponsive - but only after booting. Booting with old kernel 
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control 
(but one wants to see battery level so this hack is insufficient). Evidently, 
it is not  hardwear problem.
  Works fine with external keyboard and mouse.
  
  A similar bug from previous distro:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125
  
  This issue, including my troubleshooting, is otherwise documented here:
  
https://askubuntu.com/questions/1345402/is-there-a-proper-solution-to-keyboard-and-mouse-not-working-after-boot-proble
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:15:43 2021
  InstallationDate: Installed on 2021-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Keyboard and touchpad absent after booting, but not before

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

Bug description:
  After I recently replaced broken screen on HP Spectre x360 G2, keyboard and 
touchpad became irresponsive - but only after booting. Booting with old kernel 
(e.g. 5.4.0-42) restored full control. Also, disabling acpi restored control 
(but one wants to see battery level so this hack is insufficient). Evidently, 
it is not  hardwear problem.
  Works fine with external keyboard and mouse.

  A similar bug from previous distro:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125

  This issue, including my troubleshooting, is otherwise documented here:
  
https://askubuntu.com/questions/1345402/is-there-a-proper-solution-to-keyboard-and-mouse-not-working-after-boot-proble

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 13 13:15:43 2021
  InstallationDate: Installed on 2021-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931787/+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 1919282] Re: 'HP ImagePad' doesn't work at all in "HP Pavilion 15-p077TX Notebook" after ubuntu 20.04 installation

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  'HP ImagePad' doesn't work at all in "HP Pavilion 15-p077TX Notebook"
  after  ubuntu 20.04 installation

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Installed ubuntu 20.04 2 days ago. Touchpad is not working and is not
  present in devices list.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 16 12:25:03 2021
  InstallationDate: Installed on 2021-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1919282/+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 1919052] Re: touchpad stopped working after install

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  touchpad stopped working after install

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

Bug description:
  the touchpad stopped working after i installed kubuntu. laptop model#
  HP 15-ef1073od. thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Mar 13 19:12:38 2021
  InstallationDate: Installed on 2021-03-13 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1919052/+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 1916267] Re: Touchpad not detected HP 15s

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  Touchpad not detected HP 15s

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  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/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=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/input2
  U: Uniq=
  H: Handlers=sysrq kbd event2 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:0b/LNXVIDEO:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=046d Product=c077 Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:03:00.3-2/input0
  S: 
Sysfs=/devices/pci:00/:00:08.1/:03:00.3/usb1/1-2/1-2:1.0/0003:046D:C077.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=0003 Vendor=046d Product=c31c Version=0110
  N: Name="Logitech USB Keyboard"
  P: Phys=usb-:03:00.4-2/input0
  S: 
Sysfs=/devices/pci:00/:00:08.1/:03:00.4/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=046d Product=c31c Version=0110
  N: Name="Logitech USB Keyboard"
  P: Phys=usb-:03:00.4-2/input1
  S: 
Sysfs=/devices/pci:00/:00:08.1/:03:00.4/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=1f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 
677bfad9415fed 19ed6804400 1002
  B: REL=1040
  B: ABS=1
  B: MSC=10

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

  I: Bus=0019 Vendor= Product= Version=
  N: Name="HP WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  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-:03:00.3-3/button
  S: 
Sysfs=/devices/pci:00/:00:08.1/:03:00.3/usb1/1-3/1-3:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.1/:03:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.1/:03:00.6/sound/card1/input11
  U: Uniq=
  H: Handlers=event11 
  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/:03:00.6/sound/card1/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Feb 19 17:27:56 2021
  InstallationDate: Installed on 2021-02-19 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No

[Kernel-packages] [Bug 1924253] Re: Touchpad does not work. Not even detected. New computer.

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  Touchpad does not work. Not even detected. New computer.

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  I bought a new Laptop (Hp with AmD Ryzen 7). I assume (and hope) that
  all the other technical descriptions have been sent to you by the bug
  report.

  It did already happen in the installation medium (a flash key) and I
  couldn't resize the partitions, had to borrow a mouse from a friend to
  even install Ubuntu.

  I attach the output of < ~/devices>> as 
requested in this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  I don't know how to locate the exact package where the bug is or if is
  one of the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-49-generic 5.8.0-49.55~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 11:24:49 2021
  InstallationDate: Installed on 2021-04-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1924253/+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 1924873] Re: hp envy x360 mousepad and keyboard not working

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  hp envy x360 mousepad and keyboard not working

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  This is strange, i performed basic troubleshooting ,checking the
  xinput devices within xinput ,everthing is there, tried everything
  still not working, mouse and keypad not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 15:29:05 2021
  InstallationDate: Installed on 2021-04-13 (4 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1924873/+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 1919316] Re: touchpad driver is not being detected. so touchpad of hp pavillion not working

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

** This bug has been marked a duplicate of bug 1931787
   Keyboard and touchpad absent after booting, but not before

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

Title:
  touchpad driver is not being detected. so touchpad of hp pavillion not
  working

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

Bug description:
  I recently installed ubuntu on system and touchpad worked before
  restart. After restart, it stopped working, so i edited the file
  /etc/default/grub a bit and touchpad started working. But later on
  again after some 2 hours, when i started my system, touchpad was not
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 16 17:28:27 2021
  InstallationDate: Installed on 2021-03-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1919316/+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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2020-06-27 Thread Owen Williams

Also seeing the same behavior on 20.04

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1722478/+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 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4

2019-12-10 Thread Owen

Command run and status set to Confirmed as requested

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

** Changed in: network-manager (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/1855297

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1855297/+attachment/5311416/+files/Dependencies.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/1855297

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1855297/+attachment/5311415/+files/ProcEnviron.txt

** Description changed:

  Ubuntu 20.04
  
  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  
  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see that
  the Wi-fi had connected but the Ethernet connection was "obtaining IP
  address" --> fail --> back to "obtaining IP address" and continually
  going around and around.
  
  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.
  
  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.
  
  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu13
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2017-12-06 (734 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: network-manager 1.20.4-2ubuntu3
+ PackageArchitecture: amd64
+ Tags:  focal
+ Uname: Linux 5.4.2-050402-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
+ _MarkForUpload: True

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

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package:

[Kernel-packages] [Bug 1855297] ProcEnviron.txt

apport information

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

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

apport information

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

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4

apport information

** Tags added: apport-collected

** Description changed:

  Ubuntu 20.04
  
  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  
  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see that
  the Wi-fi had connected but the Ethernet connection was "obtaining IP
  address" --> fail --> back to "obtaining IP address" and continually
  going around and around.
  
  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.
  
  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.
  
  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu13
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2017-12-06 (734 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: network-manager 1.20.4-2ubuntu3
+ PackageArchitecture: amd64
+ Tags:  focal
+ Uname: Linux 5.4.2-050402-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1855297/+attachment/5311413/+files/Dependencies.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/1855297

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING

[Kernel-packages] [Bug 1855297] ProcCpuinfoMinimal.txt

apport information

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

Title:
  NetworkManager service fails to secure Ethernet connection when using
  kernel 5.4

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
   *** 1.20.4-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  After going to kernel 5.4, from 5.3, I noticed the network systray
  roundel going 'round and 'round. On closer examination I could see
  that the Wi-fi had connected but the Ethernet connection was
  "obtaining IP address" --> fail --> back to "obtaining IP address" and
  continually going around and around.

  Doing a "service NetworkManager stop" and quickly following up with
  "service NetworkManager start" fixes the situation. However, if you
  leave any kind of a gap between the stop and start the issue described
  above starts up again.

  I also left a freshly booted system for quite a while and went back to
  it but the issue was still there, until the workaround described above
  was performed.

  Booting up in to kernel 5.3 the issue is not seen and all network
  interfaces connect as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  Uname: Linux 5.4.2-050402-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  5 15:24:51 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-06 (729 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-06 (734 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.20.4-2ubuntu3
  PackageArchitecture: amd64
  Tags:  focal
  Uname: Linux 5.4.2-050402-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1816342] [NEW] Dmesg showing errors PCIE device?

2019-02-17 Thread Owen Pimm

Public bug reported:

ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND 
(20170831/dswload2-191)
and 
ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
and
ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND 
(20170831/psparse-550)
and 
ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND 
(20170831/dswload2-191)
and
ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
and
ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND 
(20170831/psparse-550)

GRUB manually configured using 'nomodeset' option otherwise massive
issues with PCI bus failures in Dmesg.  Info found in web search for
earlier problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-46-generic 4.15.0-46.49
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  shinfield   2027 F pulseaudio
 /dev/snd/controlC2:  shinfield   2027 F pulseaudio
 /dev/snd/controlC0:  shinfield   2027 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 18 17:12:12 2019
InstallationDate: Installed on 2018-08-07 (194 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 lono wireless extensions.
 
 enp0s31f6  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer 
vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-46-generic N/A
 linux-backports-modules-4.15.0-46-generic  N/A
 linux-firmware 1.173.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
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.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

Title:
  Dmesg showing errors PCIE device?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND 
(20170831/dswload2-191)
  and 
  ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  and
  ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND 
(20170831/psparse-550)
  and 
  ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND 
(20170831/dswload2-191)
  and
  ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  and
  ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND 
(20170831/psparse-550)

  GRUB manually configured using 'nomodeset' option otherwise massive
  issues with PCI bus failures in Dmesg.  Info found in web search for
  earlier problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shinfield   2027 F pulseaudio
   /dev/snd/controlC2:  shinfield   2027 F pulseaudio
   /dev/snd/controlC0:  shinfield   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 17:12:12 2019
  InstallationDate: Installed on 2018-08-07 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

2019-02-17 Thread Owen Williams

I'd like the second the suggestion that s2idle sleep not be used at
least on this model until the power usage issues have been worked out.
It wasn't easy to figure out what the problem was and the battery drain
will significantly reduce the lifespan of the laptop for users that
don't know to change the setting.

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

Title:
  Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems that the Dell 9370 is set to go into s2idle mode rather than
  deep sleep, forgoing significant power savings.

  I have confirmed this by suspending and then checking:
  sudo journalctl | grep "PM: suspend" | tail -2. If the output is

  PM: suspend entry (s2idle)
  PM: suspend exit

  cat /sys/power/mem_sleep showed

  [s2idle] deep

  As a temporary fix, I typed 
  echo deep > /sys/power/mem_sleep 
  as a root user (sudo -i). 

  Then the output of cat /sys/power/mem_sleep was
  s2idle [deep]

  After suspending now, 
  sudo journalctl | grep "PM: suspend" | tail -2 returns

  PM: suspend entry (deep)
  PM: suspend exit

  I have made this permanent by editing 
  /etc/default/grub

  and replacing
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

  then regenerating my grub configuration (sudo grub-mkconfig -o
  /boot/grub/grub.cfg).

  This appears to be working with no ill effects.

  Credit to https://askubuntu.com/a/1036122/470077

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   3672 F pulseaudio
   /dev/snd/pcmC0D0p:   aaron-work   3672 F...m pulseaudio
  Date: Tue Dec 18 09:52:44 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
  InstallationDate: Installed on 2018-09-04 (104 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1814393] Re: "make: write error: stdout" on parallel builds

2019-02-07 Thread Mark Owen

I'm running 16.04 and seeing the same problem on Linux 4.15.0-45. I can
also confirm that when booting with 4.15.0-43 I no longer see the
problem.

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

Title:
"make: write error: stdout" on parallel builds

Status in linux-signed package in Ubuntu:
Confirmed

Bug description:
- Release of Ubuntu: 18.04.1 LTS (Kubuntu).
- Package version: linux-image-4.15.0-44-generic,
linux-image-4.15.0-45-generic.
- Expected outcome: Large parallel make build completing properly.
- What happened instead: Build stops with "make: write error: stdout".

Full explanation:

Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic)
in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop
during large parallel builds of source code (eg: a buildroot full
rebuild for a work project). Note that this reports isn't about kernel
builds, but about large project builds in general.

I don't think it's relevant, but I'm running those builds in an
schroot with the same Ubuntu Bionic distro I'm also using as main host
distro.

The specific error I get is this (in Spanish):

make[4]: error al escribir: stdout

I call Buildroot's make like this from KDE Konsole with "infinite
history buffer" enabled (uses a tmp file to store the logs):

V=1 make ...some stuff... 2>&1

However, the error is reproducible in Konsole even if I call make
without options and also if I use "limited (in-memory) history buffer"
as well as "no history buffer". Buildroot autoselects a
parallelization level (-j) automatically. In my case, I'm using a Xeon
E-2176 CPU with 12 threads.

Searching on the Internet I found a thread[1] where people from the
GNU Make project say that the error may be coming from the C runtime
library (and I suspect originating from the kernel).

I can NOT reproduce the issue on linux-image-4.15.0-43-generic
(selected from grub at boot), but I experience it with linux-
image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why
I'm reporting this bug against the linux package.

Interestingly enough, I can NOT reproduce the issue on linux-
image-4.15.0-45-generic (haven't tried previous versions) when
building from xterm instead of Konsole. Unfortunately, this laptop has
a 4K screen and xterm isn't an option for me.

If I build redirecting stdout and stderr to different files to avoid
terminal output and then watching the stdout file with tail -f, the
tail command eventually finishes although the build continues and I
can keep watching it by running tail again. An infinite build loop
never finishes with this redirection (error not reproducible). Same
results with the 2>&1 redirection to a single file.

All this looks a bit like a poltergeist, but the only thing I'm sure
about is that it all started with the upgrade from 4.15.0-43 to -44
and it continues on -45.

Thank you.

[1]
http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1814393/+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 1765980] Re: IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock upon LXD container shutdown

2018-11-02 Thread Owen Valentine

This has expired, but affects me too here.
I'm specifically using Proxmox, which uses Ubuntu for upstream kernel - 
currently at 4.15.18, and I see the same symptoms.
Specifically LXC, specifically at stop and specifically kworker using 100% of 
one core and preventing startup of other containers.
I've found that this isn't present in Proxmox's own kernel 4.15.10-1 
specifically.

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

Title:
  IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
  upon LXD container shutdown

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired

Bug description:
  I've spent the last few days tracking down an issue where an attempt
  to shutdown an LXD container after several hours of host uptime on
  Ubuntu Bionic (4.15.0-15.16-generic) would cause a kworker thread to
  start spinning on one CPU core and all subsequent container start/stop
  operations to fail.

  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex
  and therefore blocks any further container start/stops. That in turn
  is triggered by receiving a fragmented IPv6 MDNS packet in my
  instance, but it could probably be triggered by any fragmented IPv6
  traffic.

  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.

  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
  There is already a comment saying "It is not generally safe to change 
skb->truesize." right above the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765980/+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 1790254] Re: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned

2018-09-09 Thread Owen Pimm

Unconfirmed.

The above terminal commands have fixed the issue.  Please close this BUG report.
Many thanks for the help.

Regards

Owen Pimm

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

Title:
  package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to
  install/upgrade: installed linux-image-4.15.0-34-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error from previous linux-image manual removal.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio 
snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo 
videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 
videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof 
intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sat Sep  1 13:51:45 2018
  ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-08-07 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to 
install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  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.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  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/1790254/+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 1790254] [NEW] package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess return

2018-08-31 Thread Owen Pimm

Public bug reported:

Error from previous linux-image manual removal.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio 
snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo 
videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 
videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof 
intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Sat Sep  1 13:51:45 2018
ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-08-07 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 enp0s31f6  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer 
vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to 
install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
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.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to
  install/upgrade: installed linux-image-4.15.0-34-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error from previous linux-image manual removal.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio 
snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo 
videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 
videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof 
intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sat Sep  1 13:51:45 2018
  ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-08-07 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-14 Thread Jason Owen

The original bug title was '15:10: bluetoothd reports "Not enough
handles to register service" at start', and the original bug description
described both the "Not enough free handles to register service" problem
and the "Failed to start discovery" problem[1]. Between #47 and #48, the
title and description were changed to focus on the "Failed to start
discovery" problem.

It seems to me that most of the people in the thread are focused on the
"Not enough free handles to register service", and aside from the close
message in #48, the only mention of the "Failed to start discovery"
problem was in the original description. Perhaps it would be useful to
split the "Failed to start discovery" problem off into its own bug and
keep this bug focused on "Not enough free handles to register service"?
That way the history and relevant log files are all kept in one place,
subscribers won't have to subscribe to another bug, and links pointing
to this bug for the "Not enough free handles to register service"
problem won't need to be updated.

[1]
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/comments/0

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

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1613696] Re: Several keys on Logitech keyboard not recognized

2016-08-16 Thread Owen

Traced it down to a hardware problem. There was dirt between the key's
rubber padding and the main board. For some reason, after cleaning the
'home' key the others sprang back into life.

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

** Tags removed: kernel-bug-exists-upstream keyboard

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

Title:
  Several keys on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  Upon testing other keys under xev I have discovered that the 'F5',
  'F7' and 'F9' function keys are also not recognized.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1613696/+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 1613696] Re: Several keys on Logitech keyboard not recognized

2016-08-16 Thread Owen

Confirmed the bug exists in the 4.8-rc2 kernel. There are 4 keys not
working 'F5', 'F7', 'F9' and 'Home'.

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

Title:
  Several keys on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  Upon testing other keys under xev I have discovered that the 'F5',
  'F7' and 'F9' function keys are also not recognized.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1613696/+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 1613696] Re: Several keys on Logitech keyboard not recognized

2016-08-16 Thread Owen

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

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

Title:
  Several keys on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  Upon testing other keys under xev I have discovered that the 'F5',
  'F7' and 'F9' function keys are also not recognized.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1613696/+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 1613696] Re: Several keys on Logitech keyboard not recognized

2016-08-16 Thread Owen

** Tags added: kernel-bug-exists-upstream

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

Title:
  Several keys on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  Upon testing other keys under xev I have discovered that the 'F5',
  'F7' and 'F9' function keys are also not recognized.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1613696/+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 1613696] Re: Home key on Logitech keyboard not recognized

2016-08-16 Thread Owen

** Description changed:

  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.
+ 
+ Upon testing other keys under xev I have discovered that the 'F5', 'F7'
+ and 'F9' function keys are also not recognized.
  
  This bug was not present in the previous 14.04/10 versions of Ubuntu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.
  
   tun0  no wireless extensions.
  
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Summary changed:

- Home key on Logitech keyboard not recognized
+ Several keys on Logitech keyboard not recognized

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

Title:
  Several keys on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  Upon testing other keys under xev I have discovered that the 'F5',
  'F7' and 'F9' function keys are also not recognized.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.

[Kernel-packages] [Bug 1613696] Re: Home key on Logitech keyboard not recognized

2016-08-16 Thread Owen

** Tags added: keyboard

** Description changed:

  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.
+ 
+ This bug was not present in the previous 14.04/10 versions of Ubuntu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  owen   2997 F pulseaudio
-  /dev/snd/controlC1:  owen   2997 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  owen   2997 F pulseaudio
+  /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  tun0  no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  tun0  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
+  linux-restricted-modules-4.4.0-34-generic N/A
+  linux-backports-modules-4.4.0-34-generic  N/A
+  linux-firmware1.157.3
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System 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/1613696

Title:
  Home key on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  New

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  This bug was not present in the previous 14.04/10 versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.

   tun0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi

[Kernel-packages] [Bug 1613696] [NEW] Home key on Logitech keyboard not recognized

2016-08-16 Thread Owen

Public bug reported:

Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
when pressed. This is confirmed when running the 'xev' utility and
pressing the 'home' key, xev does associate any events with the key.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  owen   2997 F pulseaudio
 /dev/snd/controlC1:  owen   2997 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 16 20:31:31 2016
HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
InstallationDate: Installed on 2016-08-07 (9 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 enp2s0no wireless extensions.
 
 tun0  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
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
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78LT-LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

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

Title:
  Home key on Logitech keyboard not recognized

Status in linux package in Ubuntu:
  New

Bug description:
  Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
  4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
  when pressed. This is confirmed when running the 'xev' utility and
  pressing the 'home' key, xev does associate any events with the key.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owen   2997 F pulseaudio
   /dev/snd/controlC1:  owen   2997 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 16 20:31:31 2016
  HibernationDevice: RESUME=UUID=6701279e-edc4-4f37-be68-dd07289681ef
  InstallationDate: Installed on 2016-08-07 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp2s0no wireless extensions.
   
   tun0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d4fa8ca8-d7ff-4cb7-8be1-2141c9ff5f4a ro quiet splash vt.handoff=7
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To

[Kernel-packages] [Bug 1527748] Re: lts-utopic kernel needs boot-up race condition fix.

2015-12-18 Thread Owen Hofmann

It looks like the patch backported for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609 is not
quite enough to fix this issue on pre-4.1 kernels. Those kernels also
need
https://github.com/torvalds/linux/commit/00df35f991914db6b8bde8cf09808e19a9cffc3d
(or in general, must call cpu_notify before smpboot_unpark_threads).

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

Title:
  lts-utopic kernel needs boot-up race condition fix.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The underlying kernel bug was originally reported and fixed here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

  The bug was fixed confirmed not present in the original trusty kernel
  and has been fixed in vivid and wily, but was not addressed in utopic
  as it has EOL.

  If my understanding is correct, while Utopic has EOL, the lts-utopic
  hwe kernel is expected to be supported until the final Trusty release
  (14.04.05) next summer.  Can we have the original kernel issue also
  addressed in lts-utopic (assuming it hasn't been already?).  We are
  seeing users running this kernel on trusty systems and they still
  appear to be affected.

  Thanks!

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

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] ProcCpuinfo.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] Re: ctrl-alt-f1 has no effect

apport information

** Tags added: apport-collected

** Description changed:

  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I attempt
  to drop to terminal, as X must be off before I can do the install, I
  used ctrl-alt-f1 but nothing happens.
  
  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the boot-
  up sequence and can not type.  I can use ctrl-alt-delete to reboot once
  I am there but nothing else seems to work.
  
  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.
  
  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.
  
  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  nathan 1754 F pulseaudio
+  /dev/snd/controlC0:  nathan 1754 F pulseaudio
+ DistroRelease: Ubuntu 15.10
+ HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
+ InstallationDate: Installed on 2015-10-24 (33 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ IwConfig:
+  enp11s0   no wireless extensions.
+  
+  lono wireless extensions.
+  
+  enp10s0   no wireless extensions.
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.2.0-18-generic N/A
+  linux-backports-modules-4.2.0-18-generic  N/A
+  linux-firmware1.149.2
+ RfKill:
+  
+ Tags:  wily
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.2.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: dialout
+ _MarkForUpload: True
+ dmi.bios.date: 03/13/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 3505
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P8Z77 WS
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu

[Kernel-packages] [Bug 1520059] Re: ctrl-alt-f1 has no effect

'sudo chvt 2' does produce the desired effect. 
I can use this solution to get around the issue however this does not resolve 
this bug.

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1520059/+attachment/4526256/+files/Lsusb.txt

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] ProcModules.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] Lspci.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] CurrentDmesg.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] UdevDb.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1520059/+attachment/4526261/+files/WifiSyslog.txt

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

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1520059/+attachment/4526254/+files/JournalErrors.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/1520059

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1520059] ProcInterrupts.txt

apport information

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

Title:
  ctrl-alt-f1 has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working in a stable install of Ubuntu 15.10.  Everything seems to
  be working fine but I needed to install nvidia drivers.  When I
  attempt to drop to terminal, as X must be off before I can do the
  install, I used ctrl-alt-f1 but nothing happens.

  I have rebooted multiple times and updated but this has had no effect.
  If I kill X manually I am dropped to something that looks like the
  boot-up sequence and can not type.  I can use ctrl-alt-delete to
  reboot once I am there but nothing else seems to work.

  ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on
  my desktop PC running 15.10.

  Expected Results:
  ctrl-alt-f1 should drop me into a terminal where I can login.

  Actual Results:
  ctrl-alt-f1 does nothing, and system continues to operate in normal unity 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 25 21:45:43 2015
  InstallationDate: Installed on 2015-10-24 (32 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nathan 1754 F pulseaudio
   /dev/snd/controlC0:  nathan 1754 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=eeb80f75-98df-45be-bcf6-7b5852957530
  InstallationDate: Installed on 2015-10-24 (33 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp11s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=2162cfe8-4d93-4080-8662-5eda31cef0a4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3505:bd03/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77WS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  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/1520059/+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 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.

2015-10-15 Thread Owen

I have the exact same problem as him

"I have the same problem in HP 14-ab019la..

"tap to click, right click, and left click work. Mutitouch, disable
touchpad with keyboard activity, as well as sensitivity settings don't
work.

Trackpad, via xinput, detect as a "PS/2 Elantech Touchpad"

dmesg | grep psmouse results:
  psmouse: module verification failed: signature and/or required key 
missing - tainting kernel
  psmouse serio1: elantech: unknown hardware version, aborting..." "

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

Title:
  Elantech clickpad/touchpad lacks multitouch features.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux package in Arch Linux:
  New

Bug description:
  Newer versions of the Elantech multitouch trackpad are not fully
  supported in Linux.  These appear in many of the newer Samsung
  laptops, for example.  elantech.c in the kernel needs to be updated to
  support these models (up to v7 perhaps?)

  This bug is confirmed to affect a range of samsung laptops running
  Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current
  (3.9) upstream kernel.

  A dkms package was produced in 2011 (see
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64) which may fix certain older laptops
  affected by this issue, but doesn't fix newer models.

  == Original Report ==

  Hello,

  So far I've been having a problem with my Elantech multitouch trackpad in 
Linux. Basically all i get is right click, left click, and tap to click, along 
with basic  movement. The problem seems to be rooted in improper detection of 
the trackpad, likely b/c its a new revision or whatnot. Of note is that working 
elantech trackpads of the past in forums i scouted through show up as "ETPS/2 
Elantech Touchpad". Mine just shows up in xinput as "PS/2 Elantech Touchpad". I 
think this might be a simple fix in the end, just improper detection, I hope. 
For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on 
Ubuntu 13.04 thus far, with all combinations of psmouse.
  
--
  What's expected: touchpad multitouch support
  What happened: basic touchpad support
  Laptop mode: Samsung Series 7 NP780 series
  Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04
  Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed
  Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and 
psmouse-alps-dst. No improvements so removed.

  synclient -l reports "Couldn't find synaptics properties. No synaptics driver 
loaded?"
  
--
  See attached for more info. Ask anything you need!
  ---
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gscoppino   2272 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d
  InstallationDate: Installed on 2013-04-06 (3 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed 
root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.104
  StagingDrivers: rts5139
  Tags:  raring staging
  Uname: Linux 3.8.0-17-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03ABU.139.130226.SK
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP780Z5E-S01UB
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias:

Re: [Kernel-packages] [Bug 1457852] Re: Optiplex 9020 reboots rather than shutting down if USB3 enabled

2015-05-27 Thread Owen Dunn

Email to linux-usb mailing list:

http://permalink.gmane.org/gmane.linux.usb.general/126171

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

Title:
  [Dell Optiplex 9020] Shut down causes restart if USB3 enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457852/+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 1457852] Re: Optiplex 9020 reboots rather than shutting down if USB3 enabled

2015-05-26 Thread Owen Dunn

On Sat, 23 May 2015, Christopher M. Penalver wrote:

 Owen Dunn, thank you for reporting this and helping make Ubuntu better.
 As per http://www.dell.com/support/home/us/en/19/product-
 support/product/optiplex-9020-desktop/drivers an update to your
 computer's buggy and outdated BIOS is available (A10). If you update to
 this following https://help.ubuntu.com/community/BIOSUpdate does it
 change anything?

No, this doesn't change anything.  The system still starts up again a 
second or two after it shuts down.

 If it doesn't, could you please both specify what happened, and provide the 
 output of the following terminal command:
 sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

root@cayenne:/home/osd1000# dmidecode -s bios-version
A10
root@cayenne:/home/osd1000# dmidecode -s bios-release-date
01/08/2015

Owen


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

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1457852] Re: Optiplex 9020 reboots rather than shutting down if USB3 enabled

2015-05-26 Thread Owen Dunn

On Tue, 26 May 2015, Christopher M. Penalver wrote:

 Once you've tested the upstream kernel, please comment on which kernel 
 version specifically you tested.

I tested with 4.1.0-040100rc5, and this has not resolved the problem. 
When the system is shut down, the system powers back shortly afterwards.

Owen


** Tags added: kernel-bug-exists-upstream 
kernel-bug-exists-upstream-4.1.0-040100rc5

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457852/+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 1457852] Re: Optiplex 9020 reboots rather than shutting down if USB3 enabled

2015-05-26 Thread Owen Dunn

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

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457852/+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 1457852] [NEW] Optiplex 9020 reboots rather than shutting down if USB3 enabled

Public bug reported:

Description:Ubuntu 14.04.2 LTS
Release:14.04

linux-image-3.13.0-49-generic version 3.13.0-49.83

I have a large number of Dell Optiplex 9020 machines, and when they are
asked to shutdown with e.g. shutdown -h now, they shut down successfully
and then approximately four seconds later they start up again.

This problem only happens if the system's USB3 ports are enabled.

If I reinstate the code removed from xhci-pci.c in the diff.gz:

if (pdev-vendor == PCI_VENDOR_ID_INTEL 
-   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
-pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
-   /* Workaround for occasional spurious wakeups from S5 (or
-* any other sleep) on Haswell machines with LPT and LPT-LP
-* with the new Intel BIOS
-*/
-   /* Limit the quirk to only known vendors, as this triggers
-* yet another BIOS bug on some other machines
-* https://bugzilla.kernel.org/show_bug.cgi?id=66171
-*/
-   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
-   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
+   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
+   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
}

and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
threads.com/lists/linux/kernel/1713011

...shutdown shuts the machine down as expected.

I attach the output of lspci -mnn.

(S)

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

** Attachment added: lspci -mnn  lspci.txt
   https://bugs.launchpad.net/bugs/1457852/+attachment/4402307/+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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)

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

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402432/+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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402435/+files/WifiSyslog.txt

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

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402430/+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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402434/+files/UdevLog.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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402424/+files/BootDmesg.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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402429/+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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1457852/+attachment/4402428/+files/Lsusb.txt

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

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1457852/+attachment/4402431/+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/1457852

Title:
  Optiplex 9020 reboots rather than shutting down if USB3 enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  linux-image-3.13.0-49-generic version 3.13.0-49.83

  I have a large number of Dell Optiplex 9020 machines, and when they
  are asked to shutdown with e.g. shutdown -h now, they shut down
  successfully and then approximately four seconds later they start up
  again.

  This problem only happens if the system's USB3 ports are enabled.

  If I reinstate the code removed from xhci-pci.c in the diff.gz:

  if (pdev-vendor == PCI_VENDOR_ID_INTEL 
  -   (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
  -pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
  -   /* Workaround for occasional spurious wakeups from S5 (or
  -* any other sleep) on Haswell machines with LPT and LPT-LP
  -* with the new Intel BIOS
  -*/
  -   /* Limit the quirk to only known vendors, as this triggers
  -* yet another BIOS bug on some other machines
  -* https://bugzilla.kernel.org/show_bug.cgi?id=66171
  -*/
  -   if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
  -   xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
  +   pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
  +   xhci-quirks |= XHCI_SPURIOUS_REBOOT;
  }

  and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
  threads.com/lists/linux/kernel/1713011

  ...shutdown shuts the machine down as expected.

  I attach the output of lspci -mnn.

  (S)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lightdm1990 F pulseaudio
   /dev/snd/controlC0:  lightdm1990 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-49-generic N/A
   linux-backports-modules-3.13.0-49-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: wheel
  _MarkForUpload: True
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457852/+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 1457852] Re: Optiplex 9020 reboots rather than shutting down if USB3 enabled