[Kernel-packages] [Bug 1391688] Re: Synaptic touchpad not working
Johnathon Henney, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/04/product-support/product/alienware-14/drivers an update to your BIOS is available (A09). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-a09 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391688 Title: Synaptic touchpad not working Status in “linux” package in Ubuntu: Incomplete Bug description: Under 'cat /proc/bus/input/devices' I see my touch pad listed, and the touch pad is on on all settings, but when i use 'xinput --test [val]' there is no response from the touch pad. This happened ever since I installed Ubuntu 14.04.1 LTS no more than two months ago. I am running a Alienware 14 I got back in January. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lifv F pulseaudio /dev/snd/controlC0: lifv F pulseaudio Date: Tue Nov 11 18:32:36 2014 InstallationDate: Installed on 2014-10-26 (16 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Alienware Alienware 14 ProcEnviron: LANGUAGE=en_US 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-39-generic.efi.signed root=UUID=9fe920e5-7374-4415-9887-2db133b1c81c ro quiet splash vt.handoff=7 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-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: Alienware dmi.bios.version: A06 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A06 dmi.modalias: dmi:bvnAlienware:bvrA06:bd10/16/2013:svnAlienware:pnAlienware14:pvrA06:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA06: dmi.product.name: Alienware 14 dmi.product.version: A06 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391744] Re: [HP 14 Notebook PC] Can't resume from suspend state
Lars Hansson, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391744 Title: [HP 14 Notebook PC] Can't resume from suspend state Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu version: 14.10 Video: Intel HD 4000+Nvidia GeForce 820M Expected: Laptop can successfully suspend and resume. What actually happen: Laptop can suspend but upon resume all that is seen is a black screen with an underline cursor in the top left corner. It is possible to switch to VT1 but if you try to switch back to VT7 the laptop stops responding to input. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lars 2398 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 14:26:57 2014 HibernationDevice: RESUME=UUID=5a554079-ba87-4a30-95af-c2c9b60ed506 InstallationDate: Installed on 2014-11-09 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP 14 Notebook PC ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_PH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=0c322239-684b-4a1e-b2b5-d5ce8fe0cedd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21BB dmi.board.vendor: Hewlett-Packard dmi.board.version: 39.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd11/28/2013:svnHewlett-Packard:pnHP14NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21BB:rvr39.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 14 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391758] Re: [Asus UX32VD] Backlight controls have no effect after suspend in most recent kernel
** Attachment added: version https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391758/+attachment/4258898/+files/version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391758 Title: [Asus UX32VD] Backlight controls have no effect after suspend in most recent kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After recent updates, the backlight doesn't work after suspend on my Asus UX32VD laptop. The hotkeys work as far as the Unity graphical indicator goes, but there is no change in backlight. The hotkeys used to work, and have worked for the last couple of years. Backlight is restored and does work after restarting, but can no longer be modified after suspend. This is the output from ls /sys/class/backlight backlight acpi_video0 acpi_video1 intel_backlight This is the output from grep -r . /proc/acpi acpi ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rasmus 2439 F pulseaudio /dev/snd/pcmC0D0p: rasmus 2439 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 08:22:20 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=49ecb728-6268-4421-9baf-b50a95225410 InstallationDate: Installed on 2012-08-10 (823 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=8f94976f-77a4-4e28-a0a8-2e0ce9149ef8 ro quiet splash pcie_aspm=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-05-31 (164 days ago) dmi.bios.date: 06/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.206:bd06/06/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/1391758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391758] Re: [Asus UX32VD] Backlight controls have no effect after suspend in most recent kernel
RK, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/us/Notebooks_Ultrabooks/ASUS_ZENBOOK_UX32VD/HelpDesk_Download/ an update to your BIOS is available (214). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-214 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391758 Title: [Asus UX32VD] Backlight controls have no effect after suspend in most recent kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After recent updates, the backlight doesn't work after suspend on my Asus UX32VD laptop. The hotkeys work as far as the Unity graphical indicator goes, but there is no change in backlight. The hotkeys used to work, and have worked for the last couple of years. Backlight is restored and does work after restarting, but can no longer be modified after suspend. This is the output from ls /sys/class/backlight backlight acpi_video0 acpi_video1 intel_backlight This is the output from grep -r . /proc/acpi acpi ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rasmus 2439 F pulseaudio /dev/snd/pcmC0D0p: rasmus 2439 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 08:22:20 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=49ecb728-6268-4421-9baf-b50a95225410 InstallationDate: Installed on 2012-08-10 (823 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=8f94976f-77a4-4e28-a0a8-2e0ce9149ef8 ro quiet splash pcie_aspm=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-05-31 (164 days ago) dmi.bios.date: 06/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.206:bd06/06/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/1391758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391430] Re: [Dell Inspiron 3441] system is too slow to use.
** Tags added: 201403-14840 taipei-lab ** Tags added: blocks-hwcert -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391430 Title: [Dell Inspiron 3441] system is too slow to use. Status in HWE Next Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: Dell Inspiron 3441 (CID 201403-14840) system is too slow to use. Steps to reproduce the bug: 1. Try to install Ubuntu 14.04.1 on target machine. 2. Log in system. 3. Try to open a terminal. 4. Execute 'glxgears'. Actual results: 1. It takes more then 30 minutes to finish installation. 2. It takes more then 3 seconds to open terminal window. 3. The animation free from slowness. Expected results: System should run smoothly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1990 F pulseaudio /dev/snd/controlC0: ubuntu 1990 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Nov 11 04:14:54 2014 HibernationDevice: RESUME=UUID=2216b507-87f2-42a1-856d-990cc01cd5d5 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3441 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=7a38588d-71d4-42f3-8467-c978be409b0a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: Inspiron 3441 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd04/28/2014:svnDellInc.:pnInspiron3441:pvrNotSpecified:rvnDellInc.:rnInspiron3441:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3441 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1391430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391744] Re: [HP 14 Notebook PC] Can't resume from suspend state
Model number: 14-d004TX -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391744 Title: [HP 14 Notebook PC] Can't resume from suspend state Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu version: 14.10 Video: Intel HD 4000+Nvidia GeForce 820M Expected: Laptop can successfully suspend and resume. What actually happen: Laptop can suspend but upon resume all that is seen is a black screen with an underline cursor in the top left corner. It is possible to switch to VT1 but if you try to switch back to VT7 the laptop stops responding to input. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lars 2398 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 14:26:57 2014 HibernationDevice: RESUME=UUID=5a554079-ba87-4a30-95af-c2c9b60ed506 InstallationDate: Installed on 2014-11-09 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP 14 Notebook PC ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_PH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=0c322239-684b-4a1e-b2b5-d5ce8fe0cedd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21BB dmi.board.vendor: Hewlett-Packard dmi.board.version: 39.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd11/28/2013:svnHewlett-Packard:pnHP14NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21BB:rvr39.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 14 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388869] Re: linux: 2.6.32-68.135 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1388869 Title: linux: 2.6.32-68.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-68.135 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-stable-Prepare-package-start:Monday, 03. November 2014 15:15 UTC kernel-stable-Prepare-package-end:Monday, 03. November 2014 23:03 UTC kernel-stable-Promote-to-proposed-start:Monday, 03. November 2014 23:03 UTC ppa-package-testing-start:Monday, 03. November 2014 23:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 04. November 2014 09:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 04. November 2014 10:01 UTC kernel-stable-Verification-testing-start:Tuesday, 04. November 2014 10:01 UTC kernel-stable-Certification-testing-start:Tuesday, 04. November 2014 10:01 UTC kernel-stable-Security-signoff-start:Tuesday, 04. November 2014 10:01 UTC kernel-stable-Regression-testing-start:Tuesday, 04. November 2014 10:01 UTC kernel-stable-Regression-testing-end:Thursday, 06. November 2014 13:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1388869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391339] Re: Trusty kernel inbound network performance regression when GRO is enabled
Hi Rodrigo, there is a possibility that the problem is not a regression
in handling GRO but actually supporting GRO. I can find the following
commit in 3.13-rc1:
commit 99d3d587b2b4314ccc8ea066cb327dfb523d598e
Author: Wei Liu wei.l...@citrix.com
Date: Mon Sep 30 13:46:34 2013 +0100
xen-netfront: convert to GRO API
Now I tried to reproduce the performance issue locally and using a
Xen-4.4.1 Trusty host which runs a Trusty PV guest. On the guest side I
start iperf in server mode (since that is the receive side, but to be
sure I reversed the setup with the same results) and on a desktop
running Trusty, I start iperf in client mode connecting to the PV guest.
The desktop and host have 1Gbit NICs. With that I get an average of
about 850Mbit/sec over 10 runs. Which is as good as I would expect it.
And this does not change significantly whether I enable or disable GRO.
Now what we do not know is what gets involved network-wise between your
server and the guests. Not really sure how this would possibly happen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1391339
Title:
Trusty kernel inbound network performance regression when GRO is
enabled
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading our EC2 instances from Lucid to Trusty we noticed an
increase on download times, Lucid instances were able to download
twice as fast as Trusty. After some investigation and testing older
kernels (precise, raring and saucy) we confirmed that this only
happens on trusty kernel or newer since utopic kernel shows the same
result and disabling gro with `ethtool -K eth0 gro off` seems to fix
the problem making download speed the same as the Lucid instances
again.
The problem is easily reproducible using Apache Bench a couple times
on files bigger than 100MB on 1Gb network (EC2) using HTTP or HTTPS.
Following is an example of download throughput with and without gro:
root@runtime-common.22 ~# ethtool -K eth0 gro off
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 85183.40 [Kbytes/sec] received
Transfer rate: 86375.80 [Kbytes/sec] received
Transfer rate: 94720.24 [Kbytes/sec] received
Transfer rate: 84783.82 [Kbytes/sec] received
Transfer rate: 84933.09 [Kbytes/sec] received
Transfer rate: 84714.04 [Kbytes/sec] received
Transfer rate: 84795.58 [Kbytes/sec] received
Transfer rate: 84636.54 [Kbytes/sec] received
Transfer rate: 84924.26 [Kbytes/sec] received
Transfer rate: 84994.10 [Kbytes/sec] received
root@runtime-common.22 ~# ethtool -K eth0 gro on
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 74193.53 [Kbytes/sec] received
Transfer rate: 56808.91 [Kbytes/sec] received
Transfer rate: 56011.58 [Kbytes/sec] received
Transfer rate: 82227.74 [Kbytes/sec] received
Transfer rate: 70806.54 [Kbytes/sec] received
Transfer rate: 72848.10 [Kbytes/sec] received
Transfer rate: 58451.94 [Kbytes/sec] received
Transfer rate: 61221.33 [Kbytes/sec] received
Transfer rate: 58620.21 [Kbytes/sec] received
Transfer rate: 69950.03 [Kbytes/sec] received
root@runtime-common.22 ~#
Similar results can be observed using iperf and netperf as well.
Tested kernels:
Not affected: 3.8.0-44-generic (precise/raring), 3.11.0-26-generic (saucy)
Affected: 3.13.0-39-generic (trusty), 3.16.0-24-generic (utopic)
Let me know if I can provide any other information that might be helpful like
perf traces and reports.
Rodrigo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391339/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389170] Re: linux: 3.16.0-25.33 -proposed tracker
So far there is no system pass the certificate for 14.10 yet, we will not running certification-testing for 3.16 kernel in this cycle. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389170 Title: linux: 3.16.0-25.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Utopic: Confirmed Bug description: This bug is for tracking the 3.16.0-25.33 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-stable-Prepare-package-start:Tuesday, 04. November 2014 10:43 UTC kernel-stable-Prepare-package-end:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 04. November 2014 21:03 UTC ppa-package-testing-start:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 05. November 2014 01:44 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Verification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Certification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Security-signoff-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-end:Saturday, 08. November 2014 05:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1389170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391339] Re: Trusty kernel inbound network performance regression when GRO is enabled
I meant, not sure how to get traffic coming in in a way that GRO
actually slows things down instead of lowering the impact of processing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1391339
Title:
Trusty kernel inbound network performance regression when GRO is
enabled
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading our EC2 instances from Lucid to Trusty we noticed an
increase on download times, Lucid instances were able to download
twice as fast as Trusty. After some investigation and testing older
kernels (precise, raring and saucy) we confirmed that this only
happens on trusty kernel or newer since utopic kernel shows the same
result and disabling gro with `ethtool -K eth0 gro off` seems to fix
the problem making download speed the same as the Lucid instances
again.
The problem is easily reproducible using Apache Bench a couple times
on files bigger than 100MB on 1Gb network (EC2) using HTTP or HTTPS.
Following is an example of download throughput with and without gro:
root@runtime-common.22 ~# ethtool -K eth0 gro off
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 85183.40 [Kbytes/sec] received
Transfer rate: 86375.80 [Kbytes/sec] received
Transfer rate: 94720.24 [Kbytes/sec] received
Transfer rate: 84783.82 [Kbytes/sec] received
Transfer rate: 84933.09 [Kbytes/sec] received
Transfer rate: 84714.04 [Kbytes/sec] received
Transfer rate: 84795.58 [Kbytes/sec] received
Transfer rate: 84636.54 [Kbytes/sec] received
Transfer rate: 84924.26 [Kbytes/sec] received
Transfer rate: 84994.10 [Kbytes/sec] received
root@runtime-common.22 ~# ethtool -K eth0 gro on
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 74193.53 [Kbytes/sec] received
Transfer rate: 56808.91 [Kbytes/sec] received
Transfer rate: 56011.58 [Kbytes/sec] received
Transfer rate: 82227.74 [Kbytes/sec] received
Transfer rate: 70806.54 [Kbytes/sec] received
Transfer rate: 72848.10 [Kbytes/sec] received
Transfer rate: 58451.94 [Kbytes/sec] received
Transfer rate: 61221.33 [Kbytes/sec] received
Transfer rate: 58620.21 [Kbytes/sec] received
Transfer rate: 69950.03 [Kbytes/sec] received
root@runtime-common.22 ~#
Similar results can be observed using iperf and netperf as well.
Tested kernels:
Not affected: 3.8.0-44-generic (precise/raring), 3.11.0-26-generic (saucy)
Affected: 3.13.0-39-generic (trusty), 3.16.0-24-generic (utopic)
Let me know if I can provide any other information that might be helpful like
perf traces and reports.
Rodrigo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391339/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389170] Re: linux: 3.16.0-25.33 -proposed tracker
** Description changed: This bug is for tracking the 3.16.0-25.33 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-stable-Prepare-package-start:Tuesday, 04. November 2014 10:43 UTC kernel-stable-Prepare-package-end:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 04. November 2014 21:03 UTC ppa-package-testing-start:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 05. November 2014 01:44 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Verification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Certification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Security-signoff-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-end:Saturday, 08. November 2014 05:01 UTC + kernel-stable-Certification-testing-end:Wednesday, 12. November 2014 09:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389170 Title: linux: 3.16.0-25.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Utopic: Confirmed Bug description: This bug is for tracking the 3.16.0-25.33 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-stable-Prepare-package-start:Tuesday, 04. November 2014 10:43 UTC kernel-stable-Prepare-package-end:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 04. November 2014 21:03 UTC ppa-package-testing-start:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 05. November 2014 01:44 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Verification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Certification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Security-signoff-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-end:Saturday, 08. November 2014 05:01 UTC kernel-stable-Certification-testing-end:Wednesday, 12. November 2014 09:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1389170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
when can we expect a push to a kernel update on 14.04? Iam not that good at IT - Ido not know how to compile, etc... :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Status in “linux” package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1387420] Re: System freezes when performing a backup bash script
I tried 3.18-rc1. I got the same result as with rc3 and rc4: a black screen. But this time, I also noticed a message quickly flashing (lasting only a second or two): kvm: disabled by bios. So far, I tried: v3.18-rc1-utopic v3.18-rc2-utopic v3.18-rc3-vivid v3.18-rc4-vivid (I didn't try v3.18-rc2-vivid. Joseph Salisbury directed me to v3.18-rc2-utopic.) Please let me know if there are other versions I should try. (By the way, what I do is install the generic amd64 linux image. For rc1, I downloaded linux- image-3.18.0-031800rc1-generic_3.18.0-031800rc1.201410192135_amd64.deb, and installed it using Ubuntu Software Centre. That's the procedure I've been following with the other versions as well.) ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1387420 Title: System freezes when performing a backup bash script Status in “linux” package in Ubuntu: Confirmed Bug description: I attached the bash script I use for performing backup. When performing backup, I connect my external hard drive and a flash drive, open a terminal window, and execute the script. Half the time it works without a problem; the other half, the system freezes and I need to restart the computer - but the backup still performs correctly; the freezing seems to happen immediately when it's done. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aviv 1511 F pulseaudio /dev/snd/controlC0: aviv 1511 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 29 18:58:25 2014 HibernationDevice: RESUME=UUID=a41b2680-73ee-49de-a2be-80cbaea2f0df InstallationDate: Installed on 2014-05-28 (154 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. M51AC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=0eadde87-8ed5-49d9-afdf-84d4b4ce6d9c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rtl8821ae UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M51AC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd07/25/2013:svnASUSTeKCOMPUTERINC.:pnM51AC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM51AC:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M51AC dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1387420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package
I'm hoping there will be a server daemon (usbipd) eventually. For the client, it seems that usbip from the package usbip is no longer valid and is replaced by usbip in a package called linux-tools-generic. There is no usbipd server in this replacement package yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/900384 Title: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package Status in “linux” package in Ubuntu: Fix Released Status in “usbip” package in Ubuntu: Confirmed Bug description: I'm on Kubuntu oneiric (11.10), using usbip 0.1.7-3 and kernel linux- image-3.0.0-13-generic. I'm trying to set up USB/IP to share a USB-only printer/scanner over the LAN. However, whenever I try to start the demon, it gives the error message that the usbip_common_mod.ko and usbip.ko kernel modules are required: root@curie:~# usbipd -D usbip err: stub_driver.c: 33 (open_sysfs_stub_driver) usbip_common_mod.ko and usbip.ko must be loaded ** ERROR **: driver open failed Trace/breakpoint trap The package description of usbip says: USB/IP requires kernel support which is included in Linux kernels 2.6.28 or newer. Unfortunately, I can't find a package that provides those kernel module. I have also installed the usbip-source package, but (1) its /usr/src/modules/usbip/src/README file says: For newer kernels ( =2.6.28 ), try linux-staging code! and (2) trying to build it with m-a also fails: # Build the module cd src /usr/bin/make KSOURCE=/usr/src/linux HCD_HEADER=/usr/src/modules/usbip/src/headers/hcd.h KBUILD_VERBOSE=0 make[2]: Entering directory `/usr/src/modules/usbip/src' make -C /usr/src/linux LANG=C KBUILD_VERBOSE=0 M=`pwd` modules make[3]: Entering directory `/usr/src/linux-headers-3.0.0-13-generic' CC [M] /usr/src/modules/usbip/src/stub_dev.o /usr/src/modules/usbip/src/stub_dev.c: In function ‘stub_probe’: /usr/src/modules/usbip/src/stub_dev.c:392:42: error: ‘struct device’ has no member named ‘bus_id’ make[4]: *** [/usr/src/modules/usbip/src/stub_dev.o] Error 1 make[3]: *** [_module_/usr/src/modules/usbip/src] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-3.0.0-13-generic' make[2]: *** [default] Error 2 make[2]: Leaving directory `/usr/src/modules/usbip/src' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/usbip' make: *** [kdist_build] Error 2 BUILD FAILED! See /var/cache/modass/usbip.buildlog.3.0.0-13-generic.1323105464 for details. Build failed. Press Return to continue... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381906] Re: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
Hello Anthony, The command can't fix it, tested with the following steps: 1. sudo /usr/bin/setpci -s 00:14 d0.w=0x01db 2. Suspend 3. Wake it up and check the BT status The Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. rfkill before S3: ubuntu@201406-15271:~$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no rfkill after S3: ubuntu@201406-15271:~$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no ** Attachment added: dmesg.log https://bugs.launchpad.net/hwe-next/+bug/1381906/+attachment/4259000/+files/dmesg.log ** Changed in: hwe-next Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system
Hello Hui, the DKMS file you provided here could not make the LED work. Steps: 1. Create an entry at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle 2. Update it with sudo udevadm hwdb -u 3. Install the DKMS file provided in comment #5 4. reboot and test the mic mute key. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by xev or sudo showkey -s But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
Does this actually need to be fixed on the kernel side in Trusty? I'm a bit confused by the fix released status of linux in utopic, as far as I know most issues can be fixed in udev's keymaps alone? ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) 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/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work Status in HWE Next Project: Fix Released Status in HWE Next trusty series: New Status in HWE Next utopic series: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Incomplete Status in “systemd” source package in Trusty: New Bug description: CID: 201402-14663 Dell Latitude 12 Rugged Extreme The microphone mute key does not work on this system, so as its LED Steps: 1. Install 14.04 + update (3.13.0-30), boot to desktop 2. Try to mute the microphone with the hotkey (fn+F4) Expected results: * Mic mute key should work, its LED should be lit and the Mute option for input device should be ticked after you press the mic mute key. Actual result: * Nothing happened. Debugging information: ubuntu@201402-14663:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 29 press ^Ccaught signal 2, cleaning up... xev cannot detect any microphone mute key event ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1501 F pulseaudio /dev/snd/controlC0: ubuntu 1501 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jul 9 23:57:11 2014 HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734 InstallationDate: Installed on 2014-07-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0TH1GJ dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 12 Rugged Extreme (7204) dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381851] Re: [Dell Latitude E5550] Brightness control does not work on this system
Yes, but it will be great if it could pass with 3.13 kernel, in that case, we won't need to deal with the kernel upgrade issue like what we're dealing with recently (3.5 / 3.8 / 3.11 - 3.13) However, we should wait and see how many blocker would be solved on this system, then we decide if it's worth to fix it in 3.13. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381851 Title: [Dell Latitude E5550] Brightness control does not work on this system Status in HWE Next Project: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201406-15271 Dell Latitude E5550 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201406-15271:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201406-15271:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate:772 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3170 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3540 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3372 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 354 mAh /proc/acpi/battery/BAT0/info:design capacity low: 107 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 35 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 35 mAh /proc/acpi/battery/BAT0/info:model number:DELL 9P4D246 /proc/acpi/battery/BAT0/info:serial number: 226 /proc/acpi/battery/BAT0/info:battery type:LiP /proc/acpi/battery/BAT0/info:OEM info:LGC-LGC3.4 /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/AC/state:state: off-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled pci::01:00.0 /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:GLAN S4*disabled pci::00:19.0 /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S0*disabled /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:PBTN S3*enabled ubuntu@201406-15271:~$ dmesg | grep 'ACPI: Video' [ 12.986933] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201406-15271:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 15 23:03:45 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release
[Kernel-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
I uploaded an SRU to the trusty review queue with the latest upstream keymaps which include the fix for this bug. Note that accepting the SRU is currently blocked on verifying the current SRU in trusty-proposed (bug 1367883). ** Changed in: systemd (Ubuntu Trusty) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work Status in HWE Next Project: Fix Released Status in HWE Next trusty series: New Status in HWE Next utopic series: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Incomplete Status in “systemd” source package in Trusty: In Progress Bug description: CID: 201402-14663 Dell Latitude 12 Rugged Extreme The microphone mute key does not work on this system, so as its LED Steps: 1. Install 14.04 + update (3.13.0-30), boot to desktop 2. Try to mute the microphone with the hotkey (fn+F4) Expected results: * Mic mute key should work, its LED should be lit and the Mute option for input device should be ticked after you press the mic mute key. Actual result: * Nothing happened. Debugging information: ubuntu@201402-14663:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 29 press ^Ccaught signal 2, cleaning up... xev cannot detect any microphone mute key event ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1501 F pulseaudio /dev/snd/controlC0: ubuntu 1501 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jul 9 23:57:11 2014 HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734 InstallationDate: Installed on 2014-07-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0TH1GJ dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 12 Rugged Extreme (7204) dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391496] Re: Can not enter password to decrypt disk at boot
Updating the BIOS doesn't change the behaviour described in the bug description. It is still not possible to enter the disk encryption passphrase at boot when running the 3.16.0-24-generic kernel. The keyboard is function (eg ctrl-alt-del reboots the machine when the encryption passphrase screen is displayed), but typing does not cause any text to be entered. Booting with the previous kernel (3.13.0-39-generic) means the passphrase can be entered as normal at boot. I would argue this issue has more than Low importance as it has the potential to totally lock people out of their systems after an upgrade. sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date: SWQ6710H.86A.0067.2014.0313.1347 03/13/2014 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391496 Title: Can not enter password to decrypt disk at boot Status in “linux” package in Ubuntu: Confirmed Bug description: I have upgraded from Ubuntu 14.04 to 14.10. My whole disk is encrypted with luks and since the upgrade I have found I can no longer unlock my disk at boot. The enter password screen appears, but typing does not cause any characters to appear in the password box. However, if I hit ctrl-alt f7 (not sure of the precise function key) I get a black screen with a flashing white cursor and I can see the password that I entered. This would seem to imply that this is not a problem with the usb drivers, as has been reported in other similar bugs. It's as if the focus is simply in the wrong place at the time when I need to enter my password. Entering the password anyway and pressing enter has no effect. By using Grub to select the previous kernel, I can then decrypt my disk and use the system as normal. The working kernel version is 3.13.0-39-generic. The problematic kernel is 3.16.0-24-generic. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: mjs510 3162 F pulseaudio /dev/snd/controlC2: mjs510 3162 F pulseaudio /dev/snd/controlC1: mjs510 3162 F pulseaudio /dev/snd/controlC0: mjs510 3162 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=66fe5f6c-9937-43f3-90ed-9764c8a9a263 IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.138 RfKill: Tags: utopic Uname: Linux 3.13.0-39-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0049.2011.0314.1053 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67SW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12527-308 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0049.2011.0314.1053:bd03/14/2011:svnViglen:pn:pvr:rvnIntelCorporation:rnDQ67SW:rvrAAG12527-308:cvn:ct3:cvr: dmi.sys.vendor: Viglen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed
I have no PPA etc. installed. But upstream kernel builds are not easy to test as Macbook users depend on the restricted Broadcom Wifi driver which (from repos) does not work with the mainline builds. Also it is very unpleasant to install unsigned kernel packages from a HTTP server on a production system. But the biggest problem is that it isn't a deterministic bug. Some times it works, some times it does not. I think that it works most of the time with the versions if proposed updates are decativated. With the versions from proposed updates, it seems to work almost never. I think that the update of xserver-xorg-video-intel is also relevant. The other issue, why it is hard to test, is kind of a separate bug. Even if suspend works, it takes half a minute until sleep state is actually reached (indicated by the keyboard backlight turning off). This is a problem, because you notice the failure of the suspend operation half a minute later. On today's super silent laptops you cannot even tell from the outside with closed lid whether it is running or sleeping. You only may see after many minutes that the computer is getting very warm. For regular users this hell. They close their lid, everything seems fine. They put it into their bag, everything seems fine. After hours they notive that their computer is hot and battery dead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391476 Title: [MacBookPro11,1] Laptop wakes up while lid closed Status in “linux” package in Ubuntu: Incomplete Bug description: Same behavior when using pm-suspend. This bug may be CRITICAL, because it is hard to notice whether the laptop waking up, especially because that does not always happen immediately. Getting to sleep takes up to 30 seconds. Hardware damage may be a result of waking up while lid is closed, for example if laptop is transported in a bag. I suspect that the problem comes from the Intel video driver. See extract from kern.log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stephan2266 F pulseaudio /dev/snd/controlC1: stephan2266 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 11 12:11:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (33 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 003: ID 05ac:0259 Apple, Inc. Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago) WifiSyslog: dmi.bios.date: 02/12/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B07.1402121134 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: stephan2266 F...m pulseaudio /dev/snd/controlC0: stephan2266 F pulseaudio /dev/snd/controlC1: stephan2266 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (34 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux (not
[Kernel-packages] [Bug 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death
Same issue with Apple Keyboard... -- 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/1341256 Title: Press caps lock on bluetooth keyboard then the keyboard go death Status in “bluez” package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358373] Re: sed: -e expression #1, char 6: unknown command: `m'
Has been fixed in Vivid, and might be backported in Utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1358373 Title: sed: -e expression #1, char 6: unknown command: `m' Status in “dkms” package in Ubuntu: Confirmed Status in “dkms” package in Debian: Fix Released Bug description: Initial dkms setup triggers a sed error, sed: -e expression #1, char 6: unknown command: `m'. This error does not appear to affect the setup and it completes. See the log below: -- sudo apt-get install virtualbox-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: virtualbox-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/556 kB of archives. After this operation, 4,494 kB of additional disk space will be used. Selecting previously unselected package virtualbox-dkms. (Reading database ... 321942 files and directories currently installed.) Preparing to unpack .../virtualbox-dkms_4.3.14-dfsg-1_all.deb ... Unpacking virtualbox-dkms (4.3.14-dfsg-1) ... Setting up virtualbox-dkms (4.3.14-dfsg-1) ... Loading new virtualbox-4.3.14 DKMS files... First Installation: checking all kernels... Building for 3.16.0-7-generic and 3.16.0-9-generic Building initial module for 3.16.0-7-generic Done. vboxdrv: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/ vboxpci.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-7-generic/updates/dkms/ sed: -e expression #1, char 6: unknown command: `m' depmod DKMS: install completed. Building initial module for 3.16.0-9-generic Done. vboxdrv: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/ vboxpci.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-9-generic/updates/dkms/ sed: -e expression #1, char 6: unknown command: `m' depmod DKMS: install completed. * Stopping VirtualBox kernel modules [ OK ] * Starting VirtualBox kernel modules [ OK ] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: virtualbox-dkms 4.3.14-dfsg-1 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 11:51:26 2014 InstallationDate: Installed on 2013-12-19 (241 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218) PackageArchitecture: all SourcePackage: virtualbox SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to utopic on 2014-05-09 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1358373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1070150] Re: Intermittent black screen or low graphics mode message
*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 ** This bug has been marked a duplicate of bug 969489 lightdm tries (and fails) to start too early? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1070150 Title: Intermittent black screen or low graphics mode message Status in Light Display Manager: New Status in “linux” package in Ubuntu: Fix Released Bug description: Update - 01.19.13 Some systems are intermittently booting to a black screen or message about low graphics mode but a graphical login display never loads. Multiple GPU's are affected. Intel HD graphics driver and ATI open source driver are confirmed to have the issue. Nvidia binary driver and Nouveau driver still unconfirmed. Multiple users are affected here: http://ubuntuforums.org/showthread.php?t=2073483 There are currently three known workarounds to this issue: 1) Log in with CTRL+ALT+F1 and issue command sudo service lightdm restart 2) Add some sleep to /etc/init/lightdm.conf 3) Install and use GDM instead of lightdm lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 uname -a Linux matt-pc 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 2002 F pulseaudio Date: Mon Oct 22 20:55:29 2012 HibernationDevice: RESUME=UUID=d9a43e39-0d27-4a5b-90ca-79dc0278afa2 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=85247ab4-6b7d-4d5a-a265-73b485861e24 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1606 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1606:bd08/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1070150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391732] Re: Ubuntu 14.4 problem
I got the following error ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net You can reset the credentials by removing the file /home/kipawa/.cache/apport/launchpad.credentials However internet connection is fine and everything else on terminal is also good. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391732 Title: Ubuntu 14.4 problem Status in “linux” package in Ubuntu: Confirmed Bug description: My touchpad is not working ever since I installed ubuntu 14.4 . However connecting mouse works. On running the command cat /proc/bus/input/devices , touchpad is not shown up too. I am using Dell Inpiron 3521 model. Synaptics touchpad Touchpad not working ever since I installed ubuntu 14.4 . Please help me. I am attaching the required files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1316221] Re: [Lenovo Thinkpad Twist] Won't stay suspended after first suspend
This is a painfully intermittent problem. I thought it had gone away completely but then it returned with Kernel 3.17.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1316221 Title: [Lenovo Thinkpad Twist] Won't stay suspended after first suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I am running 14.04 Trusty Tahr with KDE, so this is *not* a mir or Unity issue. After boot, the system will suspend once, then after that it will wake up on its own immediately after suspend. WORKAROUND: Running the following will fix the issue until the following reboot: echo EHC1 | sudo tee /proc/acpi/wakeup --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE CurrentDmesg: [ 10.300317] psmouse serio2: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64 [ 12.247478] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 12.563146] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=438d66a9-3409-4433-b18a-92b6d483243b InstallationDate: Installed on 2014-05-03 (4 days ago) InstallationMedia: KXStudio 14.04 (Live 64bit) MachineType: LENOVO 33474HU NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-lowlatency root=UUID=82174999-4881-4475-8d12-25652dc0db33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-lowlatency 3.13.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-lowlatency N/A linux-backports-modules-3.13.0-24-lowlatency N/A linux-firmware1.127 Tags: trusty Uname: Linux 3.13.0-24-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GDET33WW (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET33WW(1.03):bd08/30/2012:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33474HU dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1316221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381851] Re: [Dell Latitude E5550] Brightness control does not work on this system
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) = (unassigned) ** Changed in: hwe-next Status: Incomplete = Triaged ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381851 Title: [Dell Latitude E5550] Brightness control does not work on this system Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Triaged Bug description: CID: 201406-15271 Dell Latitude E5550 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201406-15271:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201406-15271:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate:772 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3170 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3540 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3372 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 354 mAh /proc/acpi/battery/BAT0/info:design capacity low: 107 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 35 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 35 mAh /proc/acpi/battery/BAT0/info:model number:DELL 9P4D246 /proc/acpi/battery/BAT0/info:serial number: 226 /proc/acpi/battery/BAT0/info:battery type:LiP /proc/acpi/battery/BAT0/info:OEM info:LGC-LGC3.4 /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/AC/state:state: off-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled pci::01:00.0 /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:GLAN S4*disabled pci::00:19.0 /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S0*disabled /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:PBTN S3*enabled ubuntu@201406-15271:~$ dmesg | grep 'ACPI: Video' [ 12.986933] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201406-15271:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 15 23:03:45 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1391892] [NEW] Resume failes when on AC power
Public bug reported: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Re: Resume failes when on AC power
3.16.0-25.33-generic 3.16.7 ** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+attachment/4259083/+files/lspci-vnvn.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/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1391892 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/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Re: Resume failes when on AC power
apport information ** Tags added: apport-collected utopic ** Description changed: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. - When on AC after resume you can move the mouse and see you desktop but - nothing is clickable. Only way I have been able to get around this is - to switch to a different terminal and reboot the machine. + When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tim2282 F pulseaudio + /dev/snd/controlC0: tim2282 F pulseaudio + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 + InstallationDate: Installed on 2014-10-23 (19 days ago) + InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) + MachineType: LENOVO 20266 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 + 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-3.16.0-25-generic N/A + linux-backports-modules-3.16.0-25-generic N/A + linux-firmware 1.138 + Tags: utopic + Uname: Linux 3.16.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 06/27/2014 + dmi.bios.vendor: LENOVO + dmi.bios.version: 76CN38WW + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Yoga2 + 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 Yoga 2 Pro + dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: + dmi.product.name: 20266 + dmi.product.version: Lenovo Yoga 2 Pro + dmi.sys.vendor: LENOVO ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259092/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014
[Kernel-packages] [Bug 1391892] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259098/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259099/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259094/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259096/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259095/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259103/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259100/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259093/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259104/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259097/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259102/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259101/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1391892/+attachment/4259105/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Confirmed Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390802] Re: [HP Pavilion g6-1322sr Notebook PC] Ubuntu sometimes starts with display disabled
3.14-rc4 seems to work well, or I tested it not too many times. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1390802 Title: [HP Pavilion g6-1322sr Notebook PC] Ubuntu sometimes starts with display disabled Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu sometimes starting with display disabled on my HP g6-1322sr. It can be 3 times in row, or 10 times all will be ok. Sometimes after Ubuntu start, you can hear login screen sound, but display doesn't work. To make display work I switch to tty1 (display doesn't work too) and make ctrl+alt+del. Help! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ihor 2388 F pulseaudio /dev/snd/controlC0: ihor 2388 F pulseaudio CRDA: country UA: DFS-UNSET (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Date: Sat Nov 8 22:43:47 2014 HibernationDevice: RESUME=UUID=77ad43ba-c7e9-4e4a-9057-d8a59af8c6c2 InstallationDate: Installed on 2014-11-04 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=1d31f24b-268d-48f1-a164-0c11a0caf414 ro quiet splash vt.handoff=7 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-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0695130046160:rvnHewlett-Packard:rn3566:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 0695130046160 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391908] [NEW] ASUS X551MA: Ubuntu 14.04 freezes from time to time
Public bug reported: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox of Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: New Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox of Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA
[Kernel-packages] [Bug 1391908] 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/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: Confirmed Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox of Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA 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/1391908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391912] [NEW] signal strength indication doesn't work
Public bug reported: Connecting an Ubuntu phone to my car works fine for calls, however, the car has an indication of the GSM signal strength which works with other devices, but always stays at 0 for Ubuntu phones. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1391912 Title: signal strength indication doesn't work Status in “bluez” package in Ubuntu: New Bug description: Connecting an Ubuntu phone to my car works fine for calls, however, the car has an indication of the GSM signal strength which works with other devices, but always stays at 0 for Ubuntu phones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1391912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391908] Re: ASUS X551MA: Ubuntu 14.04 freezes from time to time
** Description changed: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. - Always it was when I was using Internet via Chrome or Firefox of + Always it was when I was using Internet via Chrome or Firefox or Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: yustnip1798 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd - Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse - Bus 001 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 004: ID 04f2:b404 Chicony Electronics Co., Ltd + Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-39-generic N/A - linux-backports-modules-3.13.0-39-generic N/A - linux-firmware 1.127.8 + linux-restricted-modules-3.13.0-39-generic N/A + linux-backports-modules-3.13.0-39-generic N/A + linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA 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/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: Confirmed Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox or Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1391744] Re: [HP 14 Notebook PC] Can't resume from suspend state
Lars Hansson, as per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4158lc=encc=usdlc=ensw_lang=product=6753960#N7511 an update to your BIOS is available (F.18). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-f.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391744 Title: [HP 14 Notebook PC] Can't resume from suspend state Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu version: 14.10 Video: Intel HD 4000+Nvidia GeForce 820M Expected: Laptop can successfully suspend and resume. What actually happen: Laptop can suspend but upon resume all that is seen is a black screen with an underline cursor in the top left corner. It is possible to switch to VT1 but if you try to switch back to VT7 the laptop stops responding to input. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lars 2398 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 14:26:57 2014 HibernationDevice: RESUME=UUID=5a554079-ba87-4a30-95af-c2c9b60ed506 InstallationDate: Installed on 2014-11-09 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP 14 Notebook PC ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_PH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=0c322239-684b-4a1e-b2b5-d5ce8fe0cedd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21BB dmi.board.vendor: Hewlett-Packard dmi.board.version: 39.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd11/28/2013:svnHewlett-Packard:pnHP14NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21BB:rvr39.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 14 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1387420] Re: System freezes when performing a backup bash script
The Aviv, just to clarify, following the instructions in https://wiki.ubuntu.com/Kernel/MainlineBuilds one would install three files for a given kernel version. Are you doing this, or only installing one as your comment would be suggesting? Also, could you please test v3.17.2-vivid/ and advise to the results? If this doesn't give you a testable environment, please feel free to test the next most recent version until you have one. ** 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/1387420 Title: System freezes when performing a backup bash script Status in “linux” package in Ubuntu: Incomplete Bug description: I attached the bash script I use for performing backup. When performing backup, I connect my external hard drive and a flash drive, open a terminal window, and execute the script. Half the time it works without a problem; the other half, the system freezes and I need to restart the computer - but the backup still performs correctly; the freezing seems to happen immediately when it's done. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aviv 1511 F pulseaudio /dev/snd/controlC0: aviv 1511 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 29 18:58:25 2014 HibernationDevice: RESUME=UUID=a41b2680-73ee-49de-a2be-80cbaea2f0df InstallationDate: Installed on 2014-05-28 (154 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. M51AC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=0eadde87-8ed5-49d9-afdf-84d4b4ce6d9c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rtl8821ae UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M51AC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd07/25/2013:svnASUSTeKCOMPUTERINC.:pnM51AC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM51AC:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M51AC dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1387420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391496] Re: Can not enter password to decrypt disk at boot
Max Spicer, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.18-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-0067 ** Tags added: latest-bios-0067 ** Changed in: linux (Ubuntu) Importance: Low = High ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Summary changed: - Can not enter password to decrypt disk at boot + [Intel DQ67SW] Can not enter password to decrypt disk at boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391496 Title: [Intel DQ67SW] Can not enter password to decrypt disk at boot Status in “linux” package in Ubuntu: Incomplete Bug description: I have upgraded from Ubuntu 14.04 to 14.10. My whole disk is encrypted with luks and since the upgrade I have found I can no longer unlock my disk at boot. The enter password screen appears, but typing does not cause any characters to appear in the password box. However, if I hit ctrl-alt f7 (not sure of the precise function key) I get a black screen with a flashing white cursor and I can see the password that I entered. This would seem to imply that this is not a problem with the usb drivers, as has been reported in other similar bugs. It's as if the focus is simply in the wrong place at the time when I need to enter my password. Entering the password anyway and pressing enter has no effect. By using Grub to select the previous kernel, I can then decrypt my disk and use the system as normal. The working kernel version is 3.13.0-39-generic. The problematic kernel is 3.16.0-24-generic. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: mjs510 3162 F pulseaudio /dev/snd/controlC2: mjs510 3162 F pulseaudio /dev/snd/controlC1: mjs510 3162 F pulseaudio /dev/snd/controlC0: mjs510 3162 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=66fe5f6c-9937-43f3-90ed-9764c8a9a263 IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.138 RfKill: Tags: utopic Uname: Linux 3.13.0-39-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0049.2011.0314.1053 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67SW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12527-308 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0049.2011.0314.1053:bd03/14/2011:svnViglen:pn:pvr:rvnIntelCorporation:rnDQ67SW:rvrAAG12527-308:cvn:ct3:cvr: dmi.sys.vendor: Viglen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1316221] Re: [Lenovo Thinkpad Twist] Won't stay suspended after first suspend
Fen Labalme, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. As well, please do not announce in this report you created a new bug report. Thank you for your understanding. Helpful bug reporting tips: 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/1316221 Title: [Lenovo Thinkpad Twist] Won't stay suspended after first suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I am running 14.04 Trusty Tahr with KDE, so this is *not* a mir or Unity issue. After boot, the system will suspend once, then after that it will wake up on its own immediately after suspend. WORKAROUND: Running the following will fix the issue until the following reboot: echo EHC1 | sudo tee /proc/acpi/wakeup --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE CurrentDmesg: [ 10.300317] psmouse serio2: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64 [ 12.247478] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 12.563146] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=438d66a9-3409-4433-b18a-92b6d483243b InstallationDate: Installed on 2014-05-03 (4 days ago) InstallationMedia: KXStudio 14.04 (Live 64bit) MachineType: LENOVO 33474HU NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-lowlatency root=UUID=82174999-4881-4475-8d12-25652dc0db33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-lowlatency 3.13.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-lowlatency N/A linux-backports-modules-3.13.0-24-lowlatency N/A linux-firmware1.127 Tags: trusty Uname: Linux 3.13.0-24-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GDET33WW (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET33WW(1.03):bd08/30/2012:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33474HU dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1316221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390802] Re: [HP Pavilion g6-1322sr Notebook PC] Ubuntu sometimes starts with display disabled
Ihor Romanyshyn, the next step is to fully reverse commit bisect from kernel 3.13 to 3.14-rc4 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting. Thank you for your understanding. Helpful bug reporting tips: 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/1390802 Title: [HP Pavilion g6-1322sr Notebook PC] Ubuntu sometimes starts with display disabled Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu sometimes starting with display disabled on my HP g6-1322sr. It can be 3 times in row, or 10 times all will be ok. Sometimes after Ubuntu start, you can hear login screen sound, but display doesn't work. To make display work I switch to tty1 (display doesn't work too) and make ctrl+alt+del. Help! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ihor 2388 F pulseaudio /dev/snd/controlC0: ihor 2388 F pulseaudio CRDA: country UA: DFS-UNSET (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR Date: Sat Nov 8 22:43:47 2014 HibernationDevice: RESUME=UUID=77ad43ba-c7e9-4e4a-9057-d8a59af8c6c2 InstallationDate: Installed on 2014-11-04 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=1d31f24b-268d-48f1-a164-0c11a0caf414 ro quiet splash vt.handoff=7 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-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0695130046160:rvnHewlett-Packard:rn3566:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 0695130046160 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371591] Re: file not initialized to 0s under some conditions
We are on ESXi, version 5.5, according to our hosting provider. To run the test, I created a new, 40GB virtual disk. It's attached as SCSI ID 1:3, on a VMware Paravirtual SCSI adapter. I set it up as a PV and put ext4 on it the fast way, which is what I always do: 701 pvcreate /dev/sdd 702 vgextend mongo03-vg00 /dev/sdd 703 lvcreate -n test -l 100%PV mongo03-vg00 /dev/sdd 704 mount 705 mkfs.ext4 -E lazy_itable_init=1 -O uninit_bg /dev/mongo03-vg00/test Then I ran the test. Initially it passed, twice: /test/db.1 /test repro in db.1 creating f0 creating f1 touching files hexdump f0: 000 * ... But then, after doing some multitasking (we're working on an upgrade to MongoDB 2.6.5) and noticing that it was finished, I ran sync three times and checked the f0 files again: hexdump db.1/f0 000 * 0001000 * 0007000 * 100 * hexdump db.10/f0 000 * 100 * hexdump db.2/f0 000 * 0001000 * 0007000 * 100 * hexdump db.3/f0 000 * 0001000 * 0007000 * 100 * hexdump db.4/f0 000 * 0001000 * 0007000 * 100 * hexdump db.5/f0 000 * 100 * hexdump db.6/f0 000 * 100 * hexdump db.7/f0 000 * 100 * hexdump db.8/f0 000 * 100 * hexdump db.9/f0 000 * 100 * -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions Status in “linux” package in Ubuntu: Fix Released Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: SRU Justification: [Impact] Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. [Test Case] I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. [Fix] mptfusion: enable no_write_same in scsi_host_template commit 4089b71cc820a426d601283c92fcd4ffeb5139c2 upstream https://lkml.org/lkml/2014/9/25/482 (Note this patch may be reverted in the future as there is active
[Kernel-packages] [Bug 1391953] [NEW] [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest
You have been subscribed to a public bug: ---Problem Description--- We need below patches to support Ubunut 14.04.02 on PowerKVM host / guest. PowerKVM host : 831cf65b0295de75f40f8cf52ce62e5d261dab4f powerpc/powernv: Check OPAL dump calls exist before using 7dc992ec7b3fd875b05f49f454a922ee94af330b powerpc/powernv: Check OPAL elog calls exist before using 035ed26fb090ff3277900259f19d57e54da2e116 powerpc/powernv: Check OPAL RTC calls exists before using bffe6bda342578deea0b74f2d9cb97cc40585a1b powerpc/powernv: Add OPAL check token call cdd91b89adedb77e3e581c40788620790edc33b5 powerpc/powernv: Improve error messages in dump code 76215b04fd297c008b91ece732ed36e67e0181fa arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files 6656c21ca10e54a84673d0ec2f0cf5f676e66a40 arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs files Guest; e36d1227776a2daa2c9aa7f997ac7083d6783f2c pseries: Fix endian issues in cpu hot-removal 822e71224e07f07a07c385be869fe416ce436430 pseries: Fix endian issues in onlining cpu threads c9ac408bc7329911237c25508f578fb2fa1c4235 powerpc/pseries: Fix endian issues in memory hotplug 587870e8650a0571e895cc879cd895c78c6391bf powerpc/pseries/hvcserver: Fix endian issue in hvcs_get_partner_info d6f1e7abdb95a7ea031e7604829e4b5514d7e2c1 powerpc/pseries: Make CPU hotplug path endian safe PowerVM: PowerVM patch : 408cddd96e3b155337f9e3aba2198e92e94c6068 powerpc/fadump: Fix endianess issues in firmware assisted dump handling Note that these are the required patches on top of Ubuntu 14.10 kernel and list commit ID is from upstream.. -Vasant ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-118797 severity-high targetmilestone-inin14042 -- [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest https://bugs.launchpad.net/bugs/1391953 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391953] Re: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest
Set package to linux for kernel component ** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391953 Title: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest Status in “linux” package in Ubuntu: New Bug description: ---Problem Description--- We need below patches to support Ubunut 14.04.02 on PowerKVM host / guest. PowerKVM host : 831cf65b0295de75f40f8cf52ce62e5d261dab4f powerpc/powernv: Check OPAL dump calls exist before using 7dc992ec7b3fd875b05f49f454a922ee94af330b powerpc/powernv: Check OPAL elog calls exist before using 035ed26fb090ff3277900259f19d57e54da2e116 powerpc/powernv: Check OPAL RTC calls exists before using bffe6bda342578deea0b74f2d9cb97cc40585a1b powerpc/powernv: Add OPAL check token call cdd91b89adedb77e3e581c40788620790edc33b5 powerpc/powernv: Improve error messages in dump code 76215b04fd297c008b91ece732ed36e67e0181fa arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files 6656c21ca10e54a84673d0ec2f0cf5f676e66a40 arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs files Guest; e36d1227776a2daa2c9aa7f997ac7083d6783f2c pseries: Fix endian issues in cpu hot-removal 822e71224e07f07a07c385be869fe416ce436430 pseries: Fix endian issues in onlining cpu threads c9ac408bc7329911237c25508f578fb2fa1c4235 powerpc/pseries: Fix endian issues in memory hotplug 587870e8650a0571e895cc879cd895c78c6391bf powerpc/pseries/hvcserver: Fix endian issue in hvcs_get_partner_info d6f1e7abdb95a7ea031e7604829e4b5514d7e2c1 powerpc/pseries: Make CPU hotplug path endian safe PowerVM: PowerVM patch : 408cddd96e3b155337f9e3aba2198e92e94c6068 powerpc/fadump: Fix endianess issues in firmware assisted dump handling Note that these are the required patches on top of Ubuntu 14.10 kernel and list commit ID is from upstream.. -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391953] Re: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391953 Title: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest Status in “linux” package in Ubuntu: New Bug description: ---Problem Description--- We need below patches to support Ubunut 14.04.02 on PowerKVM host / guest. PowerKVM host : 831cf65b0295de75f40f8cf52ce62e5d261dab4f powerpc/powernv: Check OPAL dump calls exist before using 7dc992ec7b3fd875b05f49f454a922ee94af330b powerpc/powernv: Check OPAL elog calls exist before using 035ed26fb090ff3277900259f19d57e54da2e116 powerpc/powernv: Check OPAL RTC calls exists before using bffe6bda342578deea0b74f2d9cb97cc40585a1b powerpc/powernv: Add OPAL check token call cdd91b89adedb77e3e581c40788620790edc33b5 powerpc/powernv: Improve error messages in dump code 76215b04fd297c008b91ece732ed36e67e0181fa arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files 6656c21ca10e54a84673d0ec2f0cf5f676e66a40 arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs files Guest; e36d1227776a2daa2c9aa7f997ac7083d6783f2c pseries: Fix endian issues in cpu hot-removal 822e71224e07f07a07c385be869fe416ce436430 pseries: Fix endian issues in onlining cpu threads c9ac408bc7329911237c25508f578fb2fa1c4235 powerpc/pseries: Fix endian issues in memory hotplug 587870e8650a0571e895cc879cd895c78c6391bf powerpc/pseries/hvcserver: Fix endian issue in hvcs_get_partner_info d6f1e7abdb95a7ea031e7604829e4b5514d7e2c1 powerpc/pseries: Make CPU hotplug path endian safe PowerVM: PowerVM patch : 408cddd96e3b155337f9e3aba2198e92e94c6068 powerpc/fadump: Fix endianess issues in firmware assisted dump handling Note that these are the required patches on top of Ubuntu 14.10 kernel and list commit ID is from upstream.. -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391339] Re: Trusty kernel inbound network performance regression when GRO is enabled
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1391339
Title:
Trusty kernel inbound network performance regression when GRO is
enabled
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading our EC2 instances from Lucid to Trusty we noticed an
increase on download times, Lucid instances were able to download
twice as fast as Trusty. After some investigation and testing older
kernels (precise, raring and saucy) we confirmed that this only
happens on trusty kernel or newer since utopic kernel shows the same
result and disabling gro with `ethtool -K eth0 gro off` seems to fix
the problem making download speed the same as the Lucid instances
again.
The problem is easily reproducible using Apache Bench a couple times
on files bigger than 100MB on 1Gb network (EC2) using HTTP or HTTPS.
Following is an example of download throughput with and without gro:
root@runtime-common.22 ~# ethtool -K eth0 gro off
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 85183.40 [Kbytes/sec] received
Transfer rate: 86375.80 [Kbytes/sec] received
Transfer rate: 94720.24 [Kbytes/sec] received
Transfer rate: 84783.82 [Kbytes/sec] received
Transfer rate: 84933.09 [Kbytes/sec] received
Transfer rate: 84714.04 [Kbytes/sec] received
Transfer rate: 84795.58 [Kbytes/sec] received
Transfer rate: 84636.54 [Kbytes/sec] received
Transfer rate: 84924.26 [Kbytes/sec] received
Transfer rate: 84994.10 [Kbytes/sec] received
root@runtime-common.22 ~# ethtool -K eth0 gro on
root@runtime-common.22 ~# for i in {1..10}; do ab -n 10 $URL | grep Transfer
rate; done
Transfer rate: 74193.53 [Kbytes/sec] received
Transfer rate: 56808.91 [Kbytes/sec] received
Transfer rate: 56011.58 [Kbytes/sec] received
Transfer rate: 82227.74 [Kbytes/sec] received
Transfer rate: 70806.54 [Kbytes/sec] received
Transfer rate: 72848.10 [Kbytes/sec] received
Transfer rate: 58451.94 [Kbytes/sec] received
Transfer rate: 61221.33 [Kbytes/sec] received
Transfer rate: 58620.21 [Kbytes/sec] received
Transfer rate: 69950.03 [Kbytes/sec] received
root@runtime-common.22 ~#
Similar results can be observed using iperf and netperf as well.
Tested kernels:
Not affected: 3.8.0-44-generic (precise/raring), 3.11.0-26-generic (saucy)
Affected: 3.13.0-39-generic (trusty), 3.16.0-24-generic (utopic)
Let me know if I can provide any other information that might be helpful like
perf traces and reports.
Rodrigo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391339/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391476 Title: [MacBookPro11,1] Laptop wakes up while lid closed Status in “linux” package in Ubuntu: Incomplete Bug description: Same behavior when using pm-suspend. This bug may be CRITICAL, because it is hard to notice whether the laptop waking up, especially because that does not always happen immediately. Getting to sleep takes up to 30 seconds. Hardware damage may be a result of waking up while lid is closed, for example if laptop is transported in a bag. I suspect that the problem comes from the Intel video driver. See extract from kern.log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stephan2266 F pulseaudio /dev/snd/controlC1: stephan2266 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 11 12:11:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (33 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 003: ID 05ac:0259 Apple, Inc. Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago) WifiSyslog: dmi.bios.date: 02/12/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B07.1402121134 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: stephan2266 F...m pulseaudio /dev/snd/controlC0: stephan2266 F pulseaudio /dev/snd/controlC1: stephan2266 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (34 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Tags: utopic Uname: Linux 3.16.0-24-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B07.1402121134 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias:
[Kernel-packages] [Bug 1381005] Re: Long stdin from terminal can result in code execution
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-da-key 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/1381005 Title: Long stdin from terminal can result in code execution Status in “linux” package in Ubuntu: Incomplete Bug description: Under certain conditions, the input entered from a terminal with a foreground process waiting for stdin, can be interpreted and executed by the shell. Steps to reproduce: 1) Open a terminal 2) Run a simple program that waits for stdin (like cat, tee, head, tail, ...) or even the bash-builtin command read. No need to specify arguments 3) Type or paste exactly 4096 ASCII characters into the terminal (see sample attachment) 4) Press Enter What should happen: The program in foreground reads 4097 characters (the last one is new line). What actually happens: Instead of reading the input, the current program exits (read() only reads one character before EOF) and the shell executes the same input starting from the second character. I believe that the issue can be reproduced with: - any terminal (tested on xterm, gnome-terminal, tty) - any shell (tested on bash, zsh) - any program that reads stdin from terminal (not attached to a pipe) Debugging the shell with gdb suggests that the bug is in the implementation of read(), hence libc6 or under (kernel). Specifically, the bug is caused by read() reading only one character (new line) when entering a text of 4096 characters in stdin on the terminal. It looks like read() is then closing the stdin descriptor. If the input is 4097 characters long, read() will read two characters and the shell will interpret from the 3rd character, and so on. Verified on: Ubuntu 14.04.1 LTS Kernel: 3.13.0-24-generic x86_64 3.13.0-32-generic x86_64 3.13.0-36-generic x86_64 libc6: 2.19-0ubuntu6 2.19-0ubuntu6.1 2.19-0ubuntu6.3 I'm happy to provide more information if it helps. Angelo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391605] Re: [Acer Aspire 5734Z] Kernel crash
*** This bug is a duplicate of bug 1384342 *** https://bugs.launchpad.net/bugs/1384342 ** This bug has been marked a duplicate of bug 1384342 kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391605 Title: [Acer Aspire 5734Z] Kernel crash Status in “linux” package in Ubuntu: Incomplete Bug description: Crash while navigating. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1960 F pulseaudio Date: Tue Nov 11 15:43:53 2014 HibernationDevice: RESUME=UUID=c2c957db-7bbd-4a85-a6a4-ba08641bae27 InstallationDate: Installed on 2014-05-03 (192 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Acer Aspire 5734Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=93da5e1e-271e-424a-9e7e-185097bd72e4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5734Z dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnAcer:bvrV1.06:bd04/25/2011:svnAcer:pnAspire5734Z:pvrV1.06:rvnAcer:rnAspire5734Z:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.name: Aspire 5734Z dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
Added System76 as I started getting this on my Galago UltraPro after upgrading to 14.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in System76: New Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0 [82218.556280] [81094a10] ?
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@jondee, right. No need to create a new upstream bug. 64431 is already open. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in System76: New Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0 [82218.556280] [81094a10] ?
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
** Also affects: system76 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/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in System76: New Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0 [82218.556280] [81094a10] ?
[Kernel-packages] [Bug 1388415] Re: jstest-gtk doesn't detect my joystick
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1388415 Title: jstest-gtk doesn't detect my joystick Status in “linux” package in Ubuntu: Incomplete Bug description: I installed the program, plugged in my joystick, and started the program. No Joystick is listed by program. So I hit refresh and preferences. Nothing happens. So I close and look for updates. i find none. Please fix this bug in ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: jstest-gtk 0.1.1~git20140501-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 12:35:10 2014 ExecutablePath: /usr/bin/jstest-gtk InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: jstest-gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384539] Re: CVE-2014-3610
** Description changed: - If the guest writes a noncanonical value to certain MSR registers, KVM - will write that value to the MSR in the host context and a #GP will be - raised leading to kernel panic. A privileged guest user can use this - flaw to crash the host. Enabling CONFIG_PARAVIRT when building the - kernel mitigates this issue because wrmsrl() ends up invoking safe msr - write variant. + The WRMSR processing functionality in the KVM subsystem in the Linux + kernel through 3.17.2 does not properly handle the writing of a non- + canonical address to a model-specific register, which allows guest OS + users to cause a denial of service (host OS crash) by leveraging guest + OS privileges, related to the wrmsr_interception function in + arch/x86/kvm/svm.c and the handle_wrmsr function in arch/x86/kvm/vmx.c. + A privileged guest user can use this flaw to crash the host. Enabling + CONFIG_PARAVIRT when building the kernel mitigates this issue because + wrmsrl() ends up invoking safe msr write variant. Break-Fix: - 854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 -- 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/1384539 Title: CVE-2014-3610 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New 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-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid 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-fsl-imx51” source package in Vivid: Invalid Status in “linux-lts-backport-maverick”
[Kernel-packages] [Bug 1391908] Re: ASUS X551MA: Ubuntu 14.04 freezes from time to time
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = High ** 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/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: Incomplete Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox or Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA 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/1391908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Re: Resume failes when on AC power
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1391892 Title: Resume failes when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391732] Re: Ubuntu 14.4 problem
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1391732 Title: Ubuntu 14.4 problem Status in “linux” package in Ubuntu: Incomplete Bug description: My touchpad is not working ever since I installed ubuntu 14.4 . However connecting mouse works. On running the command cat /proc/bus/input/devices , touchpad is not shown up too. I am using Dell Inpiron 3521 model. Synaptics touchpad Touchpad not working ever since I installed ubuntu 14.4 . Please help me. I am attaching the required files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391700] Re: package linux-image-3.13.0-39-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
non-PAE CPUs are not supported after Precise. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid ** Changed in: linux (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391700 Title: package linux-image-3.13.0-39-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “linux” package in Ubuntu: Invalid Bug description: Happened during a software update on a pentium M machine. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 Date: Tue Nov 11 19:41:51 2014 DuplicateSignature: package:linux-image-3.13.0-39-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-22 (50 days ago) InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=65ffe6fd-df15-4b11-9220-47795abf6a04 ro quiet splash vt.handoff=7 SourcePackage: linux Title: package linux-image-3.13.0-39-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384545] Re: CVE-2014-3647
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - kvm currently mishandles noncanonical addresses when emulating - instructions that change rip (eg branches, calls), potentially causing a - failed VM-entry. A guest user with access to I/O or MMIO region can use - this flaw to crash the guest. + arch/x86/kvm/emulate.c in the KVM subsystem in the Linux kernel through + 3.17.2 does not properly perform RIP changes, which allows guest OS + users to cause a denial of service (guest OS crash) via a crafted + application. A guest user with access to I/O or MMIO region can use this + flaw to crash the guest. Break-Fix: - 234f3ce485d54017f15cf5e0699cff4100121601 Break-Fix: - d1442d85cc30ea75f7d399474ca738e0bc96f715 -- 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/1384545 Title: CVE-2014-3647 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Invalid Status in “linux-lts-backport-natty” source package in Utopic: Invalid Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid 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-fsl-imx51” source package in Vivid: Invalid Status in “linux-lts-backport-maverick” source package in Vivid: Invalid Status in “linux-lts-backport-natty” source package in
[Kernel-packages] [Bug 1384544] Re: CVE-2014-3646
** Description changed: - IA32_VMX_EPT_VPID_CAP MSR is set) guest invocation of invvpid causes vm - exit, which is currently not handled and causes unknown exit error to be - propagated to userspace. A local unprivileged guest user could use this + arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel through + 3.17.2 does not have an exit handler for the INVVPID instruction, which + allows guest OS users to cause a denial of service (guest OS crash) via + a crafted application. A local unprivileged guest user could use this flaw to crash the guest. Break-Fix: - a642fc305053cc1c6e47e4f4df327895747ab485 -- 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/1384544 Title: CVE-2014-3646 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New 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-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid 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-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description:
[Kernel-packages] [Bug 1384540] Re: CVE-2014-3611
** Description changed: - There's a race condition in the PIT emulation code in KVM. In - __kvm_migrate_pit_timer the pit_timer object is accessed without - synchronization. A local guest user with access to the PIT i/o ports - could use this flaw to crash the host. + Race condition in the __kvm_migrate_pit_timer function in + arch/x86/kvm/i8254.c in the KVM subsystem in the Linux kernel through + 3.17.2 allows guest OS users to cause a denial of service (host OS + crash) by leveraging incorrect PIT emulation. A local guest user with + access to the PIT i/o ports could use this flaw to crash the host. Break-Fix: - 2febc839133280d5a5e8e1179c94ea674489dae2 -- 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/1384540 Title: CVE-2014-3611 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New 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-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid 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-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid:
[Kernel-packages] [Bug 1386392] Re: CVE-2014-3687
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - net: sctp: fix panic on duplicate ASCONF chunks + The sctp_assoc_lookup_asconf_ack function in net/sctp/associola.c in the + SCTP implementation in the Linux kernel through 3.17.2 allows remote + attackers to cause a denial of service (panic) via duplicate ASCONF + chunks that trigger an incorrect uncork within the side-effect + interpreter. Break-Fix: 2e3216cd54b142ba605e87522e15f42e0c4e3996 b69040d8e39f20d5215a03502a8e8b4c6ab78395 -- 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/1386392 Title: CVE-2014-3687 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1386367] Re: CVE-2014-3673
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - sctp: skb_over_panic when receiving malformed ASCONF chunks + The SCTP implementation in the Linux kernel through 3.17.2 allows remote + attackers to cause a denial of service (system crash) via a malformed + ASCONF chunk, related to net/sctp/sm_make_chunk.c and + net/sctp/sm_statefuns.c. Break-Fix: - 9de7922bc709eee2f609cd01d98aaedc4cf5ea74 -- 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/1386367 Title: CVE-2014-3673 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: The SCTP implementation in the
[Kernel-packages] [Bug 1386393] Re: CVE-2014-3688
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed -- 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/1386393 Title: CVE-2014-3688 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: net: sctp: remote memory pressure from excessive queueing Break-Fix: 2e3216cd54b142ba605e87522e15f42e0c4e3996 26b87c7881006311828bb0ab271a551a62dcceb4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1388970] Re: CVE-2014-3690
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - x86,kvm,vmx: Preserve CR4 across VM entry + arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before + 3.17.2 on Intel processors does not ensure that the value in the CR4 + control register remains the same after a VM entry, which allows host OS + users to kill arbitrary processes or cause a denial of service (system + disruption) by leveraging /dev/kvm access, as demonstrated by PR_SET_TSC + prctl calls within a modified copy of QEMU. Break-Fix: - d974baa398f34393db76be45f7d4d04fbdbb4a0a -- 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/1388970 Title: CVE-2014-3690 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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:
[Kernel-packages] [Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
Updated a 12.04 LTS box today with the kernel 3.13.0-39-generic #66~precise1-Ubuntu SMP Wed Oct 29 09:56:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux and problem still there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275] [8171ed09] dump_stack+0x45/0x56 [368973.448279] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.448283] [810677ac] warn_slowpath_fmt+0x4c/0x50
[Kernel-packages] [Bug 1383356] Re: CVE-2014-7970
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- 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/1383356 Title: CVE-2014-7970 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: The pivot_root implementation in fs/namespace.c in the Linux kernel through 3.17 does not properly interact with certain locations of a chroot directory, which allows local users to cause a denial of service (mount-tree loop) via . (dot) values in both arguments to the pivot_root system call. Break-Fix: - 0d0826019e529f21c84687521d03f60cd241ca7d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383356/+subscriptions --
[Kernel-packages] [Bug 1391892] Re: Resume failes when on AC power
** Tags added: latest-bios-76cn38ww ** Attachment removed: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+attachment/4259083/+files/lspci-vnvn.log ** Summary changed: - Resume failes when on AC power + [Lenovo Yoga 2 Pro] Resume fails when on AC power -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391892 Title: [Lenovo Yoga 2 Pro] Resume fails when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391953] Re: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest
** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391953 Title: [Ubuntu 14.04.02] Kernel patches for PowerKVM host and guest Status in “linux” package in Ubuntu: Triaged Bug description: ---Problem Description--- We need below patches to support Ubunut 14.04.02 on PowerKVM host / guest. PowerKVM host : 831cf65b0295de75f40f8cf52ce62e5d261dab4f powerpc/powernv: Check OPAL dump calls exist before using 7dc992ec7b3fd875b05f49f454a922ee94af330b powerpc/powernv: Check OPAL elog calls exist before using 035ed26fb090ff3277900259f19d57e54da2e116 powerpc/powernv: Check OPAL RTC calls exists before using bffe6bda342578deea0b74f2d9cb97cc40585a1b powerpc/powernv: Add OPAL check token call cdd91b89adedb77e3e581c40788620790edc33b5 powerpc/powernv: Improve error messages in dump code 76215b04fd297c008b91ece732ed36e67e0181fa arch/powerpc/platforms/powernv/opal-dump.c: fix world-writable sysfs files 6656c21ca10e54a84673d0ec2f0cf5f676e66a40 arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs files Guest; e36d1227776a2daa2c9aa7f997ac7083d6783f2c pseries: Fix endian issues in cpu hot-removal 822e71224e07f07a07c385be869fe416ce436430 pseries: Fix endian issues in onlining cpu threads c9ac408bc7329911237c25508f578fb2fa1c4235 powerpc/pseries: Fix endian issues in memory hotplug 587870e8650a0571e895cc879cd895c78c6391bf powerpc/pseries/hvcserver: Fix endian issue in hvcs_get_partner_info d6f1e7abdb95a7ea031e7604829e4b5514d7e2c1 powerpc/pseries: Make CPU hotplug path endian safe PowerVM: PowerVM patch : 408cddd96e3b155337f9e3aba2198e92e94c6068 powerpc/fadump: Fix endianess issues in firmware assisted dump handling Note that these are the required patches on top of Ubuntu 14.10 kernel and list commit ID is from upstream.. -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388974] Re: CVE-2014-7207
** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - Network-related panic + A certain Debian patch to the IPv6 implementation in the Linux kernel + 3.2.x through 3.2.63 does not properly validate arguments in + ipv6_select_ident function calls, which allows local users to cause a + denial of service (NULL pointer dereference and system crash) by + leveraging (1) tun or (2) macvtap device access. Break-Fix: 73f156a6e8c1074ac6327e0abd1169e95eb66463 916e4cf46d0204806c062c8c6c4d1f633852c5b6 -- 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/1388974 Title: CVE-2014-7207 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-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New 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-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid 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-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: A certain Debian patch to the IPv6 implementation in the Linux kernel 3.2.x through 3.2.63 does not properly
[Kernel-packages] [Bug 1391908] Re: ASUS X551MA: Ubuntu 14.04 freezes from time to time
** Tags added: bios-outdated-513 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: Incomplete Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox or Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA 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/1391908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391908] Re: ASUS X551MA: Ubuntu 14.04 freezes from time to time
Joseph Salisbury (jsalisbury) This is my new computer and I didn't use previous version of Ubuntu on it. I also tried Linux Mint 17 during about a week before, it had the same problem. I'll try to test the latest upstream kernel. After that I'll inform here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391908 Title: ASUS X551MA: Ubuntu 14.04 freezes from time to time Status in “linux” package in Ubuntu: Incomplete Bug description: From time to time without an obvious reason the whole system freezes (Ubuntu 14.04 on ASUS X551MA) . A mouse indicator also don't respond. Always it was when I was using Internet via Chrome or Firefox or Transmission. Of course, maybe it was a mere coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yustnip1798 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 17:33:58 2014 HibernationDevice: RESUME=UUID=bb47884b-e476-470a-8454-5700c6a44ad6 InstallationDate: Installed on 2014-11-05 (7 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 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=19058e17-58c8-4adc-824f-eb3c4ed453cc ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA 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/1391908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383358] Re: CVE-2014-7975
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New = Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed -- 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/1383358 Title: CVE-2014-7975 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: The do_umount function in fs/namespace.c in the Linux kernel through 3.17 does not require the CAP_SYS_ADMIN capability for do_remount_sb calls that change the root filesystem to read-only, which allows local users to cause a denial of service (loss of writability) by
[Kernel-packages] [Bug 1386395] Re: CVE-2014-8369
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Description changed: - Linux kernel iommu.c excessive unpinning + The kvm_iommu_map_pages function in virt/kvm/iommu.c in the Linux kernel + through 3.17.2 miscalculates the number of pages during the handling of + a mapping failure, which allows guest OS users to cause a denial of + service (host OS page unpinning) or possibly have unspecified other + impact by leveraging guest OS privileges. NOTE: this vulnerability + exists because of an incorrect fix for CVE-2014-3601. Break-Fix: 350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 3d32e4dbe71374a6780eaf51d719d76f9a9bf22f -- 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/1386395 Title: CVE-2014-8369 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: Fix Committed Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in
[Kernel-packages] [Bug 1388975] Re: CVE-2014-8559
** Description changed: - [fs/dcache.c incorrect use of rename_lock] + The d_walk function in fs/dcache.c in the Linux kernel through 3.17.2 + does not properly maintain the semantics of rename_lock, which allows + local users to cause a denial of service (deadlock and system hang) via + a crafted application. -- 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/1388975 Title: CVE-2014-8559 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: New Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Status in “linux” source package in Vivid: New Status in “linux-armadaxp” source package in Vivid: Invalid Status in “linux-ec2” source package in Vivid: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” source package in Vivid: Invalid Status in “linux-ti-omap4” source package in Vivid: Invalid Bug description: The d_walk function in fs/dcache.c in the Linux kernel through 3.17.2 does not properly maintain the semantics of rename_lock, which allows local users to cause a denial of service (deadlock and system hang) via a crafted application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388975/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1392006] [NEW] CVE-2014-7825
*** This bug is a security vulnerability *** Public security bug reported: kernel/trace/trace_syscalls.c in the Linux kernel through 3.17.2 does not properly handle private syscall numbers during use of the perf subsystem, which allows local users to cause a denial of service (out- of-bounds read and OOPS) or bypass the ASLR protection mechanism via a crafted application. Break-Fix: - 086ba77a6db00ed858ff07451bedee197df868c9 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance:
[Kernel-packages] [Bug 1392006] Re: CVE-2014-7825
CVE-2014-7825 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in:
[Kernel-packages] [Bug 1392008] [NEW] CVE-2014-7826
*** This bug is a security vulnerability *** Public security bug reported: kernel/trace/trace_syscalls.c in the Linux kernel through 3.17.2 does not properly handle private syscall numbers during use of the ftrace subsystem, which allows local users to gain privileges or cause a denial of service (invalid pointer dereference) via a crafted application. Break-Fix: - 086ba77a6db00ed858ff07451bedee197df868c9 ** Affects: linux (Ubuntu) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: High Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: High Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: High Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: High Status: New ** Affects: linux (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Utopic) Importance: High
[Kernel-packages] [Bug 1392008] Re: CVE-2014-7826
CVE-2014-7826 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in:
[Kernel-packages] [Bug 1392013] [NEW] CVE-2014-8709
*** This bug is a security vulnerability *** Public security bug reported: The ieee80211_fragment function in net/mac80211/tx.c in the Linux kernel before 3.13.5 does not properly maintain a certain tail pointer, which allows remote attackers to obtain sensitive cleartext information by reading packets. Break-Fix: 2de8e0d999b8790861cd3749bec2236ccc1c8110 338f977f4eb441e69bb9a46eaa0ac715c931a67f ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New **
[Kernel-packages] [Bug 1391892] Re: [Lenovo Yoga 2 Pro] Resume fails when on AC power
kernel-fixed-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/1391892 Title: [Lenovo Yoga 2 Pro] Resume fails when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391892] Re: [Lenovo Yoga 2 Pro] Resume fails when on AC power
I installed the latest upstream kernel and I am no longer having the suspend/resume lockup issue. It looks like it is fixed in the upstream kernels. Thank you for your help on this. ** Tags added: kernel-fixed-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/1391892 Title: [Lenovo Yoga 2 Pro] Resume fails when on AC power Status in “linux” package in Ubuntu: Incomplete Bug description: laptop: yoga pro 2 running Ubuntu 14.10, also happened on 14.04 - all 64 bit Laptop fails to resume after being suspended only when on AC power. When on batter power suspend/resume works fine. When on AC after resume you can move the mouse and see you desktop but nothing is clickable. Only way I have been able to get around this is to switch to a different terminal and reboot the machine. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2282 F pulseaudio /dev/snd/controlC0: tim2282 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c87c2b51-fe80-4cca-bf24-1c912f311424 InstallationDate: Installed on 2014-10-23 (19 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20266 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=d55eb63e-9815-4f4f-9b59-7bf5a52ab545 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 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-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 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 Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392013] Re: CVE-2014-8709
CVE-2014-8709 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in:
[Kernel-packages] [Bug 1392016] [NEW] [Asus UL30VT] Backlight control does not work
Public bug reported: The backlight control on my Asus UL30VT has not worked for quite a while. It just to work, a few ubuntu versions ago. The backlight control bubble does show up when the function keys on the laptop are pressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lina 2081 F pulseaudio /dev/snd/controlC0: lina 2081 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 20:20:31 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c8002bb0-2b05-4952-bc8b-bfcd29ac6117 InstallationDate: Installed on 2013-02-26 (623 days ago) InstallationMedia: This MachineType: ASUSTeK Computer Inc. UL30VT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=ff44dc17-e11a-4d44-8ab6-bf188f64ed83 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-20 (115 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT 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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1392016 Title: [Asus UL30VT] Backlight control does not work Status in “linux” package in Ubuntu: Confirmed Bug description: The backlight control on my Asus UL30VT has not worked for quite a while. It just to work, a few ubuntu versions ago. The backlight control bubble does show up when the function keys on the laptop are pressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lina 2081 F pulseaudio /dev/snd/controlC0: lina 2081 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 20:20:31 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c8002bb0-2b05-4952-bc8b-bfcd29ac6117 InstallationDate: Installed on 2013-02-26 (623 days ago) InstallationMedia: This MachineType: ASUSTeK Computer Inc. UL30VT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=ff44dc17-e11a-4d44-8ab6-bf188f64ed83 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-20 (115 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT 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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT 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/1392016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392016] 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/1392016 Title: [Asus UL30VT] Backlight control does not work Status in “linux” package in Ubuntu: Confirmed Bug description: The backlight control on my Asus UL30VT has not worked for quite a while. It just to work, a few ubuntu versions ago. The backlight control bubble does show up when the function keys on the laptop are pressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lina 2081 F pulseaudio /dev/snd/controlC0: lina 2081 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 20:20:31 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c8002bb0-2b05-4952-bc8b-bfcd29ac6117 InstallationDate: Installed on 2013-02-26 (623 days ago) InstallationMedia: This MachineType: ASUSTeK Computer Inc. UL30VT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=ff44dc17-e11a-4d44-8ab6-bf188f64ed83 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-20 (115 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT 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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT 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/1392016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392016] Re: [Asus UL30VT] Backlight control does not work
** Attachment added: ssdt1.dat https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392016/+attachment/4259275/+files/ssdt1.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1392016 Title: [Asus UL30VT] Backlight control does not work Status in “linux” package in Ubuntu: Confirmed Bug description: The backlight control on my Asus UL30VT has not worked for quite a while. It just to work, a few ubuntu versions ago. The backlight control bubble does show up when the function keys on the laptop are pressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lina 2081 F pulseaudio /dev/snd/controlC0: lina 2081 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 20:20:31 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c8002bb0-2b05-4952-bc8b-bfcd29ac6117 InstallationDate: Installed on 2013-02-26 (623 days ago) InstallationMedia: This MachineType: ASUSTeK Computer Inc. UL30VT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=ff44dc17-e11a-4d44-8ab6-bf188f64ed83 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-20 (115 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT 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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT 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/1392016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392016] Re: [Asus UL30VT] Backlight control does not work
** Attachment added: dsdt.dat https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392016/+attachment/4259274/+files/dsdt.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1392016 Title: [Asus UL30VT] Backlight control does not work Status in “linux” package in Ubuntu: Confirmed Bug description: The backlight control on my Asus UL30VT has not worked for quite a while. It just to work, a few ubuntu versions ago. The backlight control bubble does show up when the function keys on the laptop are pressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lina 2081 F pulseaudio /dev/snd/controlC0: lina 2081 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 12 20:20:31 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c8002bb0-2b05-4952-bc8b-bfcd29ac6117 InstallationDate: Installed on 2013-02-26 (623 days ago) InstallationMedia: This MachineType: ASUSTeK Computer Inc. UL30VT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=ff44dc17-e11a-4d44-8ab6-bf188f64ed83 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-20 (115 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30VT 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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30VT 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/1392016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
