date:20160424

[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/1268669

Title:
  Lenovo T440p (Haswell/NVidia optimus gfx) flaky unless I blacklist
  nouveau

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have a new Lenovo T440p laptop, which has a Haswell CPU and NVidia
  GPU in an "optimus" setup.  In a default 14.04 install, the system is
  quite flaky: suspend doesn't work and doing lspci apparently corrupts
  memory (the system hits random weird failures and then freezes about
  10 seconds after running lspci).  If I blacklist the nouveau module
  then the system seems to work fine (suspend/resume is good and lspci
  doesn't cause problems).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-2-generic 3.13.0-2.17
  ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
  Uname: Linux 3.13.0-2-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 2111 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 13 09:35:00 2014
  HibernationDevice: RESUME=UUID=af5ffc5d-f07d-48f1-8bab-636acd0359be
  InstallationDate: Installed on 2014-01-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
  MachineType: LENOVO 20ANCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-2-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug splash quiet drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-2-generic N/A
   linux-backports-modules-3.13.0-2-generic  N/A
   linux-firmware1.121
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET43WW (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET43WW(1.18):bd12/04/2013:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1536327] Re: [Lenovo G50-30] freezes

[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/1536327

Title:
  [Lenovo G50-30] freezes

Status in linux package in Ubuntu:
  Expired

Bug description:
  My computer freezes. The best one and most reliable that i found was
  kernel 4.1.13-realtime however it has wifi bugs and system freezes as
  well.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  1224 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=8c1be7c0-8725-4999-b281-2c800eb41898
  InstallationDate: Installed on 2016-01-13 (7 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80G0
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-26-generic 
root=UUID=b02421be-8ad3-4413-8476-bf02e076581d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-26.31-generic 4.2.8-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-26-generic N/A
   linux-backports-modules-4.2.0-26-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN48WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN48WW:bd08/03/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1545830] Re: BUG: unable to handle kernel NULL pointer dereference EIP:asus_sysfs_is_visible

[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/1545830

Title:
  BUG: unable to handle kernel NULL pointer dereference
  EIP:asus_sysfs_is_visible

Status in linux package in Ubuntu:
  Expired

Bug description:
  hello,
  i have been hitting this since 4.4.0 linux kernel.
  It boots fine so it doesnt make system unbootable.

  I think this has something to do with the asus_laptop module (my
  laptop is ASUS), but im not sure.

  I attach the complete dmesg output. BUG is at line 830.
  --- 
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   toni   1708 F...m pulseaudio
   /dev/snd/controlC0:  toni   1708 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=963bfe58-9faa-4c89-a33e-31ac1d2cee76
  InstallationDate: Installed on 2015-05-28 (263 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: ASUSTeK Computer INC. K50AF
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=73345602-0907-43e9-91e1-883f6066e57a ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware   1.155
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic i686
  UpgradeStatus: Upgraded to xenial on 2015-12-13 (64 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K50AF
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd07/21/2010:svnASUSTeKComputerINC.:pnK50AF:pvr1.0:rvnASUSTeKComputerINC.:rnK50AF:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
  dmi.product.name: K50AF
  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/1545830/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1574428

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

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

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

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

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

Title:
  Macbook Pro 9, 2 battery readings screwed up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In a fresh Ubuntu 16.04 install, my Macbook does not properly report
  any of the following in the top bar:

  1. Charge. It always says 90-91%.
  2. Charging or not: when the power adapter is plugged in, it claims its not 
plugged in, and the LED is green on the charger; while if its not plugged in, 
it shows the "spark" symbol - thinking it is plugged in.

  After a while of being plugged it registers as plugged in, fully
  charged, even though its only charged ~88%

  I don't know where to start to troubleshoot this.

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

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

[Kernel-packages] [Bug 1574428] Re: Macbook Pro 9, 2 battery readings screwed up

2016-04-24 Thread Willem Hillier

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574428/+attachment/4645999/+files/Screenshot%20from%202016-04-24%2022-50-31.png

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

Title:
  Macbook Pro 9, 2 battery readings screwed up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In a fresh Ubuntu 16.04 install, my Macbook does not properly report
  any of the following in the top bar:

  1. Charge. It always says 90-91%.
  2. Charging or not: when the power adapter is plugged in, it claims its not 
plugged in, and the LED is green on the charger; while if its not plugged in, 
it shows the "spark" symbol - thinking it is plugged in.

  After a while of being plugged it registers as plugged in, fully
  charged, even though its only charged ~88%

  I don't know where to start to troubleshoot this.

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

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

[Kernel-packages] [Bug 1574428] [NEW] Macbook Pro 9, 2 battery readings screwed up

2016-04-24 Thread Willem Hillier

Public bug reported:

In a fresh Ubuntu 16.04 install, my Macbook does not properly report any
of the following in the top bar:

1. Charge. It always says 90-91%.
2. Charging or not: when the power adapter is plugged in, it claims its not 
plugged in, and the LED is green on the charger; while if its not plugged in, 
it shows the "spark" symbol - thinking it is plugged in.

After a while of being plugged it registers as plugged in, fully
charged, even though its only charged ~88%

I don't know where to start to troubleshoot this.

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


** Tags: apple battery mac

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

Title:
  Macbook Pro 9, 2 battery readings screwed up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In a fresh Ubuntu 16.04 install, my Macbook does not properly report
  any of the following in the top bar:

  1. Charge. It always says 90-91%.
  2. Charging or not: when the power adapter is plugged in, it claims its not 
plugged in, and the LED is green on the charger; while if its not plugged in, 
it shows the "spark" symbol - thinking it is plugged in.

  After a while of being plugged it registers as plugged in, fully
  charged, even though its only charged ~88%

  I don't know where to start to troubleshoot this.

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

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

[Kernel-packages] [Bug 1574428] Re: Macbook Pro 9, 2 battery readings screwed up

2016-04-24 Thread Willem Hillier

** Attachment added: "screenshot2"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574428/+attachment/4646000/+files/Screenshot%20from%202016-04-24%2022-50-46.png

** Description changed:

In a fresh Ubuntu 16.04 install, my Macbook does not properly report any
of the following in the top bar:

1. Charge. It always says 90-91%.
2. Charging or not: when the power adapter is plugged in, it claims its not
plugged in, and the LED is green on the charger; while if its not plugged in,
it shows the "spark" symbol - thinking it is plugged in.

After a while of being plugged it registers as plugged in, fully
- charged.
+ charged, even though its only charged ~88%

I don't know where to start to troubleshoot this.

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

Title:
Macbook Pro 9, 2 battery readings screwed up

Status in linux package in Ubuntu:
Incomplete

Bug description:
In a fresh Ubuntu 16.04 install, my Macbook does not properly report
any of the following in the top bar:

After a while of being plugged it registers as plugged in, fully
charged, even though its only charged ~88%

I don't know where to start to troubleshoot this.

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

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

[Kernel-packages] [Bug 1355562] Re: An "Unknown" display appears with no external display connected on 12.04.5

** Tags added: bios-outdated-a19

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+subscriptions

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

[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)

2016-04-24 Thread marco

Hi Christopher, I am ashamed to say, I am using Debian; I am not sure
why I posted this here... Even though in the past I experienced this
multiple times on Ubuntu as well as Mint. If you think it may be of some
help, I can still post my settings, but you will have to tell me how to
produce them since "ubuntu-bug" is not available on Debian.

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

Title:
  High load freezes ubuntu completely everytime (have to reboot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever an intensive application runs which consumes lots of memory
  or hard drive i/o, Ubuntu freezes completely. It is even impossible to
  kill the offending task. Only "solution" is then to wait for the
  application to finish, or restart PC.

  Windows doesn't have this issue as bad as Ubuntu, in that Windows is
  always somewhat responsive, and you can attempt to kill the intensive
  application to recover the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-32-generic 4.2.0-32.37
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-32-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/18210/fd/20: Input/output error
    USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cossio 2082 F pulseaudio
   /dev/snd/controlC1:  cossio 2082 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar  9 22:28:53 2016
  HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac
  InstallationDate: Installed on 2015-08-03 (219 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.505
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  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.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  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/1555351/+subscriptions

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

[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown

2016-04-24 Thread Peter Matulis

I just tried selecting a boot entry in the GRUB menu. It doesn't help.

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1068839] Re: Module tpm_infineon prevents kernel suspend

anville, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Module tpm_infineon prevents kernel suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  version_signature: Ubuntu 3.5.0-17.28-generic 3.5.5

  WORKAROUND: Immediately prior to suspending:
  modprobe -r tpm_infineon

  part of kernel log when it's not working:
  Oct 19 15:46:37 loki kernel: [ 2145.963934] PM: Syncing filesystems ... done.
  Oct 19 15:46:37 loki kernel: [ 2146.491439] PM: Preparing system for mem sleep
  Oct 19 15:46:42 loki kernel: [ 2146.500216] Freezing user space processes ... 
(elapsed 0.01 seconds) done.
  Oct 19 15:46:42 loki kernel: [ 2146.516247] Freezing remaining freezable 
tasks ... (elapsed 0.01 seconds) done.
  Oct 19 15:46:42 loki kernel: [ 2146.532168] PM: Entering mem sleep
  Oct 19 15:46:42 loki kernel: [ 2146.532438] Suspending console(s) (use 
no_console_suspend to debug)
  Oct 19 15:46:42 loki kernel: [ 2146.576414] sd 2:0:1:0: >[sda] Synchronizing 
SCSI cache
  Oct 19 15:46:42 loki kernel: [ 2146.577467] tpm_inf_pnp 00:03: >saving TPM 
state
  Oct 19 15:46:42 loki kernel: [ 2146.595089] tpm_inf_pnp 00:03: >Timeout while 
clearing FIFO
  Oct 19 15:46:42 loki kernel: [ 2146.595092] tpm_inf_pnp 00:03: >error while 
saving TPM state
  Oct 19 15:46:42 loki kernel: [ 2146.595103] legacy_suspend(): 
pnp_bus_suspend+0x0/0x70 returns -5
  Oct 19 15:46:42 loki kernel: [ 2146.595123] PM: Device 00:03 failed to 
suspend: error -5
  Oct 19 15:46:42 loki kernel: [ 2146.813354] sd 2:0:1:0: >[sda] Stopping disk
  Oct 19 15:46:42 loki kernel: [ 2146.948595] PM: suspend of drv:sd dev:2:0:1:0 
complete after 372.190 msecs
  Oct 19 15:46:42 loki kernel: [ 2146.948642] PM: Some devices failed to suspend
  Oct 19 15:46:42 loki kernel: [ 2146.951168] sd 2:0:1:0: >[sda] Starting disk

  log information when tpm_infineon is loaded:
  Oct 19 16:01:35 loki kernel: [ 3044.447305] tpm_inf_pnp 00:03: >Found TPM 
with ID IFX0101
  Oct 19 16:01:35 loki kernel: [ 3044.447375] tpm_inf_pnp 00:03: >TPM found: 
config base 0x4e, data base 0x4700, chip version 0x000b, vendor id 0x15d1 
(Infineon), product id 0x000b (SLB 9635 TT 1.2)

  part of successful suspend behavior after "modprobe -r tpm_infineon":
  Oct 19 16:10:58 loki kernel: [ 3603.184426] PM: Syncing filesystems ... done.
  Oct 19 16:10:58 loki kernel: [ 3603.194924] PM: Preparing system for mem sleep
  Oct 19 16:12:32 loki kernel: [ 3603.211750] Freezing user space processes ... 
(elapsed 0.01 seconds) done.
  Oct 19 16:12:32 loki kernel: [ 3603.228207] Freezing remaining freezable 
tasks ... (elapsed 0.01 seconds) done.
  Oct 19 16:12:32 loki kernel: [ 3603.244163] PM: Entering mem sleep
  Oct 19 16:12:32 loki kernel: [ 3603.244428] Suspending console(s) (use 
no_console_suspend to debug)
  Oct 19 16:12:32 loki kernel: [ 3603.248241] sd 2:0:1:0: >[sda] Synchronizing 
SCSI cache
  Oct 19 16:12:32 loki kernel: [ 3603.249462] ata_piix :00:1f.1: >power 
state changed by ACPI to D3
  Oct 19 16:12:32 loki kernel: [ 3603.249691] pciehp :00:1c.0:pcie04: 
>pciehp_suspend ENTRY
  Oct 19 16:12:32 loki kernel: [ 3603.264125] pciehp :00:1c.1:pcie04: 
>pciehp_suspend ENTRY
  Oct 19 16:12:32 loki kernel: [ 3603.368026] PM: suspend of drv:snd_hda_intel 
dev::00:1b.0 complete after 118.325 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.368177] sd 2:0:1:0: >[sda] Stopping disk
  Oct 19 16:12:32 loki kernel: [ 3603.506384] PM: suspend of drv:sd dev:2:0:1:0 
complete after 258.143 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.506405] PM: suspend of drv:scsi 
dev:target2:0:1 complete after 258.068 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.506413] PM: suspend of drv:scsi dev:host2 
complete after 257.796 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.506450] PM: suspend of drv: dev:ata3 
complete after 257.767 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.520041] PM: suspend of drv:ata_piix 
dev::00:1f.2 complete after 270.699 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.600043] PM: suspend of drv:radeon 
dev::01:00.0 complete after 350.769 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.600065] PM: suspend of drv:pcieport 
dev::00:01.0 complete after 350.332 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.600088] PM: suspend of drv: 
dev:pci:00 complete after 350.294 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.600104] PM: suspend of devices complete 
after 355.380 msecs
  Oct 19 16:12:32 loki kernel: [ 3603.600106] PM: suspend devices took 0.356 
seconds
  Oct 19 16:12:32 loki kernel: [ 3603.600357] PM: late

[Kernel-packages] [Bug 1520978] Re: [MacBook1, 1] Suspend fails with error code 38

** This bug is no longer a duplicate of bug 1068839
   Module tpm_infineon prevents kernel suspend

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

Title:
  [MacBook1,1] Suspend fails with error code 38

Status in linux package in Ubuntu:
  Expired

Bug description:

  nov 29 20:11:27 stinky kernel: sd 2:0:1:0: [sda] Stopping disk
  nov 29 20:11:27 stinky kernel: tpm_inf_pnp 00:01: Error (38) sending 
savestate before suspend
  nov 29 20:11:27 stinky kernel: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x1e0 
returns 38
  nov 29 20:11:27 stinky kernel: dpm_run_callback(): pnp_bus_suspend+0x0/0x20 
returns 38
  nov 29 20:11:27 stinky kernel: PM: Device 00:01 failed to suspend: error 38
  nov 29 20:11:27 stinky kernel: PM: Some devices failed to suspend, or early 
wake event detected
  nov 29 20:11:27 stinky kernel: rtc_cmos 00:04: System wakeup disabled by ACPI
  nov 29 20:11:27 stinky kernel: sd 2:0:1:0: [sda] Starting disk
  nov 29 20:11:27 stinky kernel: PM: resume of devices complete after 89.724 
msecs

  Attaching the dmesg log surrounding the 'sudo pm-suspend' action as
  suspend.log, full dmesg in a separate file.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fredrik1569 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Nov 29 20:14:31 2015
  HibernationDevice: RESUME=UUID=92e841bc-e3de-4914-93cc-908fa8d2a504
  MachineType: Apple Computer, Inc. MacBook1,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=850c48ad-e474-4613-8bb4-1f2fec700555 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/06
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MB11.88Z.0061.B03.0610121324
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4208CC8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208CC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMB11.88Z.0061.B03.0610121324:bd10/12/06:svnAppleComputer,Inc.:pnMacBook1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208CC8:rvrPVT:cvnAppleComputer,Inc.:ct10:cvrMac-F4208CC8:
  dmi.product.name: MacBook1,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

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

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

[Kernel-packages] [Bug 1422338] Re: I/O errors on mmc partitions

Lukas, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  I/O errors on mmc partitions

Status in linux package in Ubuntu:
  Expired

Bug description:
  Running live USB of the latest Vivid daily build on Lenovo Thinkpad 10
  with Samsung eMMC MDGAGC 116 GiB:

  Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
  Linux 3.18.0-13-generic
  systemd 218-10ubuntu1

  Extract of dmesg (full log in attachment):

  [ 12.337332] mmc0: BKOPS_EN bit is not set
  [ 12.348788] mmc0: new HS200 MMC card at address 0001
  ...
  [ 12.369112] mmcblk0: mmc0:0001 MDGAGC 116 GiB
  [ 12.369786] mmcblk0boot0: mmc0:0001 MDGAGC partition 1 4.00 MiB
  [ 12.370414] mmcblk0boot1: mmc0:0001 MDGAGC partition 2 4.00 MiB
  [ 12.370976] mmcblk0rpmb: mmc0:0001 MDGAGC partition 3 4.00 MiB
  [ 12.376682] mmcblk0: p1 p2 p3 p4

  I get multiple errors when trying to access to mmc partitions:

  [ 21.950514] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 21.950537] mmc0: Got data interrupt 0x0060 even though no data 
operation was in progress.
  [ 21.952904] mmc0: Got data interrupt 0x0002 even though no data 
operation was in progress.
  [ 21.955002] mmcblk0: error -110 sending stop command, original cmd response 
0x900, card status 0x400900
  [ 21.955007] mmcblk0: error -84 transferring data, sector 244277120, nr 8, 
cmd response 0x900, card status 0x0
  [ 21.955011] mmcblk0: retrying using single block read
  ...
  [ 22.197516] mmcblk0boot0: error -84 transferring data, sector 8071, nr 1, 
cmd response 0x900, card status 0x0
  [ 22.199814] mmc0: Got data interrupt 0x0002 even though no data 
operation was in progress.
  [ 22.201911] mmcblk0boot1: error -110 sending stop command, original cmd 
response 0x900, card status 0x400900
  [ 22.201914] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, 
cmd response 0x900, card status 0x0
  [ 22.201917] mmcblk0boot1: retrying using single block read
  ...
  [ 22.241280] Buffer I/O error on dev mmcblk0boot0, logical block 1008, async 
page read
  [ 22.244301] mmc0: Got data interrupt 0x0002 even though no data 
operation was in progress.
  [ 22.246331] mmcblk0boot1: error -110 sending stop command, original cmd 
response 0x900, card status 0x400900
  [ 22.246335] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, 
cmd response 0x900, card status 0x0
  [ 22.246337] mmcblk0boot1: retrying using single block read
  [ 22.248553] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, 
cmd response 0x900, card status 0x0
  ...
  [ 22.265044] Buffer I/O error on dev mmcblk0boot1, logical block 1008, async 
page read

  Ubiquity reports "Input/output errors" consequently, I'm unable to
  install Ubuntu on mmcblk0 device.

  Content of /sys/block/mmcblk0:

  alignment_offset
  bdi
  capability
  dev
  device
  discard_alignment
  ext_range
  force_ro
  holders
  inflight
  mmcblk0boot0
  mmcblk0boot1
  mmcblk0p1
  mmcblk0p2
  mmcblk0p3
  mmcblk0p4
  mmcblk0rpmb
  power
  queue
  range
  removable
  ro
  size
  slaves
  stat
  subsystem
  trace
  uevent

  I don't know if it's related, but I also get a warning from libparted:

  sudo parted -l
  Warning: The driver descriptor says the physical block size is 2048 bytes, but
  Linux says it is 512 bytes.
  Ignore/Cancel? i  

  Error: /dev/mmcblk0rpmb: unrecognised disk label
  Model: Generic SD/MMC Storage Card (sd/mmc)   
  Disk /dev/mmcblk0rpmb: 4194kB
  Sector size (logical/physical): 512B/512B
  Partition Table: unknown
  Disk Flags: 

  Error: /dev/mmcblk0boot0: unrecognised disk label
  Model: Generic SD/MMC Storage Card (sd/mmc)   
  Disk /dev/mmcblk0boot0: 4194kB
  Sector size (logical/physical): 512B/512B
  Partition Table: unknown
  Disk Flags: 

  Error: /dev/mmcblk0boot1: unrecognised disk label
  Model: Generic SD/MMC Storage Card (sd/mmc)   
  Disk /dev/mmcblk0boot1: 4194kB
  Sector size (logical/physical): 512B/512B
  Partition Table: unknown
  Disk Flags: 

  Model: MMC MDGAGC (sd/mmc)
  Disk /dev/mmcblk0: 125GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt
  Disk Flags: 

  Number  Start   EndSizeFile system  Name  
Flags
   1  1049kB  274MB  273MB   fat32EFI system partition  
boot, esp
   2  274MB   408MB  134MBMicrosoft reserved partition  
msftres
   3  408MB   113GB  113GB   ntfs Basic data

[Kernel-packages] [Bug 1549197] Re: Hard lockup on HP ENVY 13

Serrie, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Hard lockup on HP ENVY 13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Desktop clock showed 09:11:36

  Had to restart whole machine.

  syslog shows stuff like

  Feb 24 09:11:29 MFT-U017 kernel: [67990.662920] WARNING: CPU: 2 PID: 950 at 
/build/linux-MmY1jo/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]()
  Feb 24 09:11:29 MFT-U017 kernel: [67990.662926] WARN_ON(!wm_changed)
  Feb 24 09:11:29 MFT-U017 kernel: [67990.662930] Modules linked in: xt_nat 
xt_tcpudp veth rfcomm ctr ccm xt_conntrack ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables x_tables nf_nat nf_conntrack br_netfilter 
bridge stp llc aufs bnep arc4 nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core iwlmvm snd_hwdep i2c_designware_platform hp_wmi 
i2c_designware_core sparse_keymap mac80211 snd_pcm intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi snd_seq_midi kvm 
snd_seq_midi_event cfg80211 snd_rawmidi snd_seq snd_seq_device snd_timer snd 
serio_raw btusb soundcore btrtl uvcvideo videobuf2_vmalloc btbcm btintel 
videobuf2_memops bluetooth videobuf2_core idma64 shpchp virt_dma v4l2_common 
videodev joydev input_leds mei_me media mei intel_lpss_pci 
processor_thermal_device int340x_thermal_zone intel_soc_dts_iosf hp_accel 
lis3lv02d input_polldev int3400_thermal intel_lpss_acpi acpi_thermal_rel 
intel_lpss tpm_crb hp_wireless acpi_pad mac_hid parport_pc ppdev lp parport 
autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid 
crct10dif_pclmul crc32_pclmul aesni_intel i915 aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper psmouse drm ahci 
libahci i2c_hid wmi hid pinctrl_sunrisepoint pinctrl_intel video
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663190] CPU: 2 PID: 950 Comm: Xorg 
Tainted: GW   4.2.0-30-generic #35-Ubuntu
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663196] Hardware name: HP HP ENVY 
Notebook/80DF, BIOS F.16 08/21/2015
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663202]   
4e8f8ba8 880265c43518 817ebf13
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663213]   
880265c43570 880265c43558 8107b9d6
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663222]  880265c43620 
880265c436c4 880082a5e000 880082a5f000
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663232] Call Trace:
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663253]  [] 
dump_stack+0x45/0x57
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663268]  [] 
warn_slowpath_common+0x86/0xc0
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663279]  [] 
warn_slowpath_fmt+0x55/0x70
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663332]  [] 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663372]  [] 
skl_update_wm+0x1bb/0x740 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663449]  [] ? 
gen9_read32+0xf7/0x2d0 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663514]  [] ? 
i915_get_vblank_timestamp+0x62/0xa0 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663566]  [] 
intel_update_watermarks+0x1e/0x30 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663647]  [] 
intel_finish_crtc_commit+0x169/0x190 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663689]  [] 
drm_atomic_helper_commit_planes_on_crtc+0x143/0x260 [drm_kms_helper]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663779]  [] 
intel_atomic_commit+0x6b/0x100 [i915]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663839]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663867]  [] 
drm_atomic_helper_disable_plane+0xef/0x130 [drm_kms_helper]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663920]  [] 
__setplane_internal+0x23a/0x2f0 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663973]  [] 
drm_mode_cursor_universal+0x12b/0x210 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.663991]  [] ? 
__ww_mutex_lock+0x5f/0xa0
  Feb 24 09:11:29 MFT-U017 kernel: [67990.664037]  [] 
drm_mode_cursor_common+0x81/0x180 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.664086]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.664114]  [] 
drm_ioctl+0x125/0x610 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.664157]  [] ? 
drm_mode_setcrtc+0x500/0x500 [drm]
  Feb 24 09:11:29 MFT-U017 kernel: [67990.664175]  [] 
do_vfs_ioctl+0x295/0x480
  Feb 24 09:11:29 MFT-U017 kernel:

[Kernel-packages] [Bug 1569831] Re: Laptop does not resume after suspend (blackscreen).

Alex, thank you for reporting this and helping make Ubuntu better.

1) Could you please povide the full computer model as noted on the sticker of 
the computer itself?
2) Could you please provide the results of the following terminal commands:
lspci -vvnn | grep -A 9 Network
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date

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

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

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

Title:
  Laptop does not resume after suspend (blackscreen).

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  I have installed OS multiple times. I have to manually install the BCM
  driver. After installing the bcmwl-kernal-source the laptop will
  suspend, but not resume after. If I disable the external driver, the
  suspend resume works again. I have tried with a variety of different
  configs.

  Network card is BCM4352 [14e4-43b1](rev03)

  When I try to resume the laptop turns on, but screen never turns on. I've 
tried to the shortuts to turn the screen back on. 
  I'm using NVIDIA drivers, but even if I use the generic drivers the laptop 
will not resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 13 11:05:08 2016
  InstallationDate: Installed on 2016-03-05 (39 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse

Not Fix Committed as defined in https://wiki.ubuntu.com/Bugs/Status.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Tags added: cherry-pick

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

Title:
  BYD trackpad detected as PS/2 mouse

Status in linux package in Ubuntu:
  Triaged

Bug description:
  In 14.04.2, I expected to be able to use as touchpad with two finger
  vertical/horizontal scrolling. Currently only able to use plainly. The
  exact device is this:
  http://bydit.com/doce/products/microelectronics/2474.html

  I: Bus=0011 Vendor=0002 Product=0005 Version=
  N: Name="ImPS/2 Generic Wheel Mouse"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse0 event10
  B: PROP=0
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=103

  Output of xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ USB 2.0 Camera  id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  ---
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vjftw  1362 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=d58116d7-f5eb-4b3c-b986-a9a29b608880
  InstallationDate: Installed on 2015-04-25 (28 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp.
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 058f:3821 Alcor Micro Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation SharkBay Platform
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=cd943b28-f170-4ce9-b836-18c395f1df6d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: Fab2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/03/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SharkBay Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching

stinger, could you please advise to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/comments/8
?

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

Title:
  system freeze after vt switching

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  I'm trying to use the ctrl+alt+1 to switch to a terminal - ok,
  after switching back by  ctrl+alt+7 the system freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-3-generic 4.4.0-3.17
  ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1
  Uname: Linux 4.4.0-3-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stinger1644 F pulseaudio
  Date: Sun Feb  7 22:27:42 2016
  HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a
  InstallationDate: Installed on 2015-11-12 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112)
  Lsusb:
   Bus 002 Device 003: ID 24ae:2000  
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. P53E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic 
root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-3-generic N/A
   linux-backports-modules-4.4.0-3-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P53E.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: P53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1570754] Re: Graphics freeze after 6 - 48 hours, applications carry on working

Justas Azna, thank you for reporting this and helping make Ubuntu
better.

Please execute the following command only once, as it will automatically gather 
debugging information, in a terminal:
apport-collect 1570754

** Package changed: linux-lts-utopic (Ubuntu) => linux (Ubuntu)

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

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

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

Title:
  Graphics freeze after 6 - 48 hours, applications carry on working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We're testing Intel Compute Stick (http://www.cnet.com/products/intel-
  compute-stick/specs/) with Ubuntu 14.04 for our google chrome based
  digital signage solution. Unfortunately, the graphics freeze after a
  random period of time which I've noticed to be anything from 6 to 48
  hours.

  With the graphics frozen, the only thing I can do is move the mouse
  pointer and everything else is stuck. I've set up SSH server on it and
  after logging into the device I can see that all the applications are
  still running as expected.

  I doubt that it has anything to do with a faulty device as I was able
  to reproduce it on 7 different compute sticks.

  Kernel: 3.16.0-69-generic (but have also reproduced on
  3.16.0-45-generic and 3.16.0-70-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-69-generic 3.16.0-69.89~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-69.89~14.04.1-generic 3.16.7-ckt25
  Uname: Linux 3.16.0-69-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Apr 15 10:32:40 2016
  InstallationDate: Installed on 2016-03-23 (22 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" Linuxium - Beta Intel 
Z3735F (20150811)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1545401] Re: "kernel BUG at /build/linux-lts-wily-Vv6Eyd/linux-lts-wily-4.2.0/mm/memory.c:3146!"

Resolved as per original reporter in Xenial+.

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

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

Title:
  "kernel BUG at /build/linux-lts-wily-Vv6Eyd/linux-lts-
  wily-4.2.0/mm/memory.c:3146!"

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Incomplete
Status in linux-lts-wily source package in Wily:
  Invalid

Bug description:
  I was trying to attach gdb to chromium-browser, by passing the PID to
  gdb (gdb -p $PID). The first attempt as non-root user crashed gdb and
  I got this message:

  [ cut here ]
  kernel BUG at 
/build/linux-lts-wily-Vv6Eyd/linux-lts-wily-4.2.0/mm/memory.c:3146!
  invalid opcode:  [#1] SMP
  Modules linked in: vboxpci(OE) vboxnetadp(OE) r8168(OE) vboxnetflt(OE) 
vboxdrv(OE) ib_cm ib_sa ib_mad ib_core ib_addr libfc qla2xxx scsi_transport_fc 
configfs pci_stub drbg ansi_cprng ctr ccm dm_crypt ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables binfmt_misc uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media arc4 hp_wmi 
sparse_keymap rtsx_pci_ms memstick dm_multipath scsi_dh snd_hda_codec_idt ath9k 
snd_hda_codec_generic ath9k_common snd_hda_codec_hdmi joydev ath9k_hw 
input_leds snd_hda_intel serio_raw ath snd_hda_codec snd_hda_core snd_hwdep 
k10temp snd_pcm_oss mac80211 snd_mixer_oss snd_pcm snd_seq_midi i2c_piix4 
snd_seq_midi_event snd_rawmidi cfg80211 snd_seq snd_seq_device snd_timer snd 
soundcore shpchp parport_pc hp_accel lis3lv02d ppdev input_polldev mac_hid 
cpuid msr ircomm_tty ircomm irda crc_ccitt lp parport btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear pata_acpi rtsx_pci_sdmmc amdkfd amd_iommu_v2 radeon 
i2c_algo_bit ttm drm_kms_helper psmouse ahci drm pata_atiixp libahci rtsx_pci 
wmi video [last unloaded: vboxpci]
  CPU: 3 PID: 25702 Comm: gdb Tainted: G   OE   4.2.0-27-generic 
#32~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP Pavilion dv6 Notebook PC/3590, BIOS F.21 
09/13/2011
  task: 8800cb54d780 ti: 88000a8f task.ti: 88000a8f
  RIP: 0010:[]  [] 
handle_mm_fault+0x17e0/0x1840
  RSP: 0018:88000a8f3bb8  EFLAGS: 00010246
  RAX:  RBX:  RCX: 3000
  RDX: 8801697c04f8 RSI: 0120 RDI: 0001697c0067
  RBP: 88000a8f3c78 R08: 0001edddb120 R09: 0120
  R10: 0001 R11: 880004f8 R12: 88003265bc00
  R13: 880007a18808 R14: 7f856029fe68 R15: 8800aa3843c0
  FS:  7f3d95334740() GS:88020ed8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02b69528 CR3: 00012a9ad000 CR4: 06e0
  Stack:
   0016 8816 ea0005a5f030 817b0e73
   88003265bc00 7f856029fe68 0017 880004f8
   8800 0017 7f856029fe68 88003265bc00
  Call Trace:
   [] ? follow_page_pte+0xae/0x307
   [] ? follow_page_mask+0x1ce/0x320
   [] __get_user_pages+0xfb/0x5b0
   [] get_user_pages+0x52/0x60
   [] __access_remote_vm+0xb7/0x1c0
   [] access_process_vm+0x50/0x70
   [] ptrace_request+0x2c9/0x5a0
   [] ? queued_spin_lock_slowpath+0xb/0xf
   [] ? wait_task_inactive+0xea/0x1e0
   [] ? vfs_write+0x148/0x190
   [] arch_ptrace+0x261/0x2b0
   [] ? ptrace_check_attach+0x5f/0x140
   [] SyS_ptrace+0xa6/0x110
   [] entry_SYSCALL_64_fastpath+0x16/0x75
  Code: d8 50 a8 81 e8 92 0f ed ff 4c 8b 9d 78 ff ff ff e9 fa ee ff ff 48 8b 7d 
98 89 45 80 e8 2a dd fd ff 8b 45 80 89 c3 e9 ba eb ff ff <0f> 0b c7 45 80 01 00 
00 00 e9 a5 f7 ff ff 4c 89 c7 48 89 95 68
  RIP  [] handle_mm_fault+0x17e0/0x1840
   RSP 
  ---[ end trace c5ec208e5d4b9c66 ]---

  Then I tried running it as root (sudo gdb -p $PID). gdb got stuck at
  "Attaching to process ...". I tried killing gdb as root from another
  terminal, by running "killall gdb", but killall got stuck, too. pidof
  and ps also got stuck...

  This is the line referenced in the error message:  http://lxr.free-
  electrons.com/source/mm/memory.c?v=4.2#L3146 , I'm not sure if Ubuntu
  runs a modified version of this file, though. Also, I'm not sure if
  this affects Wily (I guess it does) or if this has been patched
  upstream.

  There is a similar bug report here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1296505 , but it doesn't
  involve gdb.

  Should I report this bug upstream?

  My system is:
  $ lsb_release -a
  LSB Version:

[Kernel-packages] [Bug 1545401] Re: "kernel BUG at /build/linux-lts-wily-Vv6Eyd/linux-lts-wily-4.2.0/mm/memory.c:3146!"

jose, could you please advise to
https://bugs.launchpad.net/ubuntu/+source/linux-lts-
wily/+bug/1545401/comments/21 ?

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

Title:
  "kernel BUG at /build/linux-lts-wily-Vv6Eyd/linux-lts-
  wily-4.2.0/mm/memory.c:3146!"

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Incomplete
Status in linux-lts-wily source package in Wily:
  Invalid

Bug description:
  I was trying to attach gdb to chromium-browser, by passing the PID to
  gdb (gdb -p $PID). The first attempt as non-root user crashed gdb and
  I got this message:

  [ cut here ]
  kernel BUG at 
/build/linux-lts-wily-Vv6Eyd/linux-lts-wily-4.2.0/mm/memory.c:3146!
  invalid opcode:  [#1] SMP
  Modules linked in: vboxpci(OE) vboxnetadp(OE) r8168(OE) vboxnetflt(OE) 
vboxdrv(OE) ib_cm ib_sa ib_mad ib_core ib_addr libfc qla2xxx scsi_transport_fc 
configfs pci_stub drbg ansi_cprng ctr ccm dm_crypt ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables binfmt_misc uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media arc4 hp_wmi 
sparse_keymap rtsx_pci_ms memstick dm_multipath scsi_dh snd_hda_codec_idt ath9k 
snd_hda_codec_generic ath9k_common snd_hda_codec_hdmi joydev ath9k_hw 
input_leds snd_hda_intel serio_raw ath snd_hda_codec snd_hda_core snd_hwdep 
k10temp snd_pcm_oss mac80211 snd_mixer_oss snd_pcm snd_seq_midi i2c_piix4 
snd_seq_midi_event snd_rawmidi cfg80211 snd_seq snd_seq_device snd_timer snd 
soundcore shpchp parport_pc hp_accel lis3lv02d ppdev input_polldev mac_hid 
cpuid msr ircomm_tty ircomm irda crc_ccitt lp parport btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear pata_acpi rtsx_pci_sdmmc amdkfd amd_iommu_v2 radeon 
i2c_algo_bit ttm drm_kms_helper psmouse ahci drm pata_atiixp libahci rtsx_pci 
wmi video [last unloaded: vboxpci]
  CPU: 3 PID: 25702 Comm: gdb Tainted: G   OE   4.2.0-27-generic 
#32~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP Pavilion dv6 Notebook PC/3590, BIOS F.21 
09/13/2011
  task: 8800cb54d780 ti: 88000a8f task.ti: 88000a8f
  RIP: 0010:[]  [] 
handle_mm_fault+0x17e0/0x1840
  RSP: 0018:88000a8f3bb8  EFLAGS: 00010246
  RAX:  RBX:  RCX: 3000
  RDX: 8801697c04f8 RSI: 0120 RDI: 0001697c0067
  RBP: 88000a8f3c78 R08: 0001edddb120 R09: 0120
  R10: 0001 R11: 880004f8 R12: 88003265bc00
  R13: 880007a18808 R14: 7f856029fe68 R15: 8800aa3843c0
  FS:  7f3d95334740() GS:88020ed8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02b69528 CR3: 00012a9ad000 CR4: 06e0
  Stack:
   0016 8816 ea0005a5f030 817b0e73
   88003265bc00 7f856029fe68 0017 880004f8
   8800 0017 7f856029fe68 88003265bc00
  Call Trace:
   [] ? follow_page_pte+0xae/0x307
   [] ? follow_page_mask+0x1ce/0x320
   [] __get_user_pages+0xfb/0x5b0
   [] get_user_pages+0x52/0x60
   [] __access_remote_vm+0xb7/0x1c0
   [] access_process_vm+0x50/0x70
   [] ptrace_request+0x2c9/0x5a0
   [] ? queued_spin_lock_slowpath+0xb/0xf
   [] ? wait_task_inactive+0xea/0x1e0
   [] ? vfs_write+0x148/0x190
   [] arch_ptrace+0x261/0x2b0
   [] ? ptrace_check_attach+0x5f/0x140
   [] SyS_ptrace+0xa6/0x110
   [] entry_SYSCALL_64_fastpath+0x16/0x75
  Code: d8 50 a8 81 e8 92 0f ed ff 4c 8b 9d 78 ff ff ff e9 fa ee ff ff 48 8b 7d 
98 89 45 80 e8 2a dd fd ff 8b 45 80 89 c3 e9 ba eb ff ff <0f> 0b c7 45 80 01 00 
00 00 e9 a5 f7 ff ff 4c 89 c7 48 89 95 68
  RIP  [] handle_mm_fault+0x17e0/0x1840
   RSP 
  ---[ end trace c5ec208e5d4b9c66 ]---

  Then I tried running it as root (sudo gdb -p $PID). gdb got stuck at
  "Attaching to process ...". I tried killing gdb as root from another
  terminal, by running "killall gdb", but killall got stuck, too. pidof
  and ps also got stuck...

  This is the line referenced in the error message:  http://lxr.free-
  electrons.com/source/mm/memory.c?v=4.2#L3146 , I'm not sure if Ubuntu
  runs a modified version of this file, though. Also, I'm not sure if
  this affects Wily (I guess it does) or if this has been patched
  upstream.

  There is a similar bug report here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1296505 , but it doesn't
  involve gdb.

  Should I report this bug upstream?

  My system is:
  $ lsb_release -a
  LSB Version:

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread milton hagler

Asus U44S laptop with Optimus Nvidia Geoforce GT 610M.

Slightly different but related issue. Can suspend with by closing the
lid which didn't work in 15.10, although only without an external
monitor plugged in. But upon resume getting a hardware lockup and freeze
nearly 100% of the time. Initially it worked, but then has since stopped
working. Using Nvidia binary driver 361.42 with the Intel card turned
off under software control.

Just noticed something odd though as writing this up. Additional Drivers
lists the Nvidia drivers OK, but for the Intel card it is now reporting
"Unknown: Unknown - This device is not working." After upgrading to
16.04 from 15.10 I double checked and it reported the Intel card turned
off from Additional Drivers. Clear, something has changed.

** Attachment added: "Additional Drivers"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+attachment/4645942/+files/Screenshot%20from%202016-04-25%2006-33-43.png

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

** Tags removed: kernel-bug-exists-upstream-4.4
** Tags added: kernel-bug-exists-upstream-4.6-rc3

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19

[Kernel-packages] [Bug 1550779] Re: [i915]] ERROR CPU pipe A FIFO underrun - Xorg glitches

** Tags added: needs-bisect

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)

marco, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  High load freezes ubuntu completely everytime (have to reboot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever an intensive application runs which consumes lots of memory
  or hard drive i/o, Ubuntu freezes completely. It is even impossible to
  kill the offending task. Only "solution" is then to wait for the
  application to finish, or restart PC.

  Windows doesn't have this issue as bad as Ubuntu, in that Windows is
  always somewhat responsive, and you can attempt to kill the intensive
  application to recover the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-32-generic 4.2.0-32.37
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-32-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/18210/fd/20: Input/output error
    USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cossio 2082 F pulseaudio
   /dev/snd/controlC1:  cossio 2082 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar  9 22:28:53 2016
  HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac
  InstallationDate: Installed on 2015-08-03 (219 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.505
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  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.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  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/1555351/+subscriptions

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

[Kernel-packages] [Bug 1549187] Re: dell_wmi: Unknown key e??? pressed

Gerald Quintana, could you please confirm the commit fixes your problem
following
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
?

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

Title:
  dell_wmi: Unknown key e??? pressed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Some special keys are not handled on Ubuntu 15.10 Wily and Dell  XPS
  15 9550

  Feb 24 10:10:14 XPS15-GQA kernel: [ 4280.734355] dell_wmi: Unknown key 153 
pressed
  Feb 24 10:10:16 XPS15-GQA kernel: [ 4282.893413] dell_wmi: Unknown key 152 
pressed
  Feb 24 10:10:30 XPS15-GQA kernel: [ 4296.263752] dell_wmi: Unknown key 151 
pressed

  - Fn+Esc -> key 151 -> Lock computer
  - Fn+F10 -> key 152 -> keyboard backlighting on/off 
  - Fn+Print Screen -> key 153 -> Wifi on/off
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gquintana   1746 F pulseaudio
   /dev/snd/controlC0:  gquintana   1746 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=2e069a2b-037f-4058-89b1-6e221da4046d
  InstallationDate: Installed on 2016-01-31 (23 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=3ecb2c05-ad6c-4d9d-9356-48c6991f0226 ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 11/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.07
  dmi.board.name: 0X2P13
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.07:bd11/02/2015:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 14.04-15.10 freezes totally

Jaime Pérez, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

** Summary changed:

- 8086:0f31 Ubuntu 14.04-15.10 freezes totally
+ 8086:0f31 Ubuntu 15.04-15.10 freezes totally

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

Title:
  8086:0f31 Ubuntu 15.04-15.10 freezes totally

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ever since I first installed 15.04 back in April/May on my new DELL
  Inspiron 3646 I have experienced frequent(daily/every-other-
  day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.).

  I have determined that the issue is related to the 'i915' driver in
  relation to my GPU.

  I'm currently using intel-linux-graphics-
  installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics
  with similar results (maybe a little better than the stock i915 stack
  in 15.04).

  WORKAROUND: Use kernel boot parameter:
  intel_idle.max_cstate=1

  I have gained _significant_ improvements in reliability / stability by
  using parameters in the i915 module:

  /etc/modprobe.d/i915.conf:
  options i915 semaphores=1

  and / or

  /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable"

  and / or
  /usr/share/X11/xorg.conf.d/20-intel.conf:

  Section "Device"
     Identifier "Intel Graphics"
     Driver "intel"
     Option "TearFree" "1"
  EndSection

  and / or
  Disable "Intel Virtualization Technologies" in the BIOS.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct  7 09:32:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:068d]
  InstallationDate: Installed on 2015-09-17 (19 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed 
to open file '/home/chris/.face': No such file or directory
  MachineType: Dell Inc. Inspiron 3646
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V6D8J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09:
  dmi.product.name: Inspiron 3646
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Oct  6 20:05:51 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 990
   vendor ACR
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

[Kernel-packages] [Bug 1568599] Re: Screen flickering with 16.04 on Dell XPS13 9350

Richard Platt, as per http://www.dell.com/support/home/us/en/19/product-
support/product/xps-13-9350-laptop/drivers?os=biosa an update to your
computer's buggy, insecure, and outdated BIOS is available (1.3.3). If
you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-1.3.3

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

Title:
  Screen flickering with 16.04 on Dell XPS13 9350

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 16.04 on my XPS13 9350 and I am experiencing
  and intermittent screen flickering. The screen goes black for a brief
  moment and constantly does this. While I have been typing it has done
  it 20-30  times.

  plattr@beatrice:~$ uname -a
  Linux beatrice 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  
  plattr@beatrice:~$ sudo dmidecode | grep -A3 '^System Information'
  [sudo] password for plattr: 
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 13 9350
Version: Not Specified

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  plattr 1194 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 10 21:07:48 2016
  HibernationDevice: RESUME=UUID=84cb2e32-5b42-44ab-be61-5906241daa1e
  InstallationDate: Installed on 2016-03-28 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  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 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=ddbb6ae6-9a35-4877-beba-6edd31e0ab97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

2016-04-24 Thread Colin Ian King

Is this being run as a normal user or with root privileges?

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1554613] Re: screen flickering on XPS13 9350

** Tags added: cherry-pick

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

Title:
  screen flickering on XPS13 9350

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

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1526537] Re: blk_update_request: I/O error

D. Charles Pyle / hakuna_matata, it will help immensely if you filed a new 
report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  blk_update_request: I/O error

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  On my laptop I am using the ubuntu in persistent mode with a backing files: 
casper-rw, home-rw. For some time in the new editions of ubuntu [ 15.04 / 15.10 
/ 16.04 daily (15.12) ] I meet with error: blk_update_request: I/O error, dev 
loop ... , sector ... .  am sure it is not a hardware problem. Please, could 
you try reproduce this issue 

  `/proc/cmdline`

  BOOT_IMAGE=/Ubuntu/16.04/desktop-amd64/casper/vmlinuz.efi append
  noprompt boot=casper intel_iommu=on toram showmounts persistent-
  path=/Ubuntu/16.04/desktop-amd64 persistent iso-
  scan/filename=/Ubuntu/16.04/xenial-desktop-amd64.iso cdrom-detect/try-
  usb=true

  `kern.log`

  Dec 15 21:49:25 ThinkPad kernel: [   11.507021] Bluetooth: BNEP socket layer 
initialized
  Dec 15 21:49:25 ThinkPad kernel: [   11.513208] blk_update_request: I/O 
error, dev loop0, sector 1376280
  Dec 15 21:49:25 ThinkPad kernel: [   11.544996] blk_update_request: I/O 
error, dev loop0, sector 1364008
  Dec 15 21:49:26 ThinkPad kernel: [   11.655626] IPv6: ADDRCONF(NETDEV_UP): 
wlp3s0: link is not ready
  Dec 15 21:49:26 ThinkPad kernel: [   11.656563] IPv6: ADDRCONF(NETDEV_UP): 
enp0s25: link is not ready
  Dec 15 21:49:26 ThinkPad kernel: [   11.884604] IPv6: ADDRCONF(NETDEV_UP): 
enp0s25: link is not ready
  Dec 15 21:49:26 ThinkPad kernel: [   12.080950] usbcore: registered new 
interface driver cdc_wdm
  Dec 15 21:49:26 ThinkPad kernel: [   12.089352] qmi_wwan 2-1.4:1.0: cdc-wdm0: 
USB WDM device
  Dec 15 21:49:26 ThinkPad kernel: [   12.089629] qmi_wwan 2-1.4:1.0 wwan0: 
register 'qmi_wwan' at usb-:00:1d.0-1.4, WWAN/QMI device, 86:f3:f1:57:ac:04
  Dec 15 21:49:26 ThinkPad kernel: [   12.089851] usbcore: registered new 
interface driver qmi_wwan
  Dec 15 21:49:27 ThinkPad kernel: [   13.014113] blk_update_request: I/O 
error, dev loop2, sector 776360
  Dec 15 21:49:27 ThinkPad kernel: [   13.026856] blk_update_request: I/O 
error, dev loop2, sector 92
  Dec 15 21:49:27 ThinkPad kernel: [   13.406901] e1000e: enp0s25 NIC Link is 
Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
  Dec 15 21:49:27 ThinkPad kernel: [   13.406909] e1000e :00:19.0 enp0s25: 
10/100 speed: disabling TSO
  Dec 15 21:49:27 ThinkPad kernel: [   13.406948] IPv6: 
ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
  Dec 15 21:49:27 ThinkPad kernel: [   13.411598] blk_update_request: I/O 
error, dev loop0, sector 1364024
  Dec 15 21:49:27 ThinkPad kernel: [   13.525480] blk_update_request: I/O 
error, dev loop2, sector 778064
  Dec 15 21:49:28 ThinkPad kernel: [   13.733896] Bluetooth: RFCOMM TTY layer 
initialized
  Dec 15 21:49:28 ThinkPad kernel: [   13.733906] Bluetooth: RFCOMM socket 
layer initialized
  Dec 15 21:49:28 ThinkPad kernel: [   13.733912] Bluetooth: RFCOMM ver 1.11
  Dec 15 21:49:28 ThinkPad kernel: [   13.758583] blk_update_request: I/O 
error, dev loop0, sector 1360048
  Dec 15 21:49:28 ThinkPad kernel: [   13.765377] blk_update_request: I/O 
error, dev loop0, sector 1364032
  Dec 15 21:49:28 ThinkPad kernel: [   13.778920] blk_update_request: I/O 
error, dev loop0, sector 1364040
  Dec 15 21:49:28 ThinkPad kernel: [   13.785037] blk_update_request: I/O 
error, dev loop0, sector 1364048
  Dec 15 21:49:28 ThinkPad gnome-session-binary[3083]: Entering running state
  Dec 15 21:49:37 ThinkPad kernel: [   22.759620] blk_update_request: 15 
callbacks suppressed
  Dec 15 21:49:37 ThinkPad kernel: [   22.759623] blk_update_request: I/O 
error, dev loop0, sector 1364072
  Dec 15 21:49:37 ThinkPad kernel: [   22.803618] hidraw: raw HID events driver 
(C) Jiri Kosina
  Dec 15 21:49:37 ThinkPad kernel: [   22.806751] Bluetooth: HIDP (Human 
Interface Emulation) ver 1.2
  Dec 15 21:49:37 ThinkPad kernel: [   22.806758] Bluetooth: HIDP socket layer 
initialized
  Dec 15 21:49:37 ThinkPad kernel: [   22.811095] hid-generic 
0005:0D62:01BF.0001: unknown main item tag 0x0
  Dec 15 21:49:37 ThinkPad kernel: [   22.811211] input: Bluetooth Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/0005:0D62:01BF.0001/input/input17
  Dec 15 21:49:37 ThinkPad kernel: [   22.811384] hid-generic 
0005:0D62:01BF.0001: input,hidraw0: BLUETOOTH HID v1.39 Mouse [ Bluetooth 
Mouse] on ec:55:f9:fa:c6:1d
  Dec 15 21:50:41 ThinkPad kernel: [   86.683594] blk_update_request: I/O 
error, dev loop2, sector 2343552
  Dec 15 21:50:41 ThinkPad kernel: [   86.690626] blk_update_request: I/O 
error, dev

[Kernel-packages] [Bug 1542716] Re: [Fujitsu LIFEBOOK S935] Touchpad doesn't work

mauribera, to confirm the previous results, could you please test
http://cdimage.ubuntu.com/daily-live/current/ (not your current install)
and advise if this is still reproducible?

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

Title:
  [Fujitsu LIFEBOOK S935] Touchpad doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  the touchpad is recognized, e.g., xinput but does not respond at all. It 
worked under the original win7 installaion
  thanks for your help

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb  6 21:36:22 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:1896]
  InstallationDate: Installed on 2016-01-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: FUJITSU LIFEBOOK S935
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic.efi.signed 
root=UUID=b2e8253b-e0f4-4300-b611-ab33856023ba ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.11
  dmi.board.name: FJNB284
  dmi.board.vendor: FUJITSU
  dmi.board.version: C3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: LIFEBOOK S935
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.11:bd06/02/2015:svnFUJITSU:pnLIFEBOOKS935:pvr1060173:rvnFUJITSU:rnFJNB284:rvrC3:cvnFUJITSU:ct10:cvrLIFEBOOKS935:
  dmi.product.name: LIFEBOOK S935
  dmi.product.version: 1060173
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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: Sat Feb  6 15:28:02 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5138 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3~trusty1

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

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

[Kernel-packages] [Bug 1540430] Re: Touchpad not working after suspend/resume

Uros Trojar, to clarify, on which of the attached dmesg files is this
problem reproducible with?

Also, please continue to test the latest mainline kernel (now 4.6-rc4)
to keep this report relevant to upstream.

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working after suspend/resume on Asus X302LA.

  I have tried both workarounds in bug  #1393079 to no success.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb  1 16:26:19 2016
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  uros   2656 F pulseaudio
   /dev/snd/controlC0:  uros   2656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
  InstallationDate: Installed on 2016-01-31 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X302LA
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-56-generic N/A
   linux-backports-modules-3.19.0-56-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  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.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1540430/+subscriptions

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

[Kernel-packages] [Bug 1413446] Re: [Dell XPS 13 9343] Audio broken with I2S mode

** Summary changed:

- [Dell XPS 13 9343] Audio broken with I2S mode in Ubuntu 14.10/15.04
+ [Dell XPS 13 9343] Audio broken with I2S mode

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

Title:
  [Dell XPS 13 9343] Audio broken with I2S mode

Status in Dell Sputnik:
  Invalid
Status in HWE Next:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in linux package in Fedora:
  Unknown

Bug description:
  Please read this first before considering making a comment:
  The root cause of the scope of this bug report was caused by a BIOS error in 
BIOS A01 that put the sound in an undefined mode that wasn't really I2S and 
wasn't really HDA. This has been fixed by BIOS A02 ( or later ).

  There was an _REV patch that was proposed but not merged upstream. If
  that (or something similar to it) does get merged upstream, then with
  BIOS A02+ the audio will operate in I2S mode.

  If you have a problem with your computer, please do not make comments
  here, as this bug report is considered closed. Instead file a new
  report following https://wiki.ubuntu.com/ReportingBugs . Your issue
  will not be dealt with by making comments in this report, and will
  likely be completely ignored.

  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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:2051 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

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

[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown

2016-04-24 Thread Moppers

Admittedly this was on Parallels (a VM host for Mac) but I noticed this
problem only occurs for me when the grub menu is allowed to time out. If
I manually select an OS, I can enter the encyption passphrase.

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1542944] Re: QCA9565 / AR9565 bluetooth not work

2016-04-24 Thread damien

For me, the wifi and the bluetooth work at the same time...

My laptop is connected in wifi and I can listen a webradio to my
bluetooth hifi receiver.

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

Title:
  QCA9565 / AR9565 bluetooth not work

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-lts-wily package in Ubuntu:
  Fix Committed

Bug description:
  usb-devices | awk '/e095/' RS=
  T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0489 ProdID=e095 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  7 23:09:38 2016
  InstallationDate: Installed on 2016-01-12 (26 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown

2016-04-24 Thread Peter Matulis

Upgraded Lubuntu 15.10 and there is no way to enter the passphrase. I
was somehow able to get to a console where I found a prompt to enter
one. On a next reboot I could not find this 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/1359689

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1542944] Re: QCA9565 / AR9565 bluetooth not work

2016-04-24 Thread Djalal

Thanks Pilot6 for solving this.

After fixing bluetooth, I suffered from the so-called bluetooth coexistence 
issue. That is wifi stopped working whenever bluetooth was in use. Does this 
affects you as well damien? The solution is mentioned here:
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex

In my case, I had to
sudo modprobe -r ath9k
sudo modprobe ath9k btcoex_enable=1

This is essentially a bug too unless done automatically by the system.
Can it be fixed through here or should I report it somewhere else?

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

Title:
  QCA9565 / AR9565 bluetooth not work

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-lts-wily package in Ubuntu:
  Fix Committed

Bug description:
  usb-devices | awk '/e095/' RS=
  T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0489 ProdID=e095 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  7 23:09:38 2016
  InstallationDate: Installed on 2016-01-12 (26 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1572347] Re: problems with network speed reporting in sysfs on s390

2016-04-24 Thread Dimitri John Ledkov

For LPAR -> it's a valid test to verity max speed and actual speeds
For z/VM -> the cards are virtualised on the host, thus any test of max & 
actual speeds is bogus
For z/KVM -> the cards are virtualised on the host, thus any test of max & 
actual speeds is bogus
Comparing z/VM and z/KVM with other architectures is also bogus, as completely 
different kernel drivers are used to implement the cards (qeth driver on a CCW 
bus and CCW-virtio bus, CCW buses are entirely s390x specific)

At best this is a wishlist bug report against upstream z/VM & upstream
qemu to expose something more realistic in the guest, which kernel then
can pick up and display. What kernel is showing to you, is as much as it
knows, and there is no bug there as far as I can tell.

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread Derek

Same issue here. Ubuntu Gnome 16.04, Lenovo y40. 
Running on kernel 4.2.0 or disabling my discrete gpu (AMD) fixes it.

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1573817] Re: linux: 4.4.0-22.38 -proposed tracker

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

Title:
  linux: 4.4.0-22.38 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-22.38 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 --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1573817/+subscriptions

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

[Kernel-packages] [Bug 1484159] Re: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] is not supported

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

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

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

Title:
  Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042]
  is not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This card remains unsupported out-of-the-box by the ath10k_pci kernel
  module. At this point, it looks like kvalo's ath10k-firmware repo just
  needs to be pulled in.

  ---

  HOW TO GET THIS CARD TO WORK:

  I don't actually have this card, but AndyP was able to get this card
  to work by following my instructions, so I've written them here in a
  clearer format.

  1) Support for this card is not present in kernel 4.2.  However, it
  was added at some point between then and kernel 4.4.  See
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel.  Kernel 4.5 is suggested.

  2) Get the latest firmware from https://github.com/kvalo/ath10k-
  firmware/archive/master.zip

  3) Unzip this file, and copy the contents of ath10k-firmware-master to
  /lib/firmware/ath10k.

  4) Run the following commands to rename the necessary firmware file:
  cd /lib/firmware/ath10k/QCA9377/hw1.0/
  sudo mv firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin

  5) Reboot your computer. Run "lshw -C network" to see if your card is
  recognized.

  Please tell me if these instructions are working for you.

  The original bug description follows.
  ---

  Hi,
  Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux 
kernal. Please add support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
   /dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 12 20:31:24 2015
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_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.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1484159/+subscriptions

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

[Kernel-packages] [Bug 1542944] Re: QCA9565 / AR9565 bluetooth not work

2016-04-24 Thread damien

Ok.

I have installed manually 4.2.0-36 and blutooth work fine.

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

Title:
  QCA9565 / AR9565 bluetooth not work

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-lts-wily package in Ubuntu:
  Fix Committed

Bug description:
  usb-devices | awk '/e095/' RS=
  T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0489 ProdID=e095 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  7 23:09:38 2016
  InstallationDate: Installed on 2016-01-12 (26 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

Title:
  package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to
  install/upgrade: package linux-image-3.13.0-27-generic is not ready
  for configuration  cannot configure (current status `half-installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Windows 10 on dual boot and then trying to fix all the
  problems that caused.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  2354 F pulseaudio
  Date: Sun Apr 24 14:39:36 2016
  DuplicateSignature: 
package:linux-image-3.13.0-27-generic:3.13.0-27.50:package 
linux-image-3.13.0-27-generic is not ready for configuration  cannot configure 
(current status `half-installed')
  ErrorMessage: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8d2d661c-dd61-4bd2-848a-7406735fc72b
  InstallationDate: Installed on 2013-01-18 (1191 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Sony Corporation SVS15123CXB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=e3363326-bb4a-4e44-8e50-cbc4cb26d252 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 N/A
  SourcePackage: linux
  Title: package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to 
install/upgrade: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (706 days ago)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS15123CXB:pvrC60BCUA5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS15123CXB
  dmi.product.version: C60BCUA5
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread Felipe

Same here, Ubuntu 16.04, Dell N4110. I tried with a fresh install too

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1574388] Re: package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to install/upgrade: package linux-image-3.13.0-27-generic is not ready for configuration cannot configure

2016-04-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to
  install/upgrade: package linux-image-3.13.0-27-generic is not ready
  for configuration  cannot configure (current status `half-installed')

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading Windows 10 on dual boot and then trying to fix all the
  problems that caused.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  2354 F pulseaudio
  Date: Sun Apr 24 14:39:36 2016
  DuplicateSignature: 
package:linux-image-3.13.0-27-generic:3.13.0-27.50:package 
linux-image-3.13.0-27-generic is not ready for configuration  cannot configure 
(current status `half-installed')
  ErrorMessage: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8d2d661c-dd61-4bd2-848a-7406735fc72b
  InstallationDate: Installed on 2013-01-18 (1191 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Sony Corporation SVS15123CXB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=e3363326-bb4a-4e44-8e50-cbc4cb26d252 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 N/A
  SourcePackage: linux
  Title: package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to 
install/upgrade: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (706 days ago)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS15123CXB:pvrC60BCUA5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS15123CXB
  dmi.product.version: C60BCUA5
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1573817] Re: linux: 4.4.0-22.38 -proposed tracker

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Description changed:

  This bug is for tracking the 4.4.0-22.38 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
  
- kernel-phase:Packaging
- kernel-phase-changed:Friday, 22. April 2016 22:01 UTC
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase-changed:Sunday, 24. April 2016 21:00 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-22.38 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 --
- phase: Packaging
- kernel-phase-changed:Sunday, 24. April 2016 21:00 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.4.0-22.38 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-22.38 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 --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1573817/+subscriptions

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

[Kernel-packages] [Bug 1574388] [NEW] package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to install/upgrade: package linux-image-3.13.0-27-generic is not ready for configuration cannot configur

2016-04-24 Thread Steve Turpin

Public bug reported:

After upgrading Windows 10 on dual boot and then trying to fix all the
problems that caused.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  steve  2354 F pulseaudio
Date: Sun Apr 24 14:39:36 2016
DuplicateSignature: package:linux-image-3.13.0-27-generic:3.13.0-27.50:package 
linux-image-3.13.0-27-generic is not ready for configuration  cannot configure 
(current status `half-installed')
ErrorMessage: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
HibernationDevice: RESUME=UUID=8d2d661c-dd61-4bd2-848a-7406735fc72b
InstallationDate: Installed on 2013-01-18 (1191 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation SVS15123CXB
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=e3363326-bb4a-4e44-8e50-cbc4cb26d252 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 N/A
SourcePackage: linux
Title: package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to 
install/upgrade: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
UpgradeStatus: Upgraded to trusty on 2014-05-19 (706 days ago)
dmi.bios.date: 03/13/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1021C8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS15123CXB:pvrC60BCUA5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVS15123CXB
dmi.product.version: C60BCUA5
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to
  install/upgrade: package linux-image-3.13.0-27-generic is not ready
  for configuration  cannot configure (current status `half-installed')

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading Windows 10 on dual boot and then trying to fix all the
  problems that caused.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  2354 F pulseaudio
  Date: Sun Apr 24 14:39:36 2016
  DuplicateSignature: 
package:linux-image-3.13.0-27-generic:3.13.0-27.50:package 
linux-image-3.13.0-27-generic is not ready for configuration  cannot configure 
(current status `half-installed')
  ErrorMessage: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=8d2d661c-dd61-4bd2-848a-7406735fc72b
  InstallationDate: Installed on 2013-01-18 (1191 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Sony Corporation SVS15123CXB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=e3363326-bb4a-4e44-8e50-cbc4cb26d252 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 N/A
  SourcePackage: linux
  Title: package linux-image-3.13.0-27-generic 3.13.0-27.50 failed to 
install/upgrade: package linux-image-3.13.0-27-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (706 days ago)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias:

[Kernel-packages] [Bug 1574362] Re: autoreconstruct: need to also generate extend-diff-ignore options for links

2016-04-24 Thread Kamal Mostafa

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

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

Title:
  autoreconstruct: need to also generate extend-diff-ignore options for
  links

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  When autoreconstruct detects links and adds them to the reconstruction
  list, it also needs to add them to the debian/source/options list as
  extend-diff-ignore options.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1574382

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

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

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

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

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

Title:
  Default sound device changes after resuming system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 and 15.10, too
  After resuming from sleep, the default sound device is set to another one, I 
have to go in the sound settings and click on the primary one to get back. Did 
not see this bug after rebooting or power on.

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

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

[Kernel-packages] [Bug 1574382] [NEW] Default sound device changes after resuming system

2016-04-24 Thread Vanyolai Krisztián

Public bug reported:

Ubuntu 16.04 and 15.10, too
After resuming from sleep, the default sound device is set to another one, I 
have to go in the sound settings and click on the primary one to get back. Did 
not see this bug after rebooting or power on.

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

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

Title:
  Default sound device changes after resuming system

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 and 15.10, too
  After resuming from sleep, the default sound device is set to another one, I 
have to go in the sound settings and click on the primary one to get back. Did 
not see this bug after rebooting or power on.

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

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

[Kernel-packages] [Bug 1574161] Re: Ubuntu 16.04 LTS Release Suspend on lid close

2016-04-24 Thread SimonKberg

Same issue on my HP Pavillion 15 running Ubuntu Gnome 16.04

The lid state is correctly reported in /proc/acpi/button/lid/LID0/state

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

Title:
  Ubuntu 16.04 LTS Release Suspend on lid close

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend when inactive for works as it should, the suspend under the
  main menu works, suspend on lid closes does not suspend right away but
  waits for the time period under suspend when inactive for. This causes
  the laptop to run hotter. My current work around has been using the
  main menu suspend before closing the lid. Also when I close the lid
  without suspending the computer it doesn't turn off the screen and
  lock it, which is a security.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gary   1555 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:36:59 2016
  HibernationDevice: RESUME=UUID=48d1c5c7-5c73-45ae-8f8f-ad02cc750f07
  InstallationDate: Installed on 2016-04-22 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=af29906f-05db-42a4-a830-a8a240491df5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1671
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.4C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06911220461620100:rvnHewlett-Packard:rn1671:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.version: 06911220461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc

2016-04-24 Thread clapsus

Same here, Dell Inspiron 3537. AMD Radeon.
Ubuntu GNOME 16.04 clean install with kernel 4.4.0-21-generic. 
Suspend worked on Ubuntu vanilla 14.04.

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

Title:
  Suspension does not work, freezes the pc

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

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN

[Kernel-packages] [Bug 1329510] Re: [Asus X200M] Changing Backlight not working

2016-04-24 Thread Nizar Kerkeni

All is working fine after the workaround to get special keys working
described above (#32) combined to the workaround to set backlight with
xbacklight in the bug description.

** Description changed:

  Backlight setting is not working with Lubuntu 14.04.
  
  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.
  
  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :
  
  Section "Device"
- Identifier "card0"
- Driver "intel"
- Option "Backlight" "intel_backlight"
- BusID "PCI:0:2:0"
+ Identifier "card0"
+ Driver "intel"
+ Option "Backlight" "intel_backlight"
+ BusID "PCI:0:2:0"
  EndSection
  
  but special keys are not working, and there are no events in acpi_listen
  when pressing these keys.
+ 
+ Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
+ In the file /etc/default/grub, you'll see a line that looks like this:
+ 
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
+ 
+ All you want to do is add two parameters to that line to make it look
+ like this:
+ 
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="
+ 
+ That's it. Save the file and run sudo update-grub in a terminal. Reboot,
+ and your brightness keys should start working perfectly.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  Update : To get special keys working (from : 
http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop)
  In the file /etc/default/grub, you'll see a line that looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  All you want to do is add two parameters to that line to make it look
  like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="

  That's it. Save the file and run sudo update-grub in a terminal.
  Reboot, and your brightness keys should start working perfectly.

  
  ProblemType: Bug

[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2016-04-24 Thread Alexey Pivovarsky

I confirm that this bug is still present on 9343 with 16.04 LTS.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Kernel-packages] [Bug 1329510] Re: [Asus X200M] Changing Backlight not working

2016-04-24 Thread Nizar Kerkeni

I confirm this bug for xubuntu 16.04 LTS
A workaround to get F5/F6 working is described here : 
 http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop
The notification is about change is displayed but the back-light is not 
changing.

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

Title:
  [Asus X200M] Changing Backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight setting is not working with Lubuntu 14.04.

  This bug is reported following
  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report
  guidelines.

  WORKAROUND: Backlight can be set with xbacklight after creating
  /usr/share/X11/xorg.conf.d/20-intel.conf :

  Section "Device"
  Identifier "card0"
  Driver "intel"
  Option "Backlight" "intel_backlight"
  BusID "PCI:0:2:0"
  EndSection

  but special keys are not working, and there are no events in
  acpi_listen when pressing these keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume   1447 F lxpanel
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
  CurrentDesktop: LXDE
  Date: Thu Jun 12 21:52:16 2014
  HibernationDevice: RESUME=UUID=5b0a59aa-0acf-415f-93bd-62df1b558efb
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
   Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=37551324-2550-4e13-aea9-4603fbd63807 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  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/1329510/+subscriptions

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

[Kernel-packages] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor

2016-04-24 Thread groucho

** Bug watch removed: freedesktop.org Bugzilla #93892
   https://bugs.freedesktop.org/show_bug.cgi?id=93892

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

Title:
  multi monitors - black flashes or black screen when the mouse cursor
  leaves a monitor

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When the mouse cursor leaves one of the screens, there is either :
  - no problem
  - the screen becomes black just below the position of the cursor and 
instantly comes back to normal.
  - the screen becomes entirely black with some random colored pixels 
flickering on the far left of the screen. I have to move the cursor to the 
black screen, otherwise it stays black.

  It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta.
  I have tested with other distributions (Debian Jessie and Fedora) and 
everything is fine.

  Hardware : Intel Ironlake (Thinkpad X201) with an external monitor
  plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar  5 13:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  MachineType: LENOVO 3680KD3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3680KD3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680KD3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sat Mar  5 13:03:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2202 
   vendor BOE
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread AM

Same here, desktop computer, Ubuntu Gnome 16.04. It doesn't do that all
the time, but i would say 50/50 chance.

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown

2016-04-24 Thread Frédéric

I confirm the problem since I upgraded to Lubuntu 16.04.

Does anyone have a solution to remove cryptsetup without reinstall all
the system ?

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread arn

Exactly the same issue, MSI GX680.

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc

2016-04-24 Thread Benny

Same issue on Dell Latitude 3650, i7, 16GB RAM, AMD Radeon. 
Ubuntu 16.04 Fresh install with kernel 4.4.0-21-generic. Suspend worked well on 
14.04.

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

Title:
  Suspension does not work, freezes the pc

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

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread Kenny Durkin

Same exact issue, Lenovo U400

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

2016-04-24 Thread TJ

In reply to Simon Fels (sorry for the long delay - I put the keyboards
aside to focus on other things).

The "Apple Wireless Keyboard" are model A1016 105-key, including a
numeric keypad.

Issue still affects 16.04.

>From 16.04 attaching a bluetoothd debug log whilst trying to pair with
the A1016. It reflects using

tj@T300CHI:~$ bluetoothctl
[NEW] Controller 34:02:86:FC:AD:59 T300CHI [default]
[NEW] Device 00:0A:95:44:37:11 Apple Wireless Keyboard
[NEW] Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 34:02:86:FC:AD:59 Discovering: yes
[NEW] Device 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj
[CHG] Device 00:0A:95:44:37:11 LegacyPairing: yes
[CHG] Device 00:0A:95:44:37:11 RSSI: -43
[bluetooth]# pair 00:0A:95:44:37:11
Attempting to pair with 00:0A:95:44:37:11
[agent] PIN code: 412054
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[CHG] Device 00:1F:3A:E0:0A:AF RSSI: -66

Notice that the "[agent] PIN code: 412054" message doesn't appear until
I press the A1016 keyboard's Enter key once. I then type the prompted
PIN followed by Enter on the A1016 keyboard.

Sometimes I get three prompts to enter PIN codes (each PIN different)
before it fails.

** Attachment added: "bluetoothd debug log trying to pair A1016"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+attachment/4645819/+files/bluetoothd-debug-A1016-pair-attempt.log

** Summary changed:

- [Regresision] 15:10 - Cannot pair with devices using PIN codes
+ [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN 
codes

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

Title:
  [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy)
  PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

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

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

[Kernel-packages] [Bug 1574362] [NEW] autoreconstruct: need to also generate extend-diff-ignore options for links

2016-04-24 Thread Andy Whitcroft

Public bug reported:

When autoreconstruct detects links and adds them to the reconstruction
list, it also needs to add them to the debian/source/options list as
extend-diff-ignore options.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  autoreconstruct: need to also generate extend-diff-ignore options for
  links

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When autoreconstruct detects links and adds them to the reconstruction
  list, it also needs to add them to the debian/source/options list as
  extend-diff-ignore options.

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

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

Re: [Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

2016-04-24 Thread Patrick Lacasse

I upgraded to Ubuntu 16.04 LTS (4.4.0-21-generic) and my wifi now works out
of the box.
I was using a usb-wifi since I bought my Lenovo Yoga 3 and I'm very happy
because the builtin wifi card is much better.

This bug is solved for me!

However, I can't tell if the firmware I copied last month are used or
not.


2016-04-22 19:14 GMT-04:00 Miles Krell :

> ** Description changed:
>
> - This card remains unsupported out-of-the-box by the ath10k_pci kernel
> - module.  At this point, it looks like kvalo's ath10k-firmware repo just
> - needs to be pulled in.
> + The firmware for this card isn't included with Ubuntu.  The firmware
> + provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
> + used with this card.  This included firmware is likely for the QCA6174
> + instead of this card, the QCA6164.
> +
> + Yes, you read that right: the files for the QCA6164 need to be a folder
> + called QCA6174 in order for the card to work.  Running "modprobe
> + ath10k_pci" shows that the ath10k_pci module looks for firmware in a
> + folder called QCA6174, but not in any folder called QCA6164.
> +
> + It seems that before this issue can be resolved, the ath10k_pci module
> + must be changed so that it recognizes firmware for both the QCA6164 and
> + QCA6174, in separate folders.
>
>
> ---
>
>   HOW TO GET THIS CARD TO WORK:
>
> - As of February 26, 2016, this has become rather simple.
> + 1) Use a kernel that supports this card
>
> - According to the Linux Wireless wiki, support was added in kernel 4.2
> - Your kernel is probably fine, but if it's older than 4.2, see
> + According to WikiDevi, support for this card was added in kernel 4.3.
> + If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip
> + to the next step.  If you're running Ubuntu 15.10 or below, see
>   https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
> - newer one.
> + newer kernel.  Alternatively, you can use backports.  This is a lot more
> + work, but if you really need to keep using an older kernel for some
> + reason, there are some guides to installing backports in the comments
> + below.
>
> - 1) Get the latest firmware from https://github.com/kvalo/ath10k-
> - firmware/archive/master.zip
> + 2) Get rid of the firmware folder for this card that's included with
> + Ubuntu:
>
> - 2) Unzip this file, and copy the contents of ath10k-firmware-master to
> - /lib/firmware/ath10k.
> + sudo rm -r /lib/firmware/ath10k/QCA6174/
>
> - 3) Rename two of the firmware files like so:
> - cd /lib/firmware/QCA6174/hw2.1
> + 3) Download the latest firmware:
> +
> + wget https://github.com/kvalo/ath10k-firmware/archive/master.zip
> +
> + 4) Unzip the downloaded file.  Inside the ath10k-firmware-master folder
> + is a folder named QCA6174.  Copy the QCA6174 folder to
> + /lib/firmware/ath10k:
> +
> + unzip master.zip
> + sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/
> +
> + 5) Rename two of the firmware files like so:
> +
> + cd /lib/firmware/ath10k/QCA6174/hw2.1/
>   sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
> - cd /lib/firmware/QCA6174/hw3.0
> + cd /lib/firmware/ath10k/QCA6174/hw3.0/
>   sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin
>
> - 4) Reboot your computer.  Run "lshw -C network" to see if your card is
> - recognized.
> + 6) Reboot your computer.  Run "lshw -C network" to see if your card is
> + recognized.  You can delete the files you downloaded earlier:
>
> - If you created a "/lib/modprobe.d/ath10k.conf" file earlier to disable
> - otp, you can remove it.  I did, and the card still works fine.
> + cd ~
> + rm master.zip
> + rm -r ath10k-firmware-master/
>
> - Last updated Match 26, 2016
> + Verified to work on Ubuntu 16.04 LTS (with kernel 4.4.0-21-generic)
> +
> + Last updated April 22, 2016
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1436940
>
> Title:
>   Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
>   is not supported
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux-firmware package in Ubuntu:
>   Confirmed
> Status in linux source package in Vivid:
>   Confirmed
> Status in linux source package in Wily:
>   Confirmed
>
> Bug description:
>   The firmware for this card isn't included with Ubuntu.  The firmware
>   provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
>   used with this card.  This included firmware is likely for the QCA6174
>   instead of this card, the QCA6164.
>
>   Yes, you read that right: the files for the QCA6164 need to be a
>   folder called QCA6174 in order for the card to work.  Running
>   "modprobe ath10k_pci" shows that the ath10k_pci module looks for
>   firmware in a folder called QCA6174, but not in any folder called

[Kernel-packages] [Bug 1568599] Re: Screen flickering with 16.04 on Dell XPS13 9350

2016-04-24 Thread Richard Platt

flickering has started again after apt-get update/upgrade . kernel
4.4.0.21

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

Title:
  Screen flickering with 16.04 on Dell XPS13 9350

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 16.04 on my XPS13 9350 and I am experiencing
  and intermittent screen flickering. The screen goes black for a brief
  moment and constantly does this. While I have been typing it has done
  it 20-30  times.

  plattr@beatrice:~$ uname -a
  Linux beatrice 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  
  plattr@beatrice:~$ sudo dmidecode | grep -A3 '^System Information'
  [sudo] password for plattr: 
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 13 9350
Version: Not Specified

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  plattr 1194 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 10 21:07:48 2016
  HibernationDevice: RESUME=UUID=84cb2e32-5b42-44ab-be61-5906241daa1e
  InstallationDate: Installed on 2016-03-28 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  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 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=ddbb6ae6-9a35-4877-beba-6edd31e0ab97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread clapsus

Here's the log after trying to run "pm-suspend" on Inspiron 3537.
FYI, nothing happens when i try to run this command. The problem only occurs if 
i try the suspend other way (from the top right corner menu, or when closing 
the lid).

** Attachment added: "pm-suspend log on a Dell Inspiron 3537"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+attachment/4645763/+files/pm-suspend_inspiron_3537.log

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread clapsus

Same here, Dell Inspiron 3537.

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument

2016-04-24 Thread Ales Kvapil

4.4.0-21-generic still not fixed. Should I wait until next Kernel
update? Or still a bug

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

Title:
  [regression]: Failed to call clock_adjtime(): Invalid argument

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

Bug description:
  Steps to reproduce:

  1) Force a time delta
  date -s "now - 1 hour"
  2) Restart systemd-timesyncd to have it fix the time
  systemctl restart systemd-timesyncd

  Expected behavior:

  The clock should be back in sync.

  Actual (problematic) behavior:

  The clock stays out of sync because the call to clock_adjtime()
  failed.

  # systemctl status systemd-timesyncd.service 
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: active (running) since Tue 2016-04-05 14:26:25 EDT; 1s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 11567 (systemd-timesyn)
 Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 512)
 Memory: 260.0K
CPU: 15ms
 CGroup: /system.slice/systemd-timesyncd.service
 └─11567 /lib/systemd/systemd-timesyncd

  Apr 05 14:26:25 simon-laptop systemd[1]: Starting Network Time 
Synchronization...
  Apr 05 14:26:25 simon-laptop systemd[1]: Started Network Time Synchronization.
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Failed to call 
clock_adjtime(): Invalid argument
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Synchronized to time 
server 172.24.21.1:123 (ntp.ubuntu.com).

  
  This problem doesn't happen when running kernel 4.4.0-16.32. Looking at the 
changelog of 4.4.0-17.33 it could be because of the new feature introduced in 
LP: #1519625.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-17-generic 4.4.0-17.33
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  5198 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Apr  5 14:21:22 2016
  HibernationDevice: RESUME=/dev/mapper/crypt-swap
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic 
root=/dev/mapper/crypt-xroot ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 
nmi_watchdog=0 kaslr quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 
nmi_watchdog=0 kaslr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-17-generic N/A
   linux-backports-modules-4.4.0-17-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1568211] Re: no UMS support in radeon module

2016-04-24 Thread broadcast23

I have an A8 3820 AMD cpu (HD 6550 graphics) I have the same problem.
First I want to say that I have been booting a usb hdd since 16.04
alpha. when I booted kernal 4.4.0-10 no problem, but I then booted to
4.4.0-12 that's when the problem started. Then I waited for the release
of 16.04, there was no change. I just booted the live dvd using nomodset
option and the screen showed an error "no ums support on radeon module."
I don't have any other driver installed except what's in the 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/1568211

Title:
  no UMS support in radeon module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded overnight from Wily to Xenial. The system will not boot.
  Only a blank screen after grub loads the kernel.

  The recovery kernel loads fine and I was able to find the following
  messages:

  [drm] VGACON disable radeon kernel modesetting
  [drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

  The recovery kernel command line had a nomodeset parameter that was
  not in the main kernel command line.

  Adding the nomodeset parameter the main kernel command line finally
  booted the system. It's kind of ugly but it seems to work.

  Note: For what it's worth I reported a similar issue against several
  Utopic kernels (bug #1407505). There was a back and forth with
  jsalisbury until a kernel finally worked. I have had no problems until
  today.

  Hope that helps.

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

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

[Kernel-packages] [Bug 1064490] Re: USB Gaming Mouse 04d9:a078 not working

2016-04-24 Thread Edson Oliveira

I´m buy a mouse of this type and do not work.
I know much choises and functions but i don´t know how solve-it.

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

Title:
  USB Gaming Mouse 04d9:a078 not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  USB Gaming Mouse 04d9:a078 is not working.
  dmesg says:

  kernel: [2.988282] usb 4-2: new full-speed USB device number 3 using 
ohci_hcd
  kernel: [3.163892] usb 4-2: New USB device found, idVendor=04d9, 
idProduct=a04a
  kernel: [3.163899] usb 4-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  kernel: [3.163904] usb 4-2: Product: USB Gaming Mouse
  kernel: [3.163908] usb 4-2: Manufacturer: Newman
  kernel: [3.173664] input: Newman USB Gaming Mouse as 
/devices/pci:00/:00:12.0/usb4/4-2/4-2:1.0/input/input4
  kernel: [3.173744] hid-generic 0003:04D9:A04A.0003: input,hidraw2: USB 
HID v1.10 Keyboard [Newman USB Gaming Mouse] on usb-:00:12.0-2/input0
  kernel: [3.181187] hid-generic 0003:04D9:A04A.0004: usage index exceeded
  kernel: [3.181189] hid-generic 0003:04D9:A04A.0004: item 0 2 2 2 parsing 
failed
  kernel: [3.181199] hid-generic: probe of 0003:04D9:A04A.0004 failed with 
error -22

  
  workaroud:

  In /usr/src/linux/include/linux/hid.h
  change the value of the constant in line 344

  #define HID_MAX_USAGES12288

  from 12288 to a value greater than 32k,
  recompile and install the new kernel.

  Solution found on site: 
  
http://forums.opensuse.org/english/get-technical-help-here/hardware/473200-usb-gaming-mouse-04d9-a078-not-working-linux-plus-workaround.html

  
  # lsb_release -rd
  Description:Ubuntu quantal (development branch)
  Release:12.10

  # apt-cache policy linux-image-extra-3.5.0-17-generic
  linux-image-extra-3.5.0-17-generic:
Zainstalowana: 3.5.0-17.27
Kandydująca:   3.5.0-17.27
Tabela wersji:
   *** 3.5.0-17.27 0
  500 http://pl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarzabek   2309 F pulseaudio
   /dev/snd/controlC0:  jarzabek   2309 F pulseaudio
   /dev/snd/pcmC0D0p:   jarzabek   2309 F...m pulseaudio
  CRDA: Error: [Errno 2] Nie ma takiego pliku ani katalogu
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=44032fe5-8c62-4706-adf6-036103183a07
  IwConfig:
   tun0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=b395cc47-d2bd-4d63-856b-ce6c5d291d3e ro splash quiet
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-16-generic N/A
   linux-backports-modules-3.5.0-16-generic  N/A
   linux-firmware1.94
  RfKill:
   
  Tags:  quantal
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-27 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/20/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1064490] Re: USB Gaming Mouse 04d9:a078 not working

2016-04-24 Thread Edson Oliveira

lsusb :
Bus 002 Device 007: ID 04d9:a077 Holtek Semiconductor, Inc.

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

Title:
  USB Gaming Mouse 04d9:a078 not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  USB Gaming Mouse 04d9:a078 is not working.
  dmesg says:

  kernel: [2.988282] usb 4-2: new full-speed USB device number 3 using 
ohci_hcd
  kernel: [3.163892] usb 4-2: New USB device found, idVendor=04d9, 
idProduct=a04a
  kernel: [3.163899] usb 4-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  kernel: [3.163904] usb 4-2: Product: USB Gaming Mouse
  kernel: [3.163908] usb 4-2: Manufacturer: Newman
  kernel: [3.173664] input: Newman USB Gaming Mouse as 
/devices/pci:00/:00:12.0/usb4/4-2/4-2:1.0/input/input4
  kernel: [3.173744] hid-generic 0003:04D9:A04A.0003: input,hidraw2: USB 
HID v1.10 Keyboard [Newman USB Gaming Mouse] on usb-:00:12.0-2/input0
  kernel: [3.181187] hid-generic 0003:04D9:A04A.0004: usage index exceeded
  kernel: [3.181189] hid-generic 0003:04D9:A04A.0004: item 0 2 2 2 parsing 
failed
  kernel: [3.181199] hid-generic: probe of 0003:04D9:A04A.0004 failed with 
error -22

  
  workaroud:

  In /usr/src/linux/include/linux/hid.h
  change the value of the constant in line 344

  #define HID_MAX_USAGES12288

  from 12288 to a value greater than 32k,
  recompile and install the new kernel.

  Solution found on site: 
  
http://forums.opensuse.org/english/get-technical-help-here/hardware/473200-usb-gaming-mouse-04d9-a078-not-working-linux-plus-workaround.html

  
  # lsb_release -rd
  Description:Ubuntu quantal (development branch)
  Release:12.10

  # apt-cache policy linux-image-extra-3.5.0-17-generic
  linux-image-extra-3.5.0-17-generic:
Zainstalowana: 3.5.0-17.27
Kandydująca:   3.5.0-17.27
Tabela wersji:
   *** 3.5.0-17.27 0
  500 http://pl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarzabek   2309 F pulseaudio
   /dev/snd/controlC0:  jarzabek   2309 F pulseaudio
   /dev/snd/pcmC0D0p:   jarzabek   2309 F...m pulseaudio
  CRDA: Error: [Errno 2] Nie ma takiego pliku ani katalogu
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=44032fe5-8c62-4706-adf6-036103183a07
  IwConfig:
   tun0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=b395cc47-d2bd-4d63-856b-ce6c5d291d3e ro splash quiet
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-16-generic N/A
   linux-backports-modules-3.5.0-16-generic  N/A
   linux-firmware1.94
  RfKill:
   
  Tags:  quantal
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-27 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/20/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1064490] Re: USB Gaming Mouse 04d9:a078 not working

2016-04-24 Thread Edson Oliveira

The mouse is a gaming mouse satellite A-52

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

Title:
  USB Gaming Mouse 04d9:a078 not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  USB Gaming Mouse 04d9:a078 is not working.
  dmesg says:

  kernel: [2.988282] usb 4-2: new full-speed USB device number 3 using 
ohci_hcd
  kernel: [3.163892] usb 4-2: New USB device found, idVendor=04d9, 
idProduct=a04a
  kernel: [3.163899] usb 4-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  kernel: [3.163904] usb 4-2: Product: USB Gaming Mouse
  kernel: [3.163908] usb 4-2: Manufacturer: Newman
  kernel: [3.173664] input: Newman USB Gaming Mouse as 
/devices/pci:00/:00:12.0/usb4/4-2/4-2:1.0/input/input4
  kernel: [3.173744] hid-generic 0003:04D9:A04A.0003: input,hidraw2: USB 
HID v1.10 Keyboard [Newman USB Gaming Mouse] on usb-:00:12.0-2/input0
  kernel: [3.181187] hid-generic 0003:04D9:A04A.0004: usage index exceeded
  kernel: [3.181189] hid-generic 0003:04D9:A04A.0004: item 0 2 2 2 parsing 
failed
  kernel: [3.181199] hid-generic: probe of 0003:04D9:A04A.0004 failed with 
error -22

  
  workaroud:

  In /usr/src/linux/include/linux/hid.h
  change the value of the constant in line 344

  #define HID_MAX_USAGES12288

  from 12288 to a value greater than 32k,
  recompile and install the new kernel.

  Solution found on site: 
  
http://forums.opensuse.org/english/get-technical-help-here/hardware/473200-usb-gaming-mouse-04d9-a078-not-working-linux-plus-workaround.html

  
  # lsb_release -rd
  Description:Ubuntu quantal (development branch)
  Release:12.10

  # apt-cache policy linux-image-extra-3.5.0-17-generic
  linux-image-extra-3.5.0-17-generic:
Zainstalowana: 3.5.0-17.27
Kandydująca:   3.5.0-17.27
Tabela wersji:
   *** 3.5.0-17.27 0
  500 http://pl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarzabek   2309 F pulseaudio
   /dev/snd/controlC0:  jarzabek   2309 F pulseaudio
   /dev/snd/pcmC0D0p:   jarzabek   2309 F...m pulseaudio
  CRDA: Error: [Errno 2] Nie ma takiego pliku ani katalogu
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=44032fe5-8c62-4706-adf6-036103183a07
  IwConfig:
   tun0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=b395cc47-d2bd-4d63-856b-ce6c5d291d3e ro splash quiet
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-16-generic N/A
   linux-backports-modules-3.5.0-16-generic  N/A
   linux-firmware1.94
  RfKill:
   
  Tags:  quantal
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-27 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/20/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread qwertz

Same here, Asus K73SV

** Attachment added: "pm-suspend.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+attachment/4645729/+files/pm-suspend.log

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised

2016-04-24 Thread cement_head

This "bug" report is as a result of BAD USB 3.0 protocols implemented by
the manufacturers of the devices.  And has nothing to do with Linux.
Please file a bug report with the manufacturers.

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread Palaniappan

Same here, with HP Pavillion Laptop

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1574319] [NEW] HDMi sound speed reduced : Intel GPU

2016-04-24 Thread Ekimia

Public bug reported:

Since 16.04 on my Broadwell Low power Intel Mini PC, the sound ( and
video) is playing really low speed which change any sound played on the
PC.

TO overcome that I need to use the i915.disable_power_well=0 grub
switch.

I woud be great to have this work as default.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-base 4.0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 24 17:49:59 2016
Dependencies:
 
InstallationDate: Installed on 2015-11-10 (165 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: linux-base
UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  HDMi sound speed reduced : Intel GPU

Status in linux-base package in Ubuntu:
  New

Bug description:
  Since 16.04 on my Broadwell Low power Intel Mini PC, the sound ( and
  video) is playing really low speed which change any sound played on
  the PC.

  TO overcome that I need to use the i915.disable_power_well=0 grub
  switch.

  I woud be great to have this work as default.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-base 4.0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 17:49:59 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-11-10 (165 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: linux-base
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago)

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

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

[Kernel-packages] [Bug 1468582] Re: Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Attaching requested alsa-info.txt pair and the diff.

Besides constant noise there are terrible clicks and pops during system startup 
and shutdown.
I've attached corresponding audio recordings.


** Patch added: "alsa-info.noisy.diff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468582/+attachment/4645617/+files/alsa-info.noisy.diff

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

Title:
  Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This was reported through community and brought up to support. They
  fixed the bug via kernel bug tracker.

  https://bugzilla.kernel.org/show_bug.cgi?id=99851

  We should backport to 3.13, 3.16 and 3.19

  This bug is used for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1468582/+subscriptions

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

[Kernel-packages] [Bug 1468582] Re: Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

** Attachment added: "alsa-info.normal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468582/+attachment/4645619/+files/alsa-info.normal.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/1468582

Title:
  Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This was reported through community and brought up to support. They
  fixed the bug via kernel bug tracker.

  https://bugzilla.kernel.org/show_bug.cgi?id=99851

  We should backport to 3.13, 3.16 and 3.19

  This bug is used for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1468582/+subscriptions

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

[Kernel-packages] [Bug 1468582] Re: Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

** Attachment added: "alsa-info.noisy.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468582/+attachment/4645620/+files/alsa-info.noisy.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/1468582

Title:
  Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This was reported through community and brought up to support. They
  fixed the bug via kernel bug tracker.

  https://bugzilla.kernel.org/show_bug.cgi?id=99851

  We should backport to 3.13, 3.16 and 3.19

  This bug is used for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1468582/+subscriptions

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

[Kernel-packages] [Bug 1468582] Re: Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

** Attachment added: "Shutdown.mp3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468582/+attachment/4645629/+files/Shutdown.mp3

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

Title:
  Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This was reported through community and brought up to support. They
  fixed the bug via kernel bug tracker.

  https://bugzilla.kernel.org/show_bug.cgi?id=99851

  We should backport to 3.13, 3.16 and 3.19

  This bug is used for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1468582/+subscriptions

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

[Kernel-packages] [Bug 1468582] Re: Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

** Attachment added: "Startup.mp3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468582/+attachment/4645628/+files/Startup.mp3

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

Title:
  Noisy (pop noise + white noise) headphone audio on Dell XPS 13 (2015)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This was reported through community and brought up to support. They
  fixed the bug via kernel bug tracker.

  https://bugzilla.kernel.org/show_bug.cgi?id=99851

  We should backport to 3.13, 3.16 and 3.19

  This bug is used for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1468582/+subscriptions

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread raphael

Same here, using Dell inspiron 5537

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade

2016-04-24 Thread Lior

I report the exact bug description on HP elitebook 840.

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

Title:
  suspend not working after uprade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1568211] Re: no UMS support in radeon module

2016-04-24 Thread datanalytics.com

I forgot to enclose the Xorg.1.log file for a failed boot. Here it goes.

** Attachment added: "Xorg.1.log file for a failed boot (radeon fails to load)"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568211/+attachment/4645405/+files/Xorg.1.log

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

Title:
no UMS support in radeon module

Status in linux package in Ubuntu:
Incomplete

Bug description:
I upgraded overnight from Wily to Xenial. The system will not boot.
Only a blank screen after grub loads the kernel.

The recovery kernel loads fine and I was able to find the following
messages:

[drm] VGACON disable radeon kernel modesetting
[drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

The recovery kernel command line had a nomodeset parameter that was
not in the main kernel command line.

Adding the nomodeset parameter the main kernel command line finally
booted the system. It's kind of ugly but it seems to work.

Note: For what it's worth I reported a similar issue against several
Utopic kernels (bug #1407505). There was a back and forth with
jsalisbury until a kernel finally worked. I have had no problems until
today.

Hope that helps.

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

[Kernel-packages] [Bug 1462169] Re: CVE-2014-9731

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2014-9731

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Fix Released
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1462173] Re: CVE-2015-4167

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2015-4167

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Fix Released
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1453256] Re: CVE-2015-3636

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2015-3636

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Fix Released
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:

[Kernel-packages] [Bug 1260616] Re: CVE-2013-6432

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2013-6432

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
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:
  New
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
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:
  Fix Released
Status in linux-lts-trusty source package in Precise:
  Invalid
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
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:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1465400] Re: CVE-2015-1328

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2015-1328

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Fix Released
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1462175] Re: CVE-2015-4170

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2015-4170

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Invalid
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in

[Kernel-packages] [Bug 1285053] Re: CVE-2014-2038

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2014-2038

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
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:
  New
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
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:
  Fix Released
Status in linux-lts-trusty source package in Precise:
  Invalid
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
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:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in

[Kernel-packages] [Bug 1568211] Re: no UMS support in radeon module

2016-04-24 Thread datanalytics.com

I am facing the same issue. I have upgraded from Xubuntu 14.04 to
Xubuntu 16.04 and I was greeted with a black screen just after my first
reboot.

I use a Radeon HD 5430 card with two monitors. Incidentally, I had to
switch off one of them so that the Live USB from which I installed the
upgrade would work. The problem, though, started with the reboot.

This is the output of my uname -a:

Linux tiramisu 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

There are three ways in which I can "start" my computer:

* Normal boot, which ends in a black screen.
* Recovery mode, which, after selecting "continue boot", generates errors such
as "*ERROR* no UMS support in radeon module!" above, defaults to VESA module
(and poor resolution), and cannot manage two screens. I enclose the Xorg.1.log
file for this method.
* Recovery method and deleting the nomodesetting kernel option. After selecting
"continue boot", I get a perfectly working environment: radeon module works,
etc. I enclose the Xorg.0.log file for this method.

** Attachment added: "Corresponds to a "clean" boot"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568211/+attachment/4645367/+files/Xorg.0.log

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

Title:
no UMS support in radeon module

Status in linux package in Ubuntu:
Incomplete

Bug description:
I upgraded overnight from Wily to Xenial. The system will not boot.
Only a blank screen after grub loads the kernel.

The recovery kernel loads fine and I was able to find the following
messages:

[drm] VGACON disable radeon kernel modesetting
[drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

The recovery kernel command line had a nomodeset parameter that was
not in the main kernel command line.

Adding the nomodeset parameter the main kernel command line finally
booted the system. It's kind of ugly but it seems to work.

Hope that helps.

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

[Kernel-packages] [Bug 1453216] Re: CVE-2014-3534

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2014-3534

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid 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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Invalid
Status in linux-lts-vivid 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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-raspi2 source package in Vivid:
  Invalid
Status in linux-ti-omap4

[Kernel-packages] [Bug 1462165] Re: CVE-2014-9729

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New => Won't Fix

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New => Won't Fix

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

Title:
  CVE-2014-9729

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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:
  Fix Released
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1260619] Re: CVE-2013-7026