[Kernel-packages] [Bug 1792672] PulseList.txt

2018-09-15 Thread Gioele Barabucci
apport information

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  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.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  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/1792672/+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 1792672] RfKill.txt

2018-09-15 Thread Gioele Barabucci
apport information

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  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.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  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/1792672/+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 1792672] WifiSyslog.txt

2018-09-15 Thread Gioele Barabucci
apport information

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

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  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.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  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/1792672/+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 1792672] Status changed to Confirmed

2018-09-15 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  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.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  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/1792672/+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 1792672] UdevDb.txt

2018-09-15 Thread Gioele Barabucci
apport information

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  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.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  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/1792672/+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 1791728] Re: linux-gcp: 4.15.0-1020.21 -proposed tracker

2018-09-15 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

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

Title:
  linux-gcp: 4.15.0-1020.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1791719
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791728/+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 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2018-09-15 Thread Werner Lueckel
I tested the flickering-issue with the upstream-kernel 
 
"linux-image-unsigned-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb"
and it seemed to be fixed!
No more flickering.
So I added the tag "kernel-fixed-upstream" to this report.


** Tags added: kernel-fixed-upstream

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

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+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 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

2018-09-15 Thread Kai-Heng Feng
Does this still happen to latest mainline kernel or latest Ubuntu 18.04
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/1782934

Title:
  XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu
  Budgie), the graphical installer works correctly, but on every post-
  install login, the screen goes black at the disk decryption screen.

  The kernel version post-install is 4.14.0-29-generic (edited to add:
  this SHOULD have read '4.15.0-29-generic').

  Other things seem to be working. If I'm careful, I can enter the disk
  decryption password and tell (via sounds) that I've gotten through to
  the login screen, but the screen remains dark.

  This happens with standard or minimal installs.

  If I then try to boot with the previous kernel--4.15.0-20-generic--
  everything works flawlessly.

  The only non-standard thing about this system is that I replaced the
  onboard wireless card with an Intel Dual Band Wireless-AC 8625.

  ---

  I don't have a clue about kernel debugging, but I can provide further
  system info as needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 21 20:35:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Iris Graphics 540 [1028:0704]
  InstallationDate: Installed on 2018-07-21 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 1792002] Re: Wireless signal extremely weak or not detected

2018-09-15 Thread Joseph
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Wireless signal extremely weak or not detected

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi Support,

  I'm Linux Mint newbie started using from LM v18. I'm using HP245
  series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE.
  Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt
  a month ago.

  I'm facing a WiFi signal problem whenever I've tried to upgrade to
  Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either
  very weak & disconnects frequently or cannot be detected from very
  small distances (3-5 mtr). I've never had this issue till kernel
  v4.15.0.32 and everything was working fine and currently I had to
  downgrade or revert back to 4.15.0.32 again in order to receive signal
  to write this mail.

  Kindly resolve this error ASAP as I want to upgrade to the latest
  version.

  Regards,
  Joseph

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2018-09-15 Thread Heribert Heckhoff
I've tested with the kernel as recommended and suggest in #25. Wifi with
rtl8723b3 works again (like a charm). However, ant_sel must be set to 1
(ant_sel=1) as opposed to kernel 4.15.0-32, which required ant_sel to be
set to 2 (ant_sel=2). (e.g sudo modprobe rtl8723be ant_sel=1 vs. sudo
modprobe rtl8723be ant_sel=2).

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard: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: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2018-09-15 Thread Heribert Heckhoff
I don't know how to add a tag to or mark this bug track. :-;

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard: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: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1644981] Re: ExFAT Formatted SD Cards not mounted

2018-09-15 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  ExFAT Formatted SD Cards not mounted

Status in linux package in Ubuntu:
  Expired

Bug description:
  ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards
  work perfectly on 12.04, 14.04 and Windows.

  Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB 
device number 7 using xhci_hcd
  Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device 
found, idVendor=058f, idProduct=6366
  Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card 
Reader/Writer
  Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic
  Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 
058F63666485
  Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass 
Storage device detected
  Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 
1-8:1.0
  Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: 
"/sys/devices/pci:00/:00:14.0/usb1/1-8"
  Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device
  Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access   
  Multiple Card  Reader 1.00 PQ: 0 ANSI: 4
  Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi 
generic sg1 type 0
  Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached 
SCSI removable disk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.47.50
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   2240 F pulseaudio
   /dev/snd/controlC1:  sebastian   2240 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Nov 26 11:22:03 2016
  HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7
  InstallationDate: Installed on 2015-08-06 (477 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305LA
  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.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305LA
  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/1644981/+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 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

2018-09-15 Thread Christopher M. Penalver
Gioele Barabucci, thank you for reporting this and helping make Ubuntu
better.

1a) Regarding regression potential, did you personally test with your
Samsung NP900X3D-A03IT (not someone else, somewhere else) a prior Ubuntu
release or prior kernel version and this was working?

1b) If so, which one specifically?

2) In order to allow additional upstream mainline kernel developers to examine 
the issue, at your earliest convenience, could you please test the latest 
mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Tags added: regression-potential

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  

[Kernel-packages] [Bug 1788004] Re: File System inaccessible after 18.04 upgrade

2018-09-15 Thread Chris Claggett
ZoL bug has also been opened for this with more information:
https://github.com/zfsonlinux/zfs/issues/7910

** Bug watch added: Github Issue Tracker for ZFS #7910
   https://github.com/zfsonlinux/zfs/issues/7910

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

Title:
  File System inaccessible after 18.04 upgrade

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  ZPool was functioning before upgrading to Ubuntu 18.04.  Unfortunately
  didn't confirm pool working before upgrading the pool so can't roll
  back.  Can't access file system anymore, though a scrub did succeed.

  Simple 'ls -la' segfaults, and this shows up in dmesg:
  [  320.449464] detected buffer overflow in memmove
  [  320.449489] [ cut here ]
  [  320.449492] kernel BUG at 
/build/linux-wuhukg/linux-4.15.0/lib/string.c:1052!
  [  320.449503] invalid opcode:  [#1] SMP PTI
  [  320.449506] Modules linked in: thunderbolt nls_iso8859_1 zfs(PO) 
zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) snd_
  hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm snd_hda_codec_ca0132 irqbypass crct10dif_pclmu
  l crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hda_intel 
snd_hda_codec aes_x86_64 crypto_simd snd_hda_core glue_helper crypt
  d intel_cstate snd_hwdep intel_rapl_perf snd_pcm intel_wmi_thunderbolt 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_de
  vice snd_timer snd soundcore input_leds mac_hid mei_me mei shpchp acpi_pad 
intel_pch_thermal sch_fq_codel vhba(OE) parport_pc ppdev l
  p parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 mxm_wmi 
e1000e i2c_algo_bit ptp drm_kms_helper pps_core syscopyarea 
  sysfillrect
  [  320.449599]  sysimgblt fb_sys_fops alx drm mdio ahci libahci wmi video
  [  320.449617] CPU: 3 PID: 3202 Comm: updatedb.mlocat Tainted: PW  OE 
   4.15.0-32-generic #35-Ubuntu
  [  320.449621] Hardware name: Gigabyte Technology Co., Ltd. To be filled by 
O.E.M./Z170X-Gaming 7, BIOS F8 08/26/2016
  [  320.449632] RIP: 0010:fortify_panic+0x13/0x22
  [  320.449636] RSP: 0018:a85fc5d27898 EFLAGS: 00010282
  [  320.449641] RAX: 0023 RBX: a85fc5d279a8 RCX: 

  [  320.449645] RDX:  RSI: 97dc51d96498 RDI: 
97dc51d96498
  [  320.449649] RBP: a85fc5d27898 R08:  R09: 
058c
  [  320.449652] R10: 97dc2916501c R11: b895380d R12: 
0001
  [  320.449656] R13: 97dc2a717460 R14: 0070 R15: 
97dc21e40300
  [  320.449661] FS:  7fb9bd9c4540() GS:97dc51d8() 
knlGS:
  [  320.449665] CS:  0010 DS:  ES:  CR0: 80050033
  [  320.449669] CR2: 7fa69800e778 CR3: 000812c88005 CR4: 
003606e0
  [  320.449673] DR0:  DR1:  DR2: 

  [  320.449677] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  320.449680] Call Trace:
  [  320.449779]  zfs_acl_node_read.constprop.15+0x33d/0x340 [zfs]
  [  320.449867]  zfs_zaccess_aces_check+0x96/0x380 [zfs]
  [  320.449874]  ? mutex_lock+0x12/0x40
  [  320.449879]  ? _cond_resched+0x19/0x40
  [  320.449929]  ? arc_buf_access+0x14a/0x270 [zfs]
  [  320.449977]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  320.450056]  zfs_zaccess_common+0xda/0x1f0 [zfs]
  [  320.450062]  ? _cond_resched+0x19/0x40
  [  320.450139]  zfs_zaccess+0xd4/0x3d0 [zfs]
  [  320.450235]  ? rrw_enter_read_impl+0xae/0x160 [zfs]
  [  320.450327]  zfs_lookup+0x1c5/0x3a0 [zfs]
  [  320.450415]  zpl_lookup+0xc9/0x1e0 [zfs]
  [  320.450424]  lookup_slow+0xab/0x170
  [  320.450432]  walk_component+0x1c3/0x470
  [  320.450438]  ? _cond_resched+0x19/0x40
  [  320.450444]  ? mutex_lock+0x12/0x40
  [  320.450451]  path_lookupat+0x84/0x1f0
  [  320.450458]  ? ___slab_alloc+0xf2/0x4b0
  [  320.450545]  ? zfs_readdir+0x267/0x460 [zfs]
  [  320.450552]  ? ___slab_alloc+0xf2/0x4b0
  [  320.450560]  filename_lookup+0xb6/0x190
  [  320.450569]  ? __check_object_size+0xaf/0x1b0
  [  320.450578]  ? strncpy_from_user+0x4d/0x170
  [  320.450586]  user_path_at_empty+0x36/0x40
  [  320.450592]  ? user_path_at_empty+0x36/0x40
  [  320.450600]  vfs_statx+0x76/0xe0
  [  320.450606]  ? _cond_resched+0x19/0x40
  [  320.450611]  ? dput.part.22+0x2d/0x1e0
  [  320.450619]  SYSC_newlstat+0x3d/0x70
  [  320.450628]  ? SyS_poll+0x9b/0x130
  [  320.450635]  ? SyS_poll+0x9b/0x130
  [  320.450643]  SyS_newlstat+0xe/0x10
  [  320.450651]  do_syscall_64+0x73/0x130
  [  320.450659]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  320.450664] RIP: 0033:0x7fb9bd4d2815
  [  320.450669] RSP: 002b:7ffe3d613f38 EFLAGS: 0246 ORIG_RAX: 
0006
  [  320.450675] RAX: ffda RBX: 5632906b5059 RCX: 
7fb9bd4d2815
  [  320.450679] RDX: 7ffe3d613fb0 RSI: 000

[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault

2018-09-15 Thread Martin Barlow
Actually, it just reoccurred on 2.1, then i dropped back to 2.0 and it
reoccurred. Now back on 1.0 again.

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

Title:
  coping files to cifs mounted directory causes general protection fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  Copy some large files from local filesystem to CIFS mounted
  filesystem. After some gigabytes, it syslog will show "general
  protection fault" and mounted file system will become unresponsive.

  How often does it occur:

  Every time, after a few minutes or so.

  Affected kernels:

  Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 
4.16.13-041613-generic from ubuntu archives an got similar GPF.
  4.13.0-43-generic from ubuntu 17.10 not affected.

  More information:

  I have kerberos authenticated, autofs mounted, cifs
  Mounted with:
  type cifs 
(rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbarlow2249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 17 23:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e
  InstallationDate: Installed on 2017-11-26 (203 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago)
  WifiSyslog:

  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 06CC14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+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 1787945] Re: Tango platform uses __initcall without further checks

2018-09-15 Thread Marc Dietrich
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Tango platform uses __initcall without further checks

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

Bug description:
  Impact:

  The TANGO platform (an embedded soc used in home entertainment,
  connectivity and control devices) is enabled by default in the generic
  arm kernel. During kernel bootup, the tango platform blindly registers
  its pm ops in arch/arm/mach-tango/pm.c via initcalls() (without
  checking whether it's actually running on the correspondent hardware)
  and this causes OOPS during suspend on tegra platforms since the tango
  pm .enter function directly pokes the underlying hardware.

  Given the narrow scope of this SOC, i propose to disable support for
  the TANGO arch.

  Fix:

  Apply the attached patch and recompile.

  How to test:

  Suspend the tegra board and chek that it worked - either close the laptop
  lid, 'systemctl suspend' or:

  # echo -n mem > /sys/power/state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1773581] Re: [Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43

2018-09-15 Thread Jonas Lippuner
*** This bug is a duplicate of bug 1773520 ***
https://bugs.launchpad.net/bugs/1773520

Thank you so much Frank for digging down into this issue! I had to use
kernel 4.13.0-1 until now. I can confirm that it's fixed in kernel
4.18.0-1.

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

Title:
  [Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After updating my Ubuntu 16.04 kernel from 4.13.0-41 to 4.13.0-43, I
  am seeing horizontal lines on the display. Rebooting into -41 makes
  them disappear. This is most likely the same problem as seen in 18.04
  by another user:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204 (also see
  the attached photo there)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 26 22:56:48 2018
  InstallationDate: Installed on 2014-05-19 (1468 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwinkl 2305 F pulseaudio
   /dev/snd/controlC1:  fwinkl 2305 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=00a4b15e-a4f1-4b35-9c8a-5ea33b1c6762
  InstallationDate: Installed on 2014-05-19 (1468 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  NonfreeKernelModules: openafs
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ed5ec6cc-07cf-4e98-8b4e-efa0ba2d07a9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  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.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.157.18
  Tags:  xenial
  Uname: Linux 4.13.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07ADU.029.141031.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3G-S01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ADU.029.141031.PS:bd10/31/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP07ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-S01US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG SENS
  dmi.product.name: 900X3G
  dmi.product.version: P07ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773581/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-09-15 Thread NJ
I am on Mint 19 with kernel 20KHCTO1WW on a X1 model 20KHCTO1WW. I would
be happy to contribute to any necessary testing. I use the synaptic
touchpad 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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.ty

[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839

2018-09-15 Thread Mathew Hodson
** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-8839

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Won't Fix
Status in linux-armadaxp source package in Vivid:
  Won't Fix
Status in linux-flo source package in Vivid:
  Won't Fix
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Won't Fix
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  Won't Fix
Status in linux-lts-trusty source package in Vivid:
  Won't Fix
Status in linux-lts-utopic source package in Vivid:
  Won't Fix
Status in linux-lts-vivid source package in Vivid:
  Won't Fix
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  Won't Fix
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  Won't Fix
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  Won't Fix
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in 

[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839

2018-09-15 Thread Mathew Hodson
** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-8839

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Won't Fix
Status in linux-armadaxp source package in Vivid:
  Won't Fix
Status in linux-flo source package in Vivid:
  Won't Fix
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Won't Fix
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  Won't Fix
Status in linux-lts-trusty source package in Vivid:
  Won't Fix
Status in linux-lts-utopic source package in Vivid:
  Won't Fix
Status in linux-lts-vivid source package in Vivid:
  Won't Fix
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  Won't Fix
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  Won't Fix
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  Won't Fix
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-m

[Kernel-packages] [Bug 1780894] Re: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

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

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

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

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw have previously been installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-112-generic:4.4.0-112.135
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
  InstallationDate: Installed on 2015-09-22 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780894/+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 1781601] Re: Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy css_killed_work_fn)

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

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

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

Title:
  Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy
  css_killed_work_fn)

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

Bug description:
  I have been stress-testing LXD and managed to cause the following
  kernel hung:

  [10271.564074] INFO: task systemd:1 blocked for more than 120 seconds.
  [10271.570397]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.577212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.585071] systemd D0 1  0 0x
  [10271.585073] Call Trace:
  [10271.585080]  __schedule+0x297/0x8b0
  [10271.585086]  schedule+0x2c/0x80
  [10271.585090]  schedule_preempt_disabled+0xe/0x10
  [10271.585095]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.585100]  __mutex_lock_slowpath+0x13/0x20
  [10271.585101]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.585102]  mutex_lock+0x2f/0x40
  [10271.585106]  proc_cgroup_show+0x4c/0x2a0
  [10271.585108]  proc_single_show+0x56/0x80
  [10271.585111]  seq_read+0xe5/0x430
  [10271.585114]  __vfs_read+0x1b/0x40
  [10271.585115]  vfs_read+0x8e/0x130
  [10271.585117]  SyS_read+0x55/0xc0
  [10271.585120]  do_syscall_64+0x73/0x130
  [10271.585121]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.585123] RIP: 0033:0x7fd47634d0b4
  [10271.585124] RSP: 002b:7ffe9a186700 EFLAGS: 0246 ORIG_RAX: 

  [10271.585125] RAX: ffda RBX: 0021 RCX: 
7fd47634d0b4
  [10271.585126] RDX: 0400 RSI: 55f70a08c0c0 RDI: 
0021
  [10271.585127] RBP: 55f70a08c0c0 R08:  R09: 

  [10271.585128] R10:  R11: 0246 R12: 
0400
  [10271.585129] R13: 7fd4766252a0 R14: 55f70a0298e0 R15: 
07ff
  [10271.585221] INFO: task lxcfs:84510 blocked for more than 120 seconds.
  [10271.591687]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.598531] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.606401] lxcfs   D0 84510  1 0x
  [10271.606407] Call Trace:
  [10271.606416]  __schedule+0x297/0x8b0
  [10271.606418]  schedule+0x2c/0x80
  [10271.606420]  schedule_preempt_disabled+0xe/0x10
  [10271.606421]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.606423]  __mutex_lock_slowpath+0x13/0x20
  [10271.606424]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.606425]  mutex_lock+0x2f/0x40
  [10271.606427]  proc_cgroup_show+0x4c/0x2a0
  [10271.606429]  proc_single_show+0x56/0x80
  [10271.606432]  seq_read+0xe5/0x430
  [10271.606434]  __vfs_read+0x1b/0x40
  [10271.606436]  vfs_read+0x8e/0x130
  [10271.606437]  SyS_read+0x55/0xc0
  [10271.606440]  do_syscall_64+0x73/0x130
  [10271.606441]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.606443] RIP: 0033:0x7f1a50e700b4
  [10271.606443] RSP: 002b:7f1a2b7fd870 EFLAGS: 0246 ORIG_RAX: 

  [10271.606445] RAX: ffda RBX: 0013 RCX: 
7f1a50e700b4
  [10271.606446] RDX: 0400 RSI: 7f1a04000f90 RDI: 
0013
  [10271.606446] RBP: 7f1a04000f90 R08: 0001 R09: 

  [10271.606447] R10:  R11: 0246 R12: 
0400
  [10271.606448] R13: 7f1a511482a0 R14:  R15: 
7f1a38003a40
  [10271.606450] INFO: task lxcfs:84676 blocked for more than 120 seconds.
  [10271.612911]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.619722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.627577] lxcfs   D0 84676  1 0x
  [10271.627579] Call Trace:
  [10271.627583]  __schedule+0x297/0x8b0
  [10271.627589]  schedule+0x2c/0x80
  [10271.627594]  schedule_preempt_disabled+0xe/0x10
  [10271.627598]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.627600]  __mutex_lock_slowpath+0x13/0x20
  [10271.627601]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.627602]  mutex_lock+0x2f/0x40
  [10271.627604]  proc_cgroup_show+0x4c/0x2a0
  [10271.627606]  proc_single_show+0x56/0x80
  [10271.627608]  seq_read+0xe5/0x430
  [10271.627610]  __vfs_read+0x1b/0x40
  [10271.627611]  vfs_read+0x8e/0x130
  [10271.627613]  SyS_read+0x55/0xc0
  [10271.627615]  do_syscall_64+0x73/0x130
  [10271.627617]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.627618] RIP: 0033:0x7f1a50e700b4
  [10271.627618] RSP: 002b:7f1a297f9870 EFLAGS: 0246 ORIG_RAX: 

  [10271.627620] RAX: ffda RBX: 0014 RCX: 
7f1a50e700b4
  [10271.627620] RDX: 0400 RSI: 7f1a2c001e8

[Kernel-packages] [Bug 1781565] Re: Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A"

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

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

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

Title:
  Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A"

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fairly recently I got an old HP Pavillion 14 laptop and installed
  Kubuntu 17.10 on it. As far as I recall it ran fine, however, not long
  after I upgraded to 18.04 and noticed frequent freezing (approx every
  few hours). When this happens, all of a sudden, the screen just stays
  with it's image immobile and unchanging. There is no visual corruption
  onscreen and even the cursor does not move. Ctrl+alt+F[1-9] and
  alt+ctrl+sysrq+RSEINUB do nothing.

  Often when I look at the logs, at the end of kern.log.1 I see:

  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A (start=96545 end=96546) time 394 us, min 763, max 767, scanline
  start 760, end 778

  Sometimes, earlier on, there is also:

  Could not find key with description: [d4628bf1c812c861]
  process_request_key_err: No key
  Could not find valid key in user session keyring for sig specified in mount 
option: [d4628bf1c812c861]
  One or more global auth toks could not properly register; rc = [-2]
  Error parsing options; rc = [-2]

  I tested, and this also occurs in a brand new live usb of 18.04, and
  noticed that it still happens there, even before any upgrades or
  installation of packages (such as the wireless driver).

  Other than the wireless driver, there are no proprietary drivers
  installed (eg Nvidia, FGLRX etc).

  Is there any more info I can provide to help troubleshoot this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1152 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 13 05:38:09 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ed1ff2d7-7aa5-4119-91ac-2720da50cb7c
  InstallationDate: Installed on 2018-03-20 (115 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=dabc38a5-afcf-4cec-be94-9ee49972e248 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (52 days ago)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781565/+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 1781023] Re: Fan noise

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

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

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

Title:
  Fan noise

Status in linux package in Ubuntu:
  Expired

Bug description:
  After recent kernel update my laptop (Thinkpad T470s) fan is always on
  max speed. It sometimes happens right after reboot and sometimes after
  first suspend. I have now after the problem occurred installed
  thinkfan and when I issue sudo /etc/init.d/thinkfan start then the fan
  speed goes back to normal (i.e. dependent on temperature).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mf 1791 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Jul 10 20:40:35 2018
  HibernationDevice: RESUME=UUID=5e0d645b-0af2-4683-b461-99416333d8b5
  InstallationDate: Installed on 2018-06-19 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HF0047MX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET35W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0047MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET35W(1.14):bd07/12/2017:svnLENOVO:pn20HF0047MX:pvrThinkPadT470s:rvnLENOVO:rn20HF0047MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0047MX
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781023/+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 1780939] Re: Drivers for Scanner Epson not work

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

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

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

Title:
  Drivers for Scanner Epson not work

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  After enw install my scanner Epson not work (Kernel 4.15.0-24) !!

  Since you changed the location of the drivers in the kernel, it is no
  longer possible to run my scanner Epson V300 Photo !!??

  I already had the same type of problems with the sound in Display Port
  that was not working after the transition to the 4.15.0-20 kernel 
  I presume that all the equipment whose driver is not included in the
  kernel are affected 

  What are you doing ??!! You play sorcerer's apprentice on the back of your 
users ??!!
  .
  Thank you for fixing this urgently, I need to use my scanner...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  philippe   3515 F pulseaudio
   /dev/snd/controlC0:  philippe   3515 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-07-03 (6 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  IwConfig:
   enp15s0   no wireless extensions.
   
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a8544fdd-b93a-4922-baaa-657b74de69be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd03/01/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-EWS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780939/+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 1781326] Re: Ubuntu freezes randomly

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

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

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

Title:
  Ubuntu freezes randomly

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I am running Ubuntu, it sometimes freezes and I can move the
  mouse but can't affect anything else. It is very frustrating because
  it is often in the middle of doing something.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 21:44:33 2018
  InstallationDate: Installed on 2018-07-10 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781326/+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 1781601] Re: Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy css_killed_work_fn)

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

** Changed in: linux (Ubuntu Bionic)
   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/1781601

Title:
  Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy
  css_killed_work_fn)

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

Bug description:
  I have been stress-testing LXD and managed to cause the following
  kernel hung:

  [10271.564074] INFO: task systemd:1 blocked for more than 120 seconds.
  [10271.570397]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.577212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.585071] systemd D0 1  0 0x
  [10271.585073] Call Trace:
  [10271.585080]  __schedule+0x297/0x8b0
  [10271.585086]  schedule+0x2c/0x80
  [10271.585090]  schedule_preempt_disabled+0xe/0x10
  [10271.585095]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.585100]  __mutex_lock_slowpath+0x13/0x20
  [10271.585101]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.585102]  mutex_lock+0x2f/0x40
  [10271.585106]  proc_cgroup_show+0x4c/0x2a0
  [10271.585108]  proc_single_show+0x56/0x80
  [10271.585111]  seq_read+0xe5/0x430
  [10271.585114]  __vfs_read+0x1b/0x40
  [10271.585115]  vfs_read+0x8e/0x130
  [10271.585117]  SyS_read+0x55/0xc0
  [10271.585120]  do_syscall_64+0x73/0x130
  [10271.585121]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.585123] RIP: 0033:0x7fd47634d0b4
  [10271.585124] RSP: 002b:7ffe9a186700 EFLAGS: 0246 ORIG_RAX: 

  [10271.585125] RAX: ffda RBX: 0021 RCX: 
7fd47634d0b4
  [10271.585126] RDX: 0400 RSI: 55f70a08c0c0 RDI: 
0021
  [10271.585127] RBP: 55f70a08c0c0 R08:  R09: 

  [10271.585128] R10:  R11: 0246 R12: 
0400
  [10271.585129] R13: 7fd4766252a0 R14: 55f70a0298e0 R15: 
07ff
  [10271.585221] INFO: task lxcfs:84510 blocked for more than 120 seconds.
  [10271.591687]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.598531] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.606401] lxcfs   D0 84510  1 0x
  [10271.606407] Call Trace:
  [10271.606416]  __schedule+0x297/0x8b0
  [10271.606418]  schedule+0x2c/0x80
  [10271.606420]  schedule_preempt_disabled+0xe/0x10
  [10271.606421]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.606423]  __mutex_lock_slowpath+0x13/0x20
  [10271.606424]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.606425]  mutex_lock+0x2f/0x40
  [10271.606427]  proc_cgroup_show+0x4c/0x2a0
  [10271.606429]  proc_single_show+0x56/0x80
  [10271.606432]  seq_read+0xe5/0x430
  [10271.606434]  __vfs_read+0x1b/0x40
  [10271.606436]  vfs_read+0x8e/0x130
  [10271.606437]  SyS_read+0x55/0xc0
  [10271.606440]  do_syscall_64+0x73/0x130
  [10271.606441]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.606443] RIP: 0033:0x7f1a50e700b4
  [10271.606443] RSP: 002b:7f1a2b7fd870 EFLAGS: 0246 ORIG_RAX: 

  [10271.606445] RAX: ffda RBX: 0013 RCX: 
7f1a50e700b4
  [10271.606446] RDX: 0400 RSI: 7f1a04000f90 RDI: 
0013
  [10271.606446] RBP: 7f1a04000f90 R08: 0001 R09: 

  [10271.606447] R10:  R11: 0246 R12: 
0400
  [10271.606448] R13: 7f1a511482a0 R14:  R15: 
7f1a38003a40
  [10271.606450] INFO: task lxcfs:84676 blocked for more than 120 seconds.
  [10271.612911]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.619722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.627577] lxcfs   D0 84676  1 0x
  [10271.627579] Call Trace:
  [10271.627583]  __schedule+0x297/0x8b0
  [10271.627589]  schedule+0x2c/0x80
  [10271.627594]  schedule_preempt_disabled+0xe/0x10
  [10271.627598]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.627600]  __mutex_lock_slowpath+0x13/0x20
  [10271.627601]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.627602]  mutex_lock+0x2f/0x40
  [10271.627604]  proc_cgroup_show+0x4c/0x2a0
  [10271.627606]  proc_single_show+0x56/0x80
  [10271.627608]  seq_read+0xe5/0x430
  [10271.627610]  __vfs_read+0x1b/0x40
  [10271.627611]  vfs_read+0x8e/0x130
  [10271.627613]  SyS_read+0x55/0xc0
  [10271.627615]  do_syscall_64+0x73/0x130
  [10271.627617]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.627618] RIP: 0033:0x7f1a50e700b4
  [10271.627618] RSP: 002b:7f1a297f9870 EFLAGS: 0246 ORIG_RAX: 

  [10271.627620] RAX: ffda RBX: 0014 RCX: 
7f1a50e700b4
  [10271.627620] RDX: 0400 RSI: 0

[Kernel-packages] [Bug 1781259] Re: quickbooks not working properly

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

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

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

Title:
  quickbooks not working properly

Status in linux package in Ubuntu:
  Expired

Bug description:
  quickbooks is not working properly as it crashes on reguarly when the
  speed of internet is slow

  Printing errors about report generated through QuickBooks.

  Any error related to the entry and the transaction done on the
  QuickBooks http://setupyour-office.us/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781259/+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 1780653] Re: my ubuntu partition does not restart

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

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

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

Title:
  my ubuntu partition does not restart

Status in linux package in Ubuntu:
  Expired

Bug description:
  when i put my laptop in the pose mode or when i close my laptop and  i
  reopen it there is no responce from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul  8 16:16:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8101]
 Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] 
[103c:811c]
  InstallationDate: Installed on 2017-05-18 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: HP HP ProBook 450 G3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ac6b4707-30fd-4b3b-8710-48d6f01a6ca1 ro plymouth:debug 
vesafb.invalid=1 nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.15
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.63
  dmi.chassis.asset.tag: 5CD6074RF7
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.15:bd11/07/2016:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion40.63:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Aug 11 23:29:19 2017
  xserver.configfile: default
  xserver.errors: modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780653/+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 1780976] Re: After upgrading to linux-image-4.15.0-24-generic, Xubuntu 18.04 LTS boots to blank screen

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

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

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

Title:
  After upgrading to linux-image-4.15.0-24-generic, Xubuntu 18.04 LTS
  boots to blank screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  On HP laptop model 15-AC106NQ running Xubuntu 18.04 LTS I have
  upgraded the kernel from linux-image-4.15.0-23-generic 4.15.0-23.25
  AMD64 Signed to the new kernel linux-image-4.15.0-24-generic
  4.15.0-24.26 AMD64 Signed.

  After this, the computer boots to blank screen and is freezing. If I
  push random keys multiple times or if I keep switching between ttys,
  the computer shows after one minute the Xubuntu login screen. If I
  chose from the Grub menu the old linux-image-4.15.0-23-generic kernel,
  the computer boots very fast directly into graphic mode as it should.
  I was able to successfully use all the old Ubuntu/Xubuntu LTS versions
  on this HP laptop.

  Thank you.

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

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

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  Could not boot stuck on gnome display error and hung the system so had
  to reinstall Ubuntu desktop after purging.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: i915 sky2 wmi
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Jul  8 06:33:32 2018
  ErrorMessage: installed linux-image-4.15.0-24-generic package pre-removal 
script subprocess returned error exit status 1
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Acer Veriton L480
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=aaa55d54-7874-44b3-b02c-833cf31dc238 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: installed linux-image-4.15.0-24-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A2
  dmi.board.name: EG43LMK
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A2:bd05/25/2009:svnAcer:pnVeritonL480:pvr:rvnAcer:rnEG43LMK:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Veriton L480
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780591/+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 1780519] Re: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it

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

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

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

Title:
  Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe
  ASPM, so disable it

Status in linux package in Ubuntu:
  Expired

Bug description:
  dmesg | grep ASPM
  [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so 
disable it
  [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM 
ClockPM Segments MSI]
  [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using 
BIOS configuration
  [3.144009] pci :00:01.0: ASPM: Could not configure common clock
  [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1852 F pulseaudio
   /dev/snd/controlC0:  hp 1852 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074
  InstallationDate: Installed on 2018-07-06 (0 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic 
root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.68
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+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 1780732] Re: Keyboard not working Toshiba Satelite C40-B

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

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

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

Title:
  Keyboard not working Toshiba Satelite C40-B

Status in linux package in Ubuntu:
  Expired

Bug description:
  Keyboard suddenly off, previously working fine

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 [modified: 
boot/vmlinuz-4.13.0-36-generic]
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul  9 13:02:06 2018
  InstallationDate: Installed on 2018-07-05 (3 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780732/+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 1780409] Re: wifi on 16.04

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

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

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

Title:
  wifi on 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Has trouble finding my router wifi. Sometimes finds my neighbour's but not 
mine. Others do not have this problem. Advice in Help sometimes works to 
connect.
  When found, the connection 'arcs' icon shows a connection but then changes to 
the double arrow logo (usually associated with wire connection).
  Currently connected but showing double arrow. Drop-down menu shows no 
available wifi's.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul  6 10:21:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:161c]
  InstallationDate: Installed on 2018-02-18 (137 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=533de285-2d90-4e13-8140-a65b8d250094 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.08
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.45
  dmi.chassis.asset.tag: m705800
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jul  5 13:59:06 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780409/+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 1780880] Re: Upgrade ubuntu 14.04 to 16.04 crash

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

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

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

Title:
  Upgrade ubuntu 14.04 to 16.04 crash

Status in linux package in Ubuntu:
  Expired

Bug description:
  When i am trying tu uipgarde from 14,04 to 16.04 (ubuntu)
  when the process starts, a crash occurs:
  first step {preparandola actualizacion} "preparing the update" runs ok.
  the process crash in the "second step" called {configurando nuevos canales de 
software} "configuring new software channels" with the error message {No se ha 
podido calcular la actualizacion} "enable to calculate the update" 
  the third possible cause is {paquetes no oficiales de software no 
proporcionados por ubuntu} "non-official packages don't provided for ubuntu" 
looks is my issue. I have disabled third part sources from the configuration, 
but there must be something else because it even does not work.
  Please help "all of us" with this issue to be able to upgrade to ubuntu 16.04 
(in order to go to ubuntu 18.04 already available)
  Thanks in advance.
  lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-153-generic 3.13.0-153.203
  ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juan   2042 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  9 18:33:25 2018
  HibernationDevice: RESUME=UUID=d636c2b9-ed1b-472f-93c6-12845c9560d1
  InstallationDate: Installed on 2016-02-09 (881 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: Dell Inc. Inspiron 1440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=3ec0f1ba-dc84-47b0-9fec-4595cd904f69 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-153-generic N/A
   linux-backports-modules-3.13.0-153-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2018-06-19 (20 days ago)
  dmi.bios.date: 07/29/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0K138P
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/29/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1440
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780880/+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 1780625] Re: VirtualBox 5.1.34 Will Not Run

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

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

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

Title:
  VirtualBox 5.1.34 Will Not Run

Status in linux package in Ubuntu:
  Expired

Bug description:
  VirtualBox 5.1.34 fails to run a Virtual Machine.
  Issue with 'vboxdrv'.

  Solution: use earlier kernel.

  I went back to: 4.13.0-45-generic, the last of the 4.13 series.
  And now VirtualBox works as it should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780625/+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 1780785] Re: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

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

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

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

Title:
  package linux-image-generic 4.4.0.130.136 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux package in Ubuntu:
  Expired

Bug description:
  ACTUALICE PERO DIO ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.130.136
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   2014 F pulseaudio
  Date: Mon Jul  9 15:17:46 2018
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=66ae5499-615e-492d-a994-812d1bf2e83d
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=75eda110-9722-43fc-b193-0c6320275164 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733Z:pvrV1.08:rvnAcer:rnAspire5733Z:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780785/+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 1780530] Re: Failed to shut down after upgrading to 4.15.0-24

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

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

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

Title:
  Failed to shut down after upgrading to 4.15.0-24

Status in linux package in Ubuntu:
  Expired

Bug description:
  Attached log is generated after reverting to 4.15.0-23, which has no issues.
  When attempting to shut down (@4.15.0-24), a stop job is running for 
wpa-supplicant for minutes. If the ath10k_pci module is removed (modprobe -r) 
prior to shut down, it proceeds normally. 

  lspci -vnvn:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 20)
Subsystem: Foxconn International, Inc. QCA6174 802.11ac Wireless 
Network Adapter [105b:e08e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcus 2076 F pulseaudio
   /dev/snd/controlC0:  marcus 2076 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul  7 16:17:14 2018
  HibernationDevice: RESUME=UUID=0a5a6389-aa92-432e-a526-72700263a7dd
  InstallationDate: Installed on 2018-03-19 (109 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  MachineType: Acer Aspire V3-574TG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=b21a6b20-bc20-4324-881c-c7e7df439dcd ro splash acipi_osi=!Windows 
2012 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-26 (41 days ago)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: USOPP_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd05/27/2015:svnAcer:pnAspireV3-574TG:pvrV3.72:rvnAcer:rnUSOPP_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire V3-574TG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780530/+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 1705784] Re: Ubuntu refuses to recognize Wacom stylus

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

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

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

Title:
  Ubuntu refuses to recognize Wacom stylus

Status in linux package in Ubuntu:
  Expired

Bug description:
  no point in owning a tablet if it can't be used

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  Date: Fri Jul 21 22:25:30 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705784/+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 1423631] Re: tap interface drops many packets on highload systems

2018-09-15 Thread Satish Patel
We are having same issue on CentOS7 and i have increase tx_queue upto
1 but i am still seeing TX drops on tap interface.

Question:

Can i increase tx_queue on interface with "ifconfig 
txqueue 1" without rebooting machine?

OR

I have to do it at boot time?

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

Title:
  tap interface drops many packets on highload systems

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  Incomplete

Bug description:
  I use qemu-kvm in openstack. On highload hypervisor tap interface of 
net-highload guest drops many TX packets.
  Network options of qemu-system-x86_64  "... -netdev 
tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:86:67:7b,bus=pci.0,addr=0x3..."

  Network domin config:

  
    
    
    
    
    
    
  

  tape4009073-0b Link encap:Ethernet  HWaddr fe:16:3e:86:67:7b
    inet6 addr: fe80::fc16:3eff:fe86:677b/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:1587622634 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1484106438 errors:0 dropped:460259 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:877878711500 (877.8 GB)  TX bytes:3071846828531 (3.0 TB)
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 18 12:06 seq
   crw-rw 1 root audio 116, 33 Feb 18 12:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-07-01 (234 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. PowerEdge M620
  Package: qemu-kvm
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5965239d-820a-49a1-9d8e-23a4c1f87ce6 ro
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.7
  dmi.board.name: 0T36VK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 25
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: PowerEdge M1000e
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.7:bd01/21/2014:svnDellInc.:pnPowerEdgeM620:pvr:rvnDellInc.:rn0T36VK:rvrA01:cvnDellInc.:ct25:cvrPowerEdgeM1000e:
  dmi.product.name: PowerEdge M620
  dmi.sys.vendor: Dell Inc.

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