[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

[Daniel van Vugt]

Ah, yes. Sorry but your bug 1726600 is a duplicate of bug 1505409. And I
think this one is different to those two. It just means the wrong .crash
file was sent...

Please try following the steps in #15 again, or repeatedly, and we'll
see if we can find an instance of this one.

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-30 (71 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Tags:  artful wayland-session
  Uname: Linux 4.8.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697450/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Anthony M.]

This bug affects the following Acer model as well (I've confirmed it as
of now, please add it to the affected models list):

Acer Swift SF314-52

I've installed the kernel 4.14.9 and can confirm that the USB Boot
option is still unavailable. I'll try to install 4.15 and get back to
you.

** Description changed:

  Description: An update to linux kernel on Ubuntu 17.10 that enabled the
  intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings
  being not stored, USB Boot impossible and EFI entries read-only.
  
  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.
  
  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux
  and BIOS should be restored to a working state.
  
  ---
  
  Test Case: Fix has been verified by our HWE team on affected hardware.
  
  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.
  
  ---
  
  Affected Machines:
  
  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY
  
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
+ Acer Swift SF314-52
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la
  
  ---
  
  Original Description:
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Acer Swift SF314-52
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1663727] Re: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

[Kai-Heng Feng]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Radeon

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

Title:
  16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just performed an "apt-get update" on a Dell 2950 Server - which
  was already running 16.04.1 and now it's spewing EDID errors - I'm not
  sure what changed from 16.04.1 to 16.04.2..

  I've attached dmesg to this, but basically it's dumping the following
  in logs and to the screen.

  [drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but 
no|invalid EDID
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 10 13:51 seq
   crw-rw 1 root audio 116, 33 Feb 10 13:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=97c6470f-0ecf-4fda-8400-9dcded48500c
  InstallationDate: Installed on 2014-04-18 (1034 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. PowerEdge 2950
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=089f7527-5b99-4ebc-9092-cd4461eebeb9 ro
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-62-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-25 (206 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/30/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.0
  dmi.board.name: 0H603H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.0:bd10/30/2010:svnDellInc.:pnPowerEdge2950:pvr:rvnDellInc.:rn0H603H:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge 2950
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663727/+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 1685937] Re: HID 1018:1006 Touchpad does not work

[Kai-Heng Feng]

Then it behaves like a mouse - you lose features like scroll/multitouch.

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

Title:
  HID 1018:1006 Touchpad does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad does not work. hid_multitouch interprets gestures as weird stuff 
-> opens search, types letters. If I didnt overlook anything the touchpad 
position does not show in any of the /dev/input files.. Any help would be 
appreciated.
  edit:  its on a trekstor surfbook w2.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 24 23:05:18 2017
  MachineType: TrekStor SurfBook W2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=78342794-9ef5-4a63-9b1e-040a63fd644b ro i8042.nopnp quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.version: SB14464-2_BIOS_V2.1.1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CherryTrail CR
  dmi.board.vendor: TS_I-Net
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvn:bvrSB14464-2_BIOS_V2.1.1:bd11/22/2016:svnTrekStor:pnSurfBookW2:pvrType1-TBDbyOEM:rvnTS_I-Net:rnCherryTrailCR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: SurfBook W2
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: TrekStor

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

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

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Kai-Heng Feng]

Yes. 
Asmedia folks are working a workaround for this issue.
I'll poke around to see if there's any timeline.

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1740536] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1740536

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

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

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

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

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

Title:
  Macbook Air Will not Sleep Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Macbook Air with Ubuntu 16.04 installed will not sleep/susped when lid
  is closed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740536/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

[Kai-Heng Feng]

Does this system have hardware clock?

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

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

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

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Leó Kolbeinsson]

Re: #420

Tried the mainline in your link (4.15RC6) with no change for Acer Aspire
E3 - 111 with Insyde Bios.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1740536] Re: Macbook Air Will not Sleep Ubuntu 16.04

[Kai-Heng Feng]

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

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

Title:
  Macbook Air Will not Sleep Ubuntu 16.04

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Macbook Air with Ubuntu 16.04 installed will not sleep/susped when lid
  is closed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740536/+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 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Kai-Heng Feng]

Please try latest mainline kernel in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.15-rc6/

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

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD
  Graphics 520, connecting an external monitor to the DisplayPort
  connector causes the system to quickly hang. The system stops
  responding to network pings, cannot switch consoles, and needs a hard
  reboot.

  The external monitor does work when using a text console, and does not
  always hang in the LightDM login screen, but starting up a desktop
  session will always hang.

  This originally happened using a ThinkPad dock, and I tested it
  further using an external DP monitor. This happens on 4.4.0-28-generic
  as well as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic;
  they all hang in a similar fashion.

  I have attached a journalctl log from running 4.7.0-040700rc5-generic
  and connecting the DP monitor while in a text console, before
  switching to the graphical console and logging in. The system hangs
  after a series of:

  kernel: WARNING: CPU: 3 PID: 2319 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3647 
skl_update_other_pipe_wm+0x15d/0x170 [i915]
  kernel: WARNING: CPU: 3 PID: 4418 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 
skl_max_scale.part.108+0x69/0x70 [i915]
  kernel: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

  The first warnings come immediately when connecting, and others when
  switching consoles and logging in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  terom  1903 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 29 13:03:18 2016
  InstallationDate: Installed on 2016-06-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20F6007RGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=6636a3bb-262e-4ab2-ae81-d9388e3f7684 ro rootflags=subvol=@ quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6007RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6007RGE:pvrThinkPadX260:rvnLENOVO:rn20F6007RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6007RGE
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597267/+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 1716009] Re: problem with the sound since the latest update

[Kai-Heng Feng]

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

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

Title:
  problem with the sound since the latest update

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716009/+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 1740163] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1740163

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

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

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

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

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

Title:
  Lost internet connecting after waking up from suspend

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

Bug description:
  I lose internet after resuming from suspended state. The network
  applet shows that I am successfully and currently connected but alas
  pinging google all the packets fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 19:04:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-20 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.0.1 dev wlp4s0 proto static metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.80 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
1429809 2a1b6b8a-314e-4099-9761-124a5acac6ce  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   cdc-wdm0   gsm   unavailable  /org/freedesktop/NetworkManager/Devices/4  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740163/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kai-Heng Feng]

Please try the mainline Linux kernel with intel-spi enabled:

http://people.canonical.com/~khfeng/linux-4.15-intel-spi/

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1634593] Re: Elantech Touchpad detects as PS/2 BYD TouchPad or as a PS/2 generic mouse

[Kai-Heng Feng]

Please run `apport-collect 1634593`

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

Title:
  Elantech Touchpad detects as PS/2 BYD TouchPad or as a PS/2 generic
  mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Elantech Touchpad installed on my Lenovo Y700 laptop and I
  can't make it work properly by any means. I tried to switch between
  libinput and synaptics but this bug seems to affect any driver.

  Usually, after a system upgrade all works properly till the moment I
  plug in external mouse (Razer DeathAdder 3500DPI). After that touchpad
  detected as either PS/2 BYD or PS/2 generic mouse or sometimes PS/2
  Elantech touchpad.

  After some 5-6 reboots without plugging in external mouse the touchpad
  finally starts to detect it as ETPS/2 Elantech touchpad.

  Reloading psmouse module seems to cause no effect (or it does yet
  after a minute touchpad stops working for a moment and then switches
  to PS/2 in xinput). Multitouch stops working as well as tapping with
  two fingers.

  I tried almost all the possible workarounds involving adding boot
  options, installing elantech driver fixes etc.

  Help is appreciated.

  The output of xinput as for now:

  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 BYD TouchPad   id=14   [slave  pointer 
 (2)]

  lsinput
  /dev/input/event14
     bustype : BUS_I8042
     vendor  : 0x2
     product : 0x1
     version : 99
     name: "PS/2 BYD TouchPad"
     phys: "isa0060/serio1/input0"
     bits ev : EV_SYN EV_KEY EV_REL

  UPDATE:

  Seems that forcing the psmouse to detect the touchpad as elantech
  helps to fix problem temporarily. But it works only from time to time:

  $ sudo rmmod psmouse
  $ sudo modprobe psmouse force="elantech"
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-27 (52 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634593/+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 1740143] Re: backport btrfs ssd mount option fix

[Kai-Heng Feng]

> On 27 Dec 2017, at 12:45 AM, Vasya Pupkin <1740...@bugs.launchpad.net> wrote:
> 
> This backport request does not miss anything. Also, the apport-collect
> 1740143 doesn't seem to do anything after opening this bug page in
> ELinks.

The change is substantial, can you ask the patch author and BTRFS
maintainers if it’s a good idea to backport it to stable Linux?

Apparently the original patch didn’t send for linux stable branch.

> 
> ** Changed in: linux (Ubuntu)
>   Status: Incomplete => Confirmed
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1740143
> 
> Title:
>  backport btrfs ssd mount option fix
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  Hello,
> 
>  It appears that all kernels before 4.14 had a problem with btrfs ssd
>  mount option. According to
>  https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it
>  has a negative impact on usability and lifetime of modern SSDs. Since
>  it is enabled by default when SSD is detected, it affects all systems
>  with SSD drives. Please backport this commit to normal and HWE
>  kernels:
>  
> https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: linux-image-generic 4.4.0.104.109
>  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
>  Uname: Linux 4.4.0-104-generic x86_64
>  AlsaDevices:
>   total 0
>   crw-rw 1 root audio 116,  1 дек 17 10:50 seq
>   crw-rw 1 root audio 116, 33 дек 17 10:50 timer
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
> k4.4.0-104-generic.
>  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
>  ApportVersion: 2.20.1-0ubuntu2.14
>  Architecture: amd64
>  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
> '/dev/snd/timer'] failed with exit code 1:
>  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
> kernel buffer failed: Operation not permitted
>  Date: Tue Dec 26 18:57:10 2017
>  InstallationDate: Installed on 2011-04-14 (2448 days ago)
>  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
> (20110211.1)
>  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
>  PciMultimedia:
> 
>  ProcFB: 0 nouveaufb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
> root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true
>  RelatedPackageVersions:
>   linux-restricted-modules-4.4.0-104-generic N/A
>   linux-backports-modules-4.4.0-104-generic  N/A
>   linux-firmware 1.157.14
>  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to xenial on 2016-07-30 (513 days ago)
>  WifiSyslog:
> 
>  dmi.bios.date: 02/20/2008
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: P1.40
>  dmi.board.name: 4Core1333-eSATA2.
>  dmi.chassis.asset.tag: To Be Filled By O.E.M.
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: To Be Filled By O.E.M.
>  dmi.chassis.version: To Be Filled By O.E.M.
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-eSATA2.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>  dmi.product.name: To Be Filled By O.E.M.
>  dmi.product.version: To Be Filled By O.E.M.
>  dmi.sys.vendor: To Be Filled By O.E.M.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740143/+subscriptions

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

Title:
  backport btrfs ssd mount option fix

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  It appears that all kernels before 4.14 had a problem with btrfs ssd
  mount option. According to
  https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it
  has a negative impact on usability and lifetime of modern SSDs. Since
  it is enabled by default when SSD is detected, it affects all systems
  with SSD drives. Please backport this commit to normal and HWE
  kernels:
  
https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.104.109
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 дек 17 10:50 seq
   crw-rw 1 root audio 116, 33 дек 17 10:50 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  

[Kernel-packages] [Bug 1740163] Re: Lost internet connecting after waking up from suspend

[Kai-Heng Feng]

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

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

Title:
  Lost internet connecting after waking up from suspend

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

Bug description:
  I lose internet after resuming from suspended state. The network
  applet shows that I am successfully and currently connected but alas
  pinging google all the packets fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 19:04:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-20 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.0.1 dev wlp4s0 proto static metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.80 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
1429809 2a1b6b8a-314e-4099-9761-124a5acac6ce  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   cdc-wdm0   gsm   unavailable  /org/freedesktop/NetworkManager/Devices/4  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740163/+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 1728748] Re: ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...

[Launchpad Bug Tracker]

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

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

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

Title:
  ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-
  ds3000.fw)...

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have an issue where the firmware on demand for my Pci-e DVB S2 card
  never gets loaded. Was working perfectly under 14.04 LTS after upgrade
  to 16.04 card stopped working and it seems to be related to this
  problem. Card firmeware loads fine. Tuner firmware cannot load even
  though it is there and is confirmed with the correct mdsum etc.

  Right now I have no working DVD S2 sat card. Any help appreciated.

  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
  [   21.609353] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
  [   21.760021] dvb-usb: found a 'TeVii S660 USB' in warm state.
  [   21.760157] dvb-usb: will pass the complete MPEG2 transport stream to the 
software demuxer.
  [   22.011709] dvb-usb: MAC address: 00:18:bd:5b:34:19
  [   22.672195] dvb-usb: schedule remote query interval to 150 msecs.
  [   22.672197] dvb-usb: TeVii S660 USB successfully initialized and connected.
  [   22.672223] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to 
load a firmware
  [   22.672248] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
  [   22.828038] dvb-usb: found a 'TeVii S660 USB' in warm state.
  [   22.828188] dvb-usb: will pass the complete MPEG2 transport stream to the 
software demuxer.
  [   23.066430] dvb-usb: MAC address: 00:18:bd:5b:34:1a
  [   23.085944] dvb-usb: schedule remote query interval to 150 msecs.
  [   23.085945] dvb-usb: TeVii S660 USB successfully initialized and connected.
  [ 2439.905073] ds3000_firmware_ondemand: Waiting for firmware upload 
(dvb-fe-ds3000.fw)...
  [ 2440.548843] ds3000_firmware_ondemand: Waiting for firmware upload 
(dvb-fe-ds3000.fw)...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen6211 F pulseaudio
   /dev/snd/controlC0:  stephen6211 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=
  MachineType: Gigabyte Technology Co., Ltd. EP45C-DS3R
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=8db65865-2ece-4cae-9fe9-3473eb9854ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2017-06-04 (148 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse hts kvm 
libvirtd lpadmin mythtv netdev plugdev sambashare scanner sudo tape users 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 09/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6a
  dmi.board.name: EP45C-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6a:bd09/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45C-DS3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45C-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728748/+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 1728727] Re: Just says internal error during start up

[Launchpad Bug Tracker]

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

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

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

Title:
  Just says internal error during start up

Status in linux package in Ubuntu:
  Expired

Bug description:
  I can continue without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2576 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 30 22:52:48 2017
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728727/+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 1728730] Re: duplicity gets stuck

[Launchpad Bug Tracker]

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

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Expired

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728730/+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 1553669] Re: Annoying "call from" message when connecting Bose devices

[Daniel van Vugt]

Can anyone affected tell if Ubuntu 18.04 has fixed this? (I'm thinking
about the fix for bug 1720684)

** Tags added: artful

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1634630] Re: Xbox 360 gamepad circular lights blink after wake-up

[Kai-Heng Feng]

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

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

Title:
  Xbox 360 gamepad circular lights blink after wake-up

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 16.10 x64.
  Linux 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  * plug a Xbox 360 gamepad on one of the USB port of the computer
  * the upper left circular green light is lit, other three lights stay off
  * put the computer in sleep mode
  * wake-up the computer

  Expected result: the circular green lights behave as when the gamepad was 
plugged
  Actual result: all four circular green lights are blinking every second for 
ever
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadrien2154 F pulseaudio
   /dev/snd/controlC1:  hadrien2154 F pulseaudio
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=6ed824e6-8d9c-4383-913b-ca2bd564bfcb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  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.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634630/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10

[Kai-Heng Feng]

It should be fixed by latest mainline kernel.
Currently there is a patch missing in Artful kernel.

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install

[Kai-Heng Feng]

> On 1 Jan 2018, at 10:01 PM, Eugene Savelov  wrote:
> 
> sorry, and how to add touchpad id so that  ELAN1200 04F3:303E  is
> detected by  elan_i2c module and works correctly?   my touchpad is
> currently detected by hid-multitouch instead and does not work
> correctly.

IIRC ELAN1200 should use hid-multitouch.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1727544
> 
> Title:
>  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
>  fresh install
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in linux source package in Xenial:
>  Fix Released
> Status in linux source package in Artful:
>  Fix Released
> 
> Bug description:
>  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
> touchpad is not working. I have followed this tutorial 
> https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
>  and it doesn't work. The touchpad is working fine on Windows. My kernel 
> version is 4.10.0-37-generic.
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.10
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  agasigp1605 F pulseaudio
>   /dev/snd/controlC1:  agasigp1605 F pulseaudio
>  CRDA:
>   country ID: DFS-JP
>   (2402 - 2482 @ 20), (N/A, 20), (N/A)
>   (5735 - 5815 @ 20), (N/A, 23), (N/A)
>  CurrentDesktop: Unity
>  DistroRelease: Ubuntu 16.04
>  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
>  InstallationDate: Installed on 2017-10-25 (2 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
> (20160420.1)
>  MachineType: LENOVO 80XU
>  Package: linux (not installed)
>  ProcFB: 0 amdgpudrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
> root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet 
> splash vt.handoff=7
>  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
>  RelatedPackageVersions:
>   linux-restricted-modules-4.10.0-37-generic N/A
>   linux-backports-modules-4.10.0-37-generic  N/A
>   linux-firmware 1.157.12
>  Tags:  xenial
>  Uname: Linux 4.10.0-37-generic x86_64
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>  _MarkForUpload: True
>  dmi.bios.date: 09/28/2017
>  dmi.bios.vendor: LENOVO
>  dmi.bios.version: 5PCN18WW
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: LNVNB161216
>  dmi.board.vendor: LENOVO
>  dmi.board.version: No DPK
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: LENOVO
>  dmi.chassis.version: Lenovo ideapad 320-14AST
>  dmi.modalias: 
> dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
>  dmi.product.name: 80XU
>  dmi.product.version: Lenovo ideapad 320-14AST
>  dmi.sys.vendor: LENOVO
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+subscriptions

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

Title:
  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
  fresh install

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
touchpad is not working. I have followed this tutorial 
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
 and it doesn't work. The touchpad is working fine on Windows. My kernel 
version is 4.10.0-37-generic.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agasigp1605 F pulseaudio
   /dev/snd/controlC1:  agasigp1605 F pulseaudio
  CRDA:
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80XU
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   

Re: [Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

> On 25 Dec 2017, at 4:44 AM, LCID Fire <1671...@bugs.launchpad.net> wrote:
> 
> I encountered a similar or same problem on Gigabyte AB350 with Ubuntu 16.04 
> running `4.13.0-21-generic #24~16.04.1-Ubuntu SMP Mon Dec 18 19:39:31 UTC 
> 2017`. It even shows up on 18.04 Alpha.
> Only thing that makes it halfway work is setting `acpi=off`.
> 
> Isn't this supposed to be fixed by now?

Please file a new bug with log attached.

> 
> -- 
> You received this bug notification because you are a member of AMD Team,
> which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1671360
> 
> Title:
>  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
> 
> Status in Linux:
>  Unknown
> Status in linux package in Ubuntu:
>  Fix Released
> Status in linux source package in Zesty:
>  Fix Released
> Status in linux source package in Artful:
>  Fix Released
> 
> Bug description:
>  [Impact]
>  Gigabyte AM4 boards users cannot boot Ubuntu successfully.
>  Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf 
> "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. 
> 
>  [Test Case]
>  All Gigabyte AM4 boards can reproduce the issue.
>  With the patch, the issue is resolved, per comment #170.
> 
>  [Regression Potential] 
>  Regression Potential is low. It limits to rather new AMD platform which has 
> pinctrl-amd. 
>  As the commit log says, use chained interrupt is not a good idea. Use 
> regular interrupt is the correct way.
> 
>  I also test the patch on an AMD laptop, where its touchpad depends on
>  pinctrl-amd. No regression found.
> 
>  Original bug report:
>  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
> motherboard,
>  and it has a load of problems, starting with not being able to boot normally.
> 
>  During normal boot, on 16.10 as well as 17.04 beta:
>  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
> vector 07"
>  messages displayed.
> 
>  Following advice from various places, I've tried:disable cpu freq
>  governor and cpu handling in acpi settings
> 
>  1. add "acpi=off" to boot params
> 
>  That helps, allowing me to boot into recovery mode, though it leaves
>  me with system seeing only one core, is really slow and still only
>  boots in recovery mode.
> 
>  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
>  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
>  option.
> 
>  That gets me even further - system sees all cores now. Still only recovery 
> mode though,
>  but its enough to get info for this bug report.
> 
>  Some observed problems:
> 
>  1. dmesg reports *a lot* of messages like this all the time:
> 
>  [  163.362068] ->handle_irq():  87a7e090,
>  [  163.362081] bad_chained_irq+0x0/0x40
>  [  163.362089] ->handle_irq():  87a7e090,
>  [  163.362090] amd_gpio_irq_handler+0x0/0x200
>  [  163.362090] ->irq_data.chip(): 88587e20,
>  [  163.362090] ioapic_ir_chip+0x0/0x120
>  [  163.362090] ->action(): 884601c0
>  [  163.362091]IRQ_NOPROBE set
>  [  163.362099] ->handle_irq():  87a7e090,
>  [  163.362099] amd_gpio_irq_handler+0x0/0x200
>  [  163.362100] ->irq_data.chip(): 88587e20,
>  [  163.362100] ioapic_ir_chip+0x0/0x120
>  [  163.362101] ->action(): 884601c0
> 
>  I've tried to redirect dmesg to a file, stopped after a short while,
>  it generated 400M of those.
> 
>  2. Systemd cannot start journald. Perhaps because it cannot cope with
>  amount of kernel logs?
> 
>  3. Looking at pci, I've noticed something called AMDI0040
>  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
>  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
>  kernel and google are completely silent about AMDI0040.
> 
>  Phoronix tested ryzen using different motherboard, and it worked better 
> (though not well),
>  so I suspect it is an issue with motherboard.
>  ---
>  ApportVersion: 2.20.4-0ubuntu2
>  Architecture: amd64
>  DistroRelease: Ubuntu 17.04
>  InstallationDate: Installed on 2015-08-06 (581 days ago)
>  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
>  Package: linux (not installed)
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   TERM=linux
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  Tags:  zesty
>  Uname: Linux 4.11.0-rc1-custom x86_64
>  UnreportableReason: The running kernel is not an Ubuntu kernel
>  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
>  UserGroups:
> 
>  _MarkForUpload: True
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  

Re: [Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged

[Kai-Heng Feng]

> On 21 Dec 2017, at 11:02 PM, tjiagoM <1661...@bugs.launchpad.net> wrote:
> 
> I have now kernel 4.14 and this issue is still not solved.

Same as LP: #1482390?

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1661876
> 
> Title:
>  [Asus UX360UA] battery status in unity-panel is not changing when
>  battery is being charged
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus
>  UX360UA, alongside with Windows 10. I've already installed the updates
>  meanwhile.
> 
>  When I start charging my computer the battery icon on the unity-panel
>  is not changing (it stays in the 98% complete).
> 
>  This is strange because this is a fresh installation so I didn't change any 
> configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
> that the icon changed when I started charging the laptop. That's why I think 
> it is a bug.
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.5
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
>  CurrentDesktop: Unity
>  DistroRelease: Ubuntu 16.04
>  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
>  InstallationDate: Installed on 2017-02-04 (0 days ago)
>  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
> (20160719)
>  Lsusb:
>   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: ASUSTeK COMPUTER INC. UX360UA
>  Package: linux (not installed)
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
> root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
>  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
>  RelatedPackageVersions:
>   linux-restricted-modules-4.4.0-62-generic N/A
>   linux-backports-modules-4.4.0-62-generic  N/A
>   linux-firmware1.157.6
>  Tags:  xenial
>  Uname: Linux 4.4.0-62-generic x86_64
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>  _MarkForUpload: True
>  dmi.bios.date: 06/17/2016
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: UX360UA.300
>  dmi.board.asset.tag: ATN12345678901234567
>  dmi.board.name: UX360UA
>  dmi.board.vendor: ASUSTeK COMPUTER INC.
>  dmi.board.version: 1.0
>  dmi.chassis.asset.tag: ATN12345678901234567
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>  dmi.chassis.version: 1.0
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>  dmi.product.name: UX360UA
>  dmi.product.version: 1.0
>  dmi.sys.vendor: ASUSTeK COMPUTER INC.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions

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

Title:
  [Asus UX360UA] battery status in unity-panel is not changing when
  battery is being charged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus
  UX360UA, alongside with Windows 10. I've already installed the updates
  meanwhile.

  When I start charging my computer the battery icon on the unity-panel
  is not changing (it stays in the 98% complete).

  This is strange because this is a fresh installation so I didn't change any 
configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
that the icon changed when I started charging the laptop. That's why I think it 
is a bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
 

[Kernel-packages] [Bug 1661878] Re: [Asus UX360UA] Physical screen rotation is not detected

[Kai-Heng Feng]

I think Unity doesn't support screen rotate. Please try latest Ubuntu or
Ubuntu-Gnome.

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

Title:
  [Asus UX360UA] Physical screen rotation is not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus
  UX360UA, alongside with Windows 10. I've already installed the updates
  meanwhile.

  This laptop has a 360º degree rotating screen. When I physically
  rotate my screen, Windows (or some installed driver, I don't know)
  detects that. Consequently, the image being displayed in the screen is
  rotated 180º and the keyboard is blocked. However, Ubuntu doesn't do
  nothing when I rotate the screen.

  I think this is a bug because a fresh Ubuntu installation should recognise 
these laptop features. I searched a little bit and it seems there are some 
workarounds on this, but I guess Ubuntu installation should recognise this 
automatically?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661878/+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 1738490] Re: current boot config dims screen during initramfs

[Kai-Heng Feng]

That's because rootfs has systemd-backlight@.service to restore/save the
brightness value. Probably a good idea to do the same for initramfs.

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  current boot config dims screen during initramfs

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a weird one. Shortly after moving to 17.10, my laptop has
  started dimming its internal screen to minimum brightness at the start
  of initramfs execution. shortly thereafter it restores it to normal
  brightness, but that only happens *after* typing in encrypted
  filesystem passwords, so the password dialogues are practically
  invisible. Not sure why its doing this, but whatever's restoring the
  brightness should do it before prompting for filesystem mounting so
  these prompts are actually visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.19.20
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessa 17026 F pulseaudio
   /dev/snd/controlC1:  tessa 17026 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Dec 15 13:44:02 2017
  InstallationDate: Installed on 2016-07-08 (524 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=ZFS=rpool/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (57 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0177.B00.1708080033
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1738490/+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 1739102] Re: Lenovo 11e Input Freeze

[Kai-Heng Feng]

You need to do a kernel bisection then.

Please find the first bad v4.13-rc kernel release from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  Lenovo 11e Input Freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We're been running into an issue that so far seems to be limited to our 
Lenovo 11e laptops and Ubuntu 17.10. 
  On first boot, the touchpad and keyboard will work sporadically with random 
keys occasionally being registered as being pressed. After some time, both the 
touchpad and keyboard completely stop functioning. We've replicated the issue 
on other 11e laptops to ensure it wasn't a hardware problem.

  Touchpad and keyboard both work perfectly on Ubuntu 16.04.3

  
  dmesg is showing a bunch of the following:

  psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, 
throwing 4 bytes away.
  psmouse serio1: resync failed, issuing reconnect request
  psmouse serio1: synaptics: unable to initialize device

  
  What we expect to happen:
  Touchpad and Keyboard will allow user input

  
  What happened instead:
  Touchpad and Keyboard register random input or don't function at all.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tech970 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-12-12 (7 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20GBS00S00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8b4328ce-7dad-4e55-8229-df928776303b ro quiet splash acpi_osi=Linux 
acpi_lightback=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare 
scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 03/01/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0AET33W (1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13467 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:bvrR0AET33W(1.16):bd03/01/2017:svnLENOVO:pn20GBS00S00:pvrThinkPad11e3rdGen:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0K13467WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad 11e 3rd Gen
  dmi.product.name: 20GBS00S00
  dmi.product.version: ThinkPad 11e 3rd Gen
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739102/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Hernán Alvarez]

The 4.15-rc6 from kernel.ubuntu.com is no different, it also lacks the
intel-spi driver.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Ryan Burke]

@bbaker6212/Brad, weirdly enough it does work after a suspend/wake but
will cease working after any sort of interaction with the touchpad
settings including on/off.

modprobe commands have no effect.

Requested Info:

theyield@Keyloggertop ~ $ uname -a
Linux Keyloggertop 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 
23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
theyield@Keyloggertop ~ $ dmesg | grep YEPO
[0.00] DMI: LIVEFAN LIVEFAN/P313R, BIOS YEPOM10x.8.WP313R.NHNAUHL01 
10/09/2017
theyield@Keyloggertop ~ $ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PixArt Dell MS116 USB Optical Mouse   id=8[slave  pointer  (2)]
⎜   ↳ SYNA3602:00 0911:5288 Touchpadid=10   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Video Bus id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ USB2.0 UVC PC Camera: USB2.0 UV   id=9[slave  keyboard (3)]
↳ Intel HID events  id=11   [slave  keyboard (3)]
↳ Intel HID 5 button array  id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
theyield@Keyloggertop ~ $ xinput list 10
SYNA3602:00 0911:5288 Touchpad  id=10   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right"
Button state:
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 10. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 15.00
  flags: 0x0
Class originated from: 10. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: 15.00
  flags: 0x0

theyield@Keyloggertop ~ $ xinput list-props "SYNA3602:00 0911:5288 Touchpad"
Device 'SYNA3602:00 0911:5288 Touchpad':
Device Enabled (142):   1
Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Tapping Enabled (293): 1
libinput Tapping Enabled Default (294): 0
libinput Tapping Drag Enabled (295):1
libinput Tapping Drag Enabled Default (296):1
libinput Tapping Drag Lock Enabled (297):   0
libinput Tapping Drag Lock Enabled Default (298):   0
libinput Accel Speed (276): 0.00
libinput Accel Speed Default (277): 0.00
libinput Natural Scrolling Enabled (281):   1
libinput Natural Scrolling Enabled Default (282):   0
libinput Send Events Modes Available (260): 1, 1
libinput Send Events Mode Enabled (261):0, 0
libinput Send Events Mode Enabled Default (262):0, 0
libinput Left Handed Enabled (283): 0
libinput Left Handed Enabled Default (284): 0
libinput Scroll Methods Available (285):1, 1, 0
libinput Scroll Method Enabled (286):   1, 0, 0
libinput Scroll Method Enabled Default (287):   1, 0, 0
libinput Click Methods Available (299): 1, 1
libinput Click Method Enabled (300):1, 0
libinput Click Method Enabled Default (301):1, 0
libinput Middle Emulation Enabled (290):0
libinput Middle Emulation Enabled Default 

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

Ryan, also provide the info @mogio provided in post #85 so we can see
your configuration.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

@theyield/Ryan, does the touchpad function after you perform suspend+wake with 
either kernel 4.14.x or 4.15 as reported in post #86 above?
What about after you perform these two terminal commands?..
sudo modprobe -rv i2c_hid
sudo modprobe -v i2c_hid

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Ryan Burke]

I just thought I would add that I too am affect by this on my system:

SYNA3602 device on a YEPO 737A Laptop - Linux Mint 18.3 Cinnamon respun,
as OP describes. The touchpad doesn't work live, and has never worked
after install.

I'm currently on 4.15 RC6 which was respun into the install ISO via the
-u argument.

Touchpad works flawlessly in windows 10 of course.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  HP Notebook - 17-y012cy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No touch screen.
  This is a newer computer and a fresh install of 17.10 with updates
  Blew away Windows 10 when new computer arrived
  I have not seen any other issues

  HP Notebook - 17-y012cy
  2 tb drive
  12 gb ram
  17 inch screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franklin   2134 F pulseaudio
   /dev/snd/controlC0:  franklin   2134 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  1 12:57:13 2018
  InstallationDate: Installed on 2017-10-23 (69 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=0bbf90d5-9d0a-47d8-973b-3d5c08672ed5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-24 (69 days ago)
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8221
  dmi.board.vendor: HP
  dmi.board.version: 85.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd03/13/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740770/+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 1697230] Re: atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on isa0060/serio0).

[Markus Birth]

My problem seems to also be reported in bug #1535008 .

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

Title:
  atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on
  isa0060/serio0).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [  126.478301] atkbd serio0: Unknown key pressed (translated set 2, code 0x87 
on isa0060/serio0).
  [  126.478308] atkbd serio0: Use 'setkeycodes e007 ' to make it 
known.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1963 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1963 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun 10 20:35:47 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (685 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.166
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-05-15 (26 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697230/+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 1740770] [NEW] HP Notebook - 17-y012cy

[Highlander]

Public bug reported:

No touch screen.
This is a newer computer and a fresh install of 17.10 with updates
Blew away Windows 10 when new computer arrived
I have not seen any other issues

HP Notebook - 17-y012cy
2 tb drive
12 gb ram
17 inch screen

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  franklin   2134 F pulseaudio
 /dev/snd/controlC0:  franklin   2134 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  1 12:57:13 2018
InstallationDate: Installed on 2017-10-23 (69 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Notebook
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=0bbf90d5-9d0a-47d8-973b-3d5c08672ed5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-21-generic N/A
 linux-backports-modules-4.13.0-21-generic  N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-24 (69 days ago)
dmi.bios.date: 03/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8221
dmi.board.vendor: HP
dmi.board.version: 85.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd03/13/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


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

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

Title:
  HP Notebook - 17-y012cy

Status in linux package in Ubuntu:
  New

Bug description:
  No touch screen.
  This is a newer computer and a fresh install of 17.10 with updates
  Blew away Windows 10 when new computer arrived
  I have not seen any other issues

  HP Notebook - 17-y012cy
  2 tb drive
  12 gb ram
  17 inch screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franklin   2134 F pulseaudio
   /dev/snd/controlC0:  franklin   2134 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  1 12:57:13 2018
  InstallationDate: Installed on 2017-10-23 (69 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=0bbf90d5-9d0a-47d8-973b-3d5c08672ed5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-24 (69 days ago)
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8221
  dmi.board.vendor: HP
  dmi.board.version: 85.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd03/13/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740770/+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 1626283] Re: lenovo t420s very slow wifi after dist upgrade 14-16

[Aleksei]

sorry - The config above is not working as well. I mean - it is unstable - it 
may give 35 MBit/s
or 0.5 MBit/s. No relation with '11n_disable' setting found. I tried several 
kernels - 4.4.10 - but haven't been able to find stable working one - so the 
question is still open

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

Title:
  lenovo t420s very slow wifi after dist upgrade 14-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it is not more than 2 mbit\s for the moment - before upgrade it works well - 
about 40-50 mbit\s.
  it is not ISP issue other devices works fast at my wifi network

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Sep 22 00:29:18 2016
  InstallationDate: Installed on 2015-12-17 (279 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (35 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626283/+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 1697230] Re: atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on isa0060/serio0).

[Markus Birth]

I see this during bootup with a fresh install of artful on a HP Spectre
x360 13-4104ng notebook. For me it's  setkeycodes e057 and code 0xd7,
though.

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

Title:
  atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on
  isa0060/serio0).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [  126.478301] atkbd serio0: Unknown key pressed (translated set 2, code 0x87 
on isa0060/serio0).
  [  126.478308] atkbd serio0: Use 'setkeycodes e007 ' to make it 
known.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1963 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1963 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun 10 20:35:47 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (685 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.166
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-05-15 (26 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697230/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Hernán Alvarez]

I have the one that ukuu installed, I'm now downloading the Ubuntu-
compiled ones.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10

[Eugene Savelov]

currently my touchpad is detected by hid-multitouch module - and I
assume I need to add ELAN1200:00 04F3:303E Touchpad to elan_i2c module
instead, right?

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[apt-ghetto]

You have the kernel 4.15-rc6 from kernel.org or from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6/ ?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install

[Eugene Savelov]

sorry, and how to add touchpad id so that  ELAN1200 04F3:303E  is
detected by  elan_i2c module and works correctly?   my touchpad is
currently detected by hid-multitouch instead and does not work
correctly.

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

Title:
  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
  fresh install

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
touchpad is not working. I have followed this tutorial 
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
 and it doesn't work. The touchpad is working fine on Windows. My kernel 
version is 4.10.0-37-generic.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agasigp1605 F pulseaudio
   /dev/snd/controlC1:  agasigp1605 F pulseaudio
  CRDA:
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80XU
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+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 1553669] Re: Annoying "call from" message when connecting Bose devices

[Knut Sindre Åbjørsbråten]

This problem is still present in Ubuntu 17.10.

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10

[Eugene Savelov]

this is output of evtest - worked for 18 mins, but finally stopped, these are 
the last lines -
Event: time 1514812803.354344, -- SYN_REPORT 
Event: time 1514812803.354927, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 1868
Event: time 1514812803.354927, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 750
Event: time 1514812803.354927, -- SYN_REPORT 
Event: time 1514812803.368057, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 1872
Event: time 1514812803.368057, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 781
Event: time 1514812803.368057, -- SYN_REPORT 
Event: time 1514812803.381777, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 1883
Event: time 1514812803.381777, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 851
Event: time 1514812803.381777, -- SYN_REPORT 
Event: time 1514812803.382357, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 1888
Event: time 1514812803.382357, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 895
Event: time 1514812803.382357, -- SYN_REPORT 
Event: time 1514812803.485414, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), 
value -1
Event: time 1514812803.485414, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1
Event: time 1514812803.485414, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), 
value -1
Event: time 1514812803.485414, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1514812803.485414, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), 
value 0
Event: time 1514812803.485414, -- SYN_REPORT 

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Hernán Alvarez]

Just installed 4.15-rc6 and it doesn't even have the intel-spi driver
compiled...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1740116] Re: Touchpad incorrectly being detected by kernel as PS/2 mouse

[Apicultor]

This might be a duplicate of bug 1708852, but the upstream kernel 4.14.9
does NOT fix the issue.

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

Title:
  Touchpad incorrectly being detected by kernel as PS/2 mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Panasonic Toughbook CF-30 (specifically CF-30K, also known as "CF30",
  "CF-30 Mk3", "CF-30 Mark 3", etc) touchpad is being detected as only a
  generic PS/2 mouse, not a touchpad.

  Pointing and clicking (also tapping to click) works, but scrolling
  doesn't work -- and there is no touchpad options in the relevant
  control panel, only pointer speed.

  This appears to be happening in the kernel, not in X.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Tue Dec 26 11:54:48 2017
  InstallationDate: Installed on 2017-12-17 (8 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740116/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sachin Anand]

I am using Lubuntu 17.10
Few week back I did this install and due to some requirement I wanted to change 
OS. But to my bad luck the initial BIOS page itself is not coming and while 
searching for the solution I got to know the big issue. Its not the way an OS 
should behave. My Laptop is LENOVO Y500 45Q.
Either Lenovo or Ubuntu should come up with solution... every one is not that 
equipped to do BIOS flash or some hardware changes by themselves. Hoping to get 
some solution soon...   :(

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[serj.kzv]

Hi Juan Felipe (hacktt),

I have got HP 15-ac159ur laptop and Ubuntu 17.10 is fine for me. All functions 
except Hibernation work fine. Only one small problem with artefact in EFI that 
I have been seeing by typing "efibootmgr" command.
I have fixed that according that article: 
https://wiki.debian.org/GrubEFIReinstall

I am not sure but do you need 'System Diagnostics' to recover BIOS? According 
article below you could recover BIOS by pressing and holding 'Win + B' during 
booting to repair BIOS from USB Flash Drive (which you have to create with any 
Windows OS):
https://support.hp.com/us-en/document/c02693833

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[serj.kzv]

Hi Juan Felipe (hacktt),

I have got HP 15-ac159ur laptop and Ubuntu 17.10 is fine for me. All functions 
except Hibernation works fine. Only one small problem with artefact in EFI that 
I have been seeing by typing "efibootmgr" command.
I have fixed that according that article: 
https://wiki.debian.org/GrubEFIReinstall

I am not sure but do you need 'System Diagnostics' to recover BIOS? According 
article below you could recover BIOS by pressing and holding 'Win + B' during 
booting to repair BIOS from USB Flash Drive (which you have to create with any 
Windows OS):
https://support.hp.com/us-en/document/c02693833

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3

[ajmal]

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

 modprobe bcm2835-v4l2 crashes the system. I tried various thinks but
same. I could not use openCV to capture the images. However
raspicam_node (https://github.com/fpasteau/raspicam_node) able is
capturing images from the camera.

HARDWARE: Raspberry Pi3
Camera: picam v2
uname -vr output: 4.4.0-1080-raspi2 #88-Ubuntu SMP Mon Dec 11 14:23:15 UTC 2017

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

Title:
  Recent updates broke Ubuntu on Raspberry Pi 3

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've been running Raspberry Pi 3 with Ubuntu as described here 
https://wiki.ubuntu.com/ARM/RaspberryPi

  I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been
  using this setup successfully since October up until last week.
  Unfortunately one of the latest kernel updates broke the installation
  and I found out the same happened for Ubuntu 16.04 LTS - and therefore
  I can no longer run up-to-date Ubuntu installation (with updated
  kernel) on my RPI.

  I am getting this error:
  Error image is not a fdt - must reset the board to recover

  I also tried this but it didn't help me:
  https://www.raspberrypi.org/forums/viewtopic.php?f=28=168838

  Now I know running Ubuntu on RPI3 this way is not officially
  supported, but since Ubuntu Snappy is supported I thought someone here
  could know what is going on.

  Thank you very much.

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1726934/+attachment/5029660/+files/IwConfig.txt

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1726934/+attachment/5029663/+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/1726934

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1726934/+attachment/5029669/+files/RfKill.txt

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

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

[Eugene Savelov]

apport information

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10

[Eugene Savelov]

ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mikhail1048 F pulseaudio
 /dev/snd/controlC0:  mikhail1048 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-10-22 (71 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: ASUSTeK COMPUTER INC. X505BA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=UUID=346c6d11-8a1f-4d8e-bec3-523a1beb0e9b ro quiet splash
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-22-generic N/A
 linux-backports-modules-4.13.0-22-generic  N/A
 linux-firmware 1.169.2
Tags:  wayland-session artful
Uname: Linux 4.13.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X505BA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X505BA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX505BA.303:bd06/27/2017:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X505BA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.


** Tags added: apport-collected wayland-session

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

Title:
  Elantech touchpad unresponsive in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and
  with the upgrade to Wayland full-time, all of the elantech issues from
  a few years back are coming back with a vengeance. Upon upgrade, my
  trackpad is no longer functional and I am forced to use an external
  mouse. I don't have an extra mouse that I can just drag around with
  the laptop, nor do I wish to purchase one to use when I have a
  trackpad on the laptop itself. Dmesg doesn't show anything about the
  driver failing to load and syslog shows nothing either. I know this is
  a common issue with this kind of trackpad but I hope to see a fix soon
  so I can go back to using Ubuntu normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1626283] Re: lenovo t420s very slow wifi after dist upgrade 14-16

[Aleksei]

As I managed to solve the problem before and after updates I started
using latest kernel where the problem reveals again, I put my working
config here

First - this one - sudo vim /etc/modprobe.d/iwlwifi-disable11n.conf
having this one inside - options iwlwifi 11n_disable=0
is not affecting the wi-fi speed

Secondly, I've installed 3.19 kernel - and it works for me

GRUB config

1. Using grub-customizer, I've put 3.19 entry on top of menu list, to have it 
 being run with just one 'enter' key

2. I've put here - sudo gedit /etc/default/grub
the following - GRUB_DEFAULT="Ubuntu, with Linux 3.19.0-66-generic"

the speed is good - about 36 MBit/second for upload/download both

Hope it will help someone

Note, that the latest (4.4.23 kernel) have buggy slow wi-fi driver(0.5,
2 MBit/second)

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

Title:
  lenovo t420s very slow wifi after dist upgrade 14-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it is not more than 2 mbit\s for the moment - before upgrade it works well - 
about 40-50 mbit\s.
  it is not ISP issue other devices works fast at my wifi network

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Sep 22 00:29:18 2016
  InstallationDate: Installed on 2015-12-17 (279 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (35 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626283/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Mika Westerberg]

Can someone who still has the problem try v4.15-rcX kernel instead? It
got few fixes for the atomic sequence handling and might explain why not
all systems recover.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Leó Kolbeinsson]

Happy New Year!

Acer Aspire E3-111-P605 with Insyde BIOS in legacy mode when updated to
lubuntu 17.10 resulting in the problem unable to boot from USB or save
changes in the BIOS.

My solution was to upgrade the kernel to 4.14.10. Still unable to make any 
changes in BIOS.
However when booting GRUB2 and selecting "c" (entering prompt) and then "exit" 
the Intel Undi PXE -2.1 (build 083)utility was invoked and wait for the PXE 
utility to exit - then I could boot from USB and/or USB CD-ROM drives.  

I found it interesting that when booting if I pressed "ESC" the attached
drives appeared on the BIOS info screen - however if I entered the BIOS
with "F2" - the BIOS reported only the Hard Drive and the Intel PXE as
available boot devices.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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