[Kernel-packages] [Bug 1265544] Re: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7
Ok, I will send it on my next reboot.
For information, I was unable to suspend the laptop because it was awakening
some seconds later.
I made it working by using the following script (/etc/pm/sleep.d/20_zenbook) :
case ${1} in
hibernate|suspend)
# Unbind ehci_hcd for first device :00:14.0:
echo -n :00:14.0 | tee /sys/bus/pci/drivers/xhci_hcd/unbind
;;
resume|thaw)
# Bind ehci_hcd for first device :00:14.0:
echo -n :00:14.0 | tee /sys/bus/pci/drivers/xhci_hcd/bind
;;
esac
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG] black screen on boot 3.12.0-7
Status in The Linux Kernel:
Incomplete
Status in “linux” package in Ubuntu:
Triaged
Bug description:
Same description/workaround as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015
I tried both Enable CSM and non-CSM boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.12.0-7-generic 3.12.0-7.15
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
Date: Thu Jan 2 09:59:33 2014
HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6
InstallationDate: Installed on 2013-12-31 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 03eb:8a03 Atmel Corp.
Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX302LG
ProcFB: 0 simple
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
RelatedPackageVersions:
linux-restricted-modules-3.12.0-7-generic N/A
linux-backports-modules-3.12.0-7-generic N/A
linux-firmware1.117
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX302LG.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX302LG
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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX302LG
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1265544/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
Mailed linux-in...@vger.kernel.org with requested info. Re a url I cannot see it when I search http://www.spinics.net/lists /linux-input/ for Novatech touchpad but I suppose it takes a while to be put in 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/1244643 Title: [Novatech N1402 NNB-978] Touchpad does not work at all Status in “linux” package in Ubuntu: Triaged Bug description: WORKAROUND: Kernel parameter: i8042.noloop When producing this bug report I got: ubuntu@ubuntu:~$ ubuntu-bug linux ubuntu@ubuntu:~$ (process:4162): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2918 F pulseaudio CasperVersion: 1.336ubuntu1 Date: Fri Oct 25 12:32:01 2013 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 869243] Re: CVE-2011-2496
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/869243 Title: CVE-2011-2496 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in
[Kernel-packages] [Bug 1273587] [NEW] [Acer TravelMate 8572G] suspend/resume failure [non-free: wl]
Public bug reported: After start sytem ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mateusz2242 F pulseaudio Date: Tue Jan 28 09:43:59 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3e66ed3c-3b7c-43d9-a54e-389f1ec48223 InstallationDate: Installed on 2014-01-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) InterpreterPath: /usr/bin/python3.3 MachineType: Acer TravelMate 8572G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=04737bcf-4bff-4754-966c-3b1c85935572 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/20/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.28 dmi.board.name: BAP50-CP dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 8572G dmi.product.version: Not Applicable dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend 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/1273587 Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: After start sytem ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mateusz2242 F pulseaudio Date: Tue Jan 28 09:43:59 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3e66ed3c-3b7c-43d9-a54e-389f1ec48223 InstallationDate: Installed on 2014-01-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) InterpreterPath: /usr/bin/python3.3 MachineType: Acer TravelMate 8572G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=04737bcf-4bff-4754-966c-3b1c85935572 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/20/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.28 dmi.board.name: BAP50-CP dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 8572G dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1273587] 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/1273587 Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Confirmed Bug description: After start sytem ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mateusz2242 F pulseaudio Date: Tue Jan 28 09:43:59 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3e66ed3c-3b7c-43d9-a54e-389f1ec48223 InstallationDate: Installed on 2014-01-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) InterpreterPath: /usr/bin/python3.3 MachineType: Acer TravelMate 8572G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=04737bcf-4bff-4754-966c-3b1c85935572 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/20/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.28 dmi.board.name: BAP50-CP dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 8572G dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267489] Re: linux-ti-omap4: 3.5.0-238.54 -proposed tracker
Copied to -proposed and overrides adjusted. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1267489 Title: linux-ti-omap4: 3.5.0-238.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-ti-omap4” source package in Raring: New Status in “linux-ti-omap4” source package in Saucy: New Bug description: This bug is for tracking the version to be filled 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:Thursday, 09. January 2014 14:38 UTC kernel-stable-master-bug:1266857 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267490] Re: linux-armadaxp: 3.5.0-1627.36 -proposed tracker
Copied to -proposed and overrides adjusted. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- 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/1267490 Title: linux-armadaxp: 3.5.0-1627.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Quantal: In Progress Bug description: This bug is for tracking the 3.5.0-1627.36 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:Thursday, 09. January 2014 14:40 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 07:02 UTC kernel-stable-Security-signoff-end:Friday, 10. January 2014 07:03 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-start:Monday, 13. January 2014 04:04 UTC kernel-stable-phase-changed:Monday, 13. January 2014 04:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266525] Re: linux: 2.6.32-56.118 -proposed tracker
** Description changed: This bug is for tracking the 2.6.32-56.118 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, 06. January 2014 17:17 UTC kernel-stable-Prepare-package-end:Tuesday, 07. January 2014 01:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 07. January 2014 01:03 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:00 UTC ppa-package-testing-start:Monday, 27. January 2014 09:00 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 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/1266525 Title: linux: 2.6.32-56.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New 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-56.118 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, 06. January 2014 17:17 UTC kernel-stable-Prepare-package-end:Tuesday, 07. January 2014 01:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 07. January 2014 01:03 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:00 UTC ppa-package-testing-start:Monday, 27. January 2014 09:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 09:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266525] Re: linux: 2.6.32-56.118 -proposed tracker
Copied to -proposed and overrides adjusted. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266525 Title: linux: 2.6.32-56.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New 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-56.118 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, 06. January 2014 17:17 UTC kernel-stable-Prepare-package-end:Tuesday, 07. January 2014 01:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 07. January 2014 01:03 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:00 UTC ppa-package-testing-start:Monday, 27. January 2014 09:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 09:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1192411] Re: [Dell Inspiron 14R 5420] Bluetooth indicator disappeared after wakeup form suspend / hibenate
Hello, As Quantal is about to EOL, and this bug does not happen in later releases. Confirmed with Ara, I will close this bug. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1192411 Title: [Dell Inspiron 14R 5420] Bluetooth indicator disappeared after wakeup form suspend / hibenate Status in “linux” package in Ubuntu: Won't Fix Bug description: CID: 201202-10511 Dell Inspiron 5420 The Bluetooth indicator disappears after suspend / hibernate. Connected Bluetooth device will stop working. Press the wireless key twice to bring down and up wireless device will get it back. Message from bluetooth-applet with a connected bluetooth device after suspend: ***wakeup from suspend*** Agent unregistration failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method UnregisterAgent with signature o on interface org.bluez.Adapter doesn't exist 'g-io-error-quark' (bluetooth-applet:6714): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (bluetooth-applet:6714): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (bluetooth-applet:6714): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (bluetooth-applet:6714): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (bluetooth-applet:6714): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-34-generic 3.5.0-34.55 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic x86_64 ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1811 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Jun 19 09:49:52 2013 HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533 InstallationDate: Installed on 2013-06-06 (12 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 5420 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-34-generic root=UUID=34982449-6328-4fbc-8e61-41863e82df6b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-34-generic N/A linux-backports-modules-3.5.0-34-generic N/A linux-firmware1.95.1 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X58 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 5420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1192411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273594] [NEW] [ASUSTeK Computer Inc. K53TA] suspend/resume failure
Public bug reported: Unity stop responding when pluging power cord. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ovi1434 F pulseaudio /dev/snd/controlC0: ovi1434 F pulseaudio Date: Tue Jan 28 10:56:11 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f83dc5f-6beb-4116-a122-76da673cb91f InstallationDate: Installed on 2014-01-26 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK Computer Inc. K53TA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-5-generic root=UUID=3bfc8893-7f5d-4561-840d-b2f2df3d19bc ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TA 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.:bvr214:bd04/06/2012:svnASUSTeKComputerInc.:pnK53TA:pvr1.0:rvnASUSTeKComputerInc.:rnK53TA:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend 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/1273594 Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: Unity stop responding when pluging power cord. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ovi1434 F pulseaudio /dev/snd/controlC0: ovi1434 F pulseaudio Date: Tue Jan 28 10:56:11 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f83dc5f-6beb-4116-a122-76da673cb91f InstallationDate: Installed on 2014-01-26 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK Computer Inc. K53TA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-5-generic root=UUID=3bfc8893-7f5d-4561-840d-b2f2df3d19bc ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TA dmi.board.vendor: ASUSTeK Computer Inc.
[Kernel-packages] [Bug 1273369] Re: [Acer Aspire V5-551G] late resume failure
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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.13-trusty/ ** 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/1273369 Title: [Acer Aspire V5-551G] late resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Resuming after suspension the screen remains all black. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1315 F pulseaudio leo2162 F pulseaudio /dev/snd/controlC0: lightdm1315 F pulseaudio leo2162 F pulseaudio Date: Mon Jan 27 19:36:39 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=fe7c6ec3-380a-4a91-bb5c-eebdc8c0e791 InstallationDate: Installed on 2014-01-17 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Aspire V5-551G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=9a1c801a-c943-4277-b910-0f1b7e02ce8c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer Aspire V5-551G] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd11/02/2012:svnAcer:pnAspireV5-551G:pvrV2.10:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
I have worked a bit more on this issue, and it seems that the crash happens when a process is executed in a namespace. So it's not the metadata proxy doing something that crashes the kernel, but is the act of launching the metadata proxy which causes the crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273594] 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/1273594 Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Unity stop responding when pluging power cord. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ovi1434 F pulseaudio /dev/snd/controlC0: ovi1434 F pulseaudio Date: Tue Jan 28 10:56:11 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f83dc5f-6beb-4116-a122-76da673cb91f InstallationDate: Installed on 2014-01-26 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK Computer Inc. K53TA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-5-generic root=UUID=3bfc8893-7f5d-4561-840d-b2f2df3d19bc ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TA 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.:bvr214:bd04/06/2012:svnASUSTeKComputerInc.:pnK53TA:pvr1.0:rvnASUSTeKComputerInc.:rnK53TA:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TA 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/1273594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270292] Re: linux: 3.11.0-17.30 -proposed tracker
Copied to -proposed, overrides adjusted, and linux-signed built. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270292 Title: linux: 3.11.0-17.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-17.30 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:Friday, 17. January 2014 20:58 UTC kernel-stable-Prepare-package-end:Saturday, 18. January 2014 05:10 UTC kernel-stable-Promote-to-proposed-start:Saturday, 18. January 2014 05:10 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 21. January 2014 18:54 UTC ppa-package-testing-start:Tuesday, 21. January 2014 18:54 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1270292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267489] Re: linux-ti-omap4: 3.5.0-238.54 -proposed tracker
** Description changed: This bug is for tracking the version to be filled 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:Thursday, 09. January 2014 14:38 UTC kernel-stable-master-bug:1266857 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1267489 Title: linux-ti-omap4: 3.5.0-238.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-ti-omap4” source package in Raring: New Status in “linux-ti-omap4” source package in Saucy: New Bug description: This bug is for tracking the version to be filled 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:Thursday, 09. January 2014 14:38 UTC kernel-stable-master-bug:1266857 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267490] Re: linux-armadaxp: 3.5.0-1627.36 -proposed tracker
** Description changed: This bug is for tracking the 3.5.0-1627.36 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:Thursday, 09. January 2014 14:40 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 07:02 UTC kernel-stable-Security-signoff-end:Friday, 10. January 2014 07:03 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-start:Monday, 13. January 2014 04:04 UTC kernel-stable-phase-changed:Monday, 13. January 2014 04:04 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC -- 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/1267490 Title: linux-armadaxp: 3.5.0-1627.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Quantal: In Progress Bug description: This bug is for tracking the 3.5.0-1627.36 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:Thursday, 09. January 2014 14:40 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 07:02 UTC kernel-stable-Security-signoff-end:Friday, 10. January 2014 07:03 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-start:Monday, 13. January 2014 04:04 UTC kernel-stable-phase-changed:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266857] Re: linux: 3.5.0-46.70 -proposed tracker
Copied to -proposed, overrides adjusted, and linux-signed built. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266857 Title: linux: 3.5.0-46.70 -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: In Progress 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-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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Quantal: New Bug description: This bug is for tracking the 3.5.0-46.70 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, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC kernel-stable-Prepare-package-end:Thursday, 09. January 2014 14:45 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. January 2014 14:45 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:01 UTC ppa-package-testing-start:Monday, 27. January 2014 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 869245] Re: CVE-2011-2517
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/869245 Title: CVE-2011-2517 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in
[Kernel-packages] [Bug 1266525] Re: linux: 2.6.32-56.118 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the 2.6.32-56.118 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, 06. January 2014 17:17 UTC kernel-stable-Prepare-package-end:Tuesday, 07. January 2014 01:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 07. January 2014 01:03 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Monday, 27. January 2014 09:00 UTC ppa-package-testing-start:Monday, 27. January 2014 09:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 09:00 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Tuesday, 28. January 2014 10:01 UTC + kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 10:01 UTC + kernel-stable-Certification-testing-start:Tuesday, 28. January 2014 10:01 UTC + kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 10:01 UTC + kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 10:01 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/1266525 Title: linux: 2.6.32-56.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress 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: Confirmed 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-56.118 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, 06. January 2014 17:17 UTC kernel-stable-Prepare-package-end:Tuesday, 07. January 2014 01:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 07. January 2014 01:03 UTC ppa-package-testing-start:Monday, 27. January 2014 09:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 09:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 28. January 2014 10:01 UTC kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 10:01 UTC kernel-stable-Certification-testing-start:Tuesday, 28. January 2014 10:01 UTC kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 10:01 UTC kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 10:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello Alberto, or anyone else affected, Accepted jockey into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “jockey” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: Fix Released Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “screen-resolution-extra” source package in Precise: Fix Released Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261116] Re: dkms uninstall fails unexpectedly without error message
Hello Antonius, or anyone else affected, Accepted dkms into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: dkms (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1261116 Title: dkms uninstall fails unexpectedly without error message Status in “dkms” package in Ubuntu: Fix Released Status in “dkms” source package in Precise: Fix Committed Status in “dkms” source package in Quantal: Won't Fix Status in “dkms” source package in Raring: New Status in “dkms” source package in Saucy: New Status in “dkms” source package in Trusty: Fix Released Status in “dkms” package in Debian: New Bug description: When trying to uninstall a (customly built) DKMS module using dkms uninstall -m my_module -v 1.1 dkms fails with exit code 1 and doesn't print an error message. The problem occurs with the invocation of the function have_one_kernel in the /usr/sbin/dkms script. This function doesn't evaluate to 0 as it should, when all conditions are met (as with the command specified above). The commands dkms uninstall -m my_module -v 1.1 --all and dkms uninstall -m my_module -v 1.1 -k 3.2.0-57 -k 3.5.0-44 fail as expected with the resp. error messages and exit codes in function have_one_kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1261116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 869250] Re: CVE-2011-2525
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/869250 Title: CVE-2011-2525 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in
[Kernel-packages] [Bug 880890] Re: CVE-2011-3209
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/880890 Title: CVE-2011-3209 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: 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: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Released Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released 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
[Kernel-packages] [Bug 1273629] [NEW] HSP fails on Ubuntu Touch
Public bug reported: When on Ubuntu Touch, HSP consistently fails to route any audio to the paired audio device. bluez-test-device create BT address bluez-test-audio connect BT address The above should create and pair a detected (in discoverable mode) bluetooth device, by default setting it up for HSP. The following excerpt from syslog on my mako shows the issue, with a bluetooth headset device failing to bring up HSP -- pulseaudio can acquire the first transport, but never release it: Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:start_inquiry() hci0 length 8 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: Discovery session 0x41f77f98 with :1.132 activated Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_ref() 0x41f77f98: ref=1 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 1 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Discovery session 0x41f77f98 with :1.132 deactivated Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Stopping discovery Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_discovery() index 0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_inquiry() hci0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 0 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_create() Creating device /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_set_temporary() temporary 1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=2 Jan 28 09:47:54 ubuntu-phablet kernel: [ 3389.758613] l2cap_sock_connect: failed -115 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:conn_complete() status 0x00 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_version_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_features_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_name_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:device_probe_drivers() Probing drivers for 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 1108--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/port.c:create_serial_device() Registered interface org.bluez.Serial on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 111e--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/manager.c:headset_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=3 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/device.c:input_device_new() Registered interface org.bluez.Input on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=4 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/device.c:audio_device_register() Registered interface org.bluez.Audio on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/manager.c:handle_uuid() Found Headset record Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/headset.c:headset_init() Registered interface org.bluez.Headset on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/manager.c:handle_uuid() Found Handsfree record Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:device_set_temporary() temporary 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_unref() 0x41f936e8: ref=3 Jan 28 09:47:56 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:__get_remote_version() hci0 handle 7 Jan 28 09:47:56 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_version_information() hci0 status 0 Jan 28 09:47:56 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_features_information() hci0 status 0 Jan 28 09:47:59
[Kernel-packages] [Bug 1261116] Re: dkms uninstall fails unexpectedly without error message
** Branch linked: lp:ubuntu/precise-proposed/dkms -- 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/1261116 Title: dkms uninstall fails unexpectedly without error message Status in “dkms” package in Ubuntu: Fix Released Status in “dkms” source package in Precise: Fix Committed Status in “dkms” source package in Quantal: Won't Fix Status in “dkms” source package in Raring: New Status in “dkms” source package in Saucy: New Status in “dkms” source package in Trusty: Fix Released Status in “dkms” package in Debian: New Bug description: When trying to uninstall a (customly built) DKMS module using dkms uninstall -m my_module -v 1.1 dkms fails with exit code 1 and doesn't print an error message. The problem occurs with the invocation of the function have_one_kernel in the /usr/sbin/dkms script. This function doesn't evaluate to 0 as it should, when all conditions are met (as with the command specified above). The commands dkms uninstall -m my_module -v 1.1 --all and dkms uninstall -m my_module -v 1.1 -k 3.2.0-57 -k 3.5.0-44 fail as expected with the resp. error messages and exit codes in function have_one_kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1261116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273629] Re: HSP fails on Ubuntu Touch
I've tracked it down to a shutdown() call in audio/headset.c so far. It seems to fail with ECONNABORTED on the mako; so nothing carries through with the HUP expected to happen when the SCO socket is really closed. On maguro, the socket appears to be properly closed (which may well indicate a firmware issue), however I still cannot properly make use of the headset, it will just loop back sound from the microphone to the speaker. ** Changed in: bluez (Ubuntu) Status: New = In Progress ** Changed in: bluez (Ubuntu) Importance: Undecided = Critical ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- 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/1273629 Title: HSP fails on Ubuntu Touch Status in “bluez” package in Ubuntu: In Progress Bug description: When on Ubuntu Touch, HSP consistently fails to route any audio to the paired audio device. bluez-test-device create BT address bluez-test-audio connect BT address The above should create and pair a detected (in discoverable mode) bluetooth device, by default setting it up for HSP. The following excerpt from syslog on my mako shows the issue, with a bluetooth headset device failing to bring up HSP -- pulseaudio can acquire the first transport, but never release it: Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:start_inquiry() hci0 length 8 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: Discovery session 0x41f77f98 with :1.132 activated Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_ref() 0x41f77f98: ref=1 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 1 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Discovery session 0x41f77f98 with :1.132 deactivated Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Stopping discovery Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_discovery() index 0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_inquiry() hci0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 0 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_create() Creating device /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_set_temporary() temporary 1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=2 Jan 28 09:47:54 ubuntu-phablet kernel: [ 3389.758613] l2cap_sock_connect: failed -115 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:conn_complete() status 0x00 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_version_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_features_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_name_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:device_probe_drivers() Probing drivers for 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 1108--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/port.c:create_serial_device() Registered interface org.bluez.Serial on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 111e--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/manager.c:headset_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=3 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/device.c:input_device_new() Registered interface org.bluez.Input on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=4 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/device.c:audio_device_register() Registered
[Kernel-packages] [Bug 880316] Re: Ubuntu installer can't setup network on Shuttle XS35GTV2
I updated my driver like suggested by Jabba56 in comment #11 and voila it's fixed. The strange thing in my situation was that I was able to connect using 1000mbit connection but not on a 100mbit connection. Will say before the update an ethernet cable on a 1000mbit networks has worked and the same cable on a 100mbit didn't. After the driver update this bug was fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Ubuntu installer can't setup network on Shuttle XS35GTV2 Status in “linux” package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1269872] Re: linux: 3.13.0-4.19 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release Status: Confirmed = Fix Released ** Changed in: kernel-development-workflow Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269872 Title: linux: 3.13.0-4.19 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-4.19 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-Prepare-package-start:Thursday, 16. January 2014 16:58 UTC kernel-Package-testing-start:Friday, 17. January 2014 01:00 UTC kernel-Prepare-package-end:Friday, 17. January 2014 01:00 UTC ppa-package-testing-start:Tuesday, 21. January 2014 22:00 UTC kernel-phase-changed:Thursday, 23. January 2014 17:00 UTC kernel-phase:CopyToRelease kernel-Promote-to-release-start:Thursday, 23. January 2014 17:00 UTC kernel-Package-testing-end:Thursday, 23. January 2014 17:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1269872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 887291] Re: CVE-2011-3638
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/887291 Title: CVE-2011-3638 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 887298] Re: CVE-2011-4077
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/887298 Title: CVE-2011-4077 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-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid
[Kernel-packages] [Bug 1266857] Re: linux: 3.5.0-46.70 -proposed tracker
** Description changed: This bug is for tracking the 3.5.0-46.70 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, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC kernel-stable-Prepare-package-end:Thursday, 09. January 2014 14:45 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. January 2014 14:45 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:01 UTC ppa-package-testing-start:Monday, 27. January 2014 09:01 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 11:02 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/1266857 Title: linux: 3.5.0-46.70 -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: In Progress 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-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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Quantal: New Bug description: This bug is for tracking the 3.5.0-46.70 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, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC kernel-stable-Prepare-package-end:Thursday, 09. January 2014 14:45 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. January 2014 14:45 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 27. January 2014 09:01 UTC ppa-package-testing-start:Monday, 27. January 2014 09:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 11:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 887299] Re: CVE-2011-4081
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/887299 Title: CVE-2011-4081 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released 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”
[Kernel-packages] [Bug 894369] Re: CVE-2011-4110
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/894369 Title: CVE-2011-4110 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-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Released Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
More info. The crash actually happen when a process is killed. This has consistently happened in 10 failures I've analyzed. So the first conclusion is that this might be, after all, a red herring, and the kernel dump being merely a consequence of the abrupt killing of a process. I've pushed this to verify whether this is the case: https://review.openstack.org/#/c/69579/ In this patch, I'm trying to use, just for testing purposes, SIGTERM instead of SIGKILL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239938] Re: No cardreader support for O2 Micro, Inc. Device [1217:8520]
** Changed in: linux-lts-saucy (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239938 Title: No cardreader support for O2 Micro, Inc. Device [1217:8520] Status in HWE Next Project: Confirmed Status in HWE Next saucy series: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Fix Committed Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: In Progress Status in “linux” source package in Saucy: Fix Committed Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Bug description: Open this bug to trace device driver for O2 Micro, Inc. Device [1217:8520]. We have seen this cardreader on some laptops, but most BIOS missed its special init, it's better to do that init in kernel. The support doesn't show up in mainline or mmc-next yet. Patch submitted upstream: http://article.gmane.org/gmane.linux.kernel.mmc/24244 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 893148] Re: CVE-2011-4132
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/893148 Title: CVE-2011-4132 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-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid
[Kernel-packages] [Bug 893147] Re: CVE-2011-4131
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/893147 Title: CVE-2011-4131 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-backport-oneiric” 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: Won't Fix 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: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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 Released Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51”
[Kernel-packages] [Bug 1273652] [NEW] apply of multi-monitor setting results in crash
Public bug reported: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Attachment added: Overview of used nvidia settings https://bugs.launchpad.net/bugs/1273652/+attachment/3960482/+files/NVIDIA%20X%20Server%20Settings_001.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1273652 Title: apply of multi-monitor setting results in crash Status in “nvidia-settings” package in Ubuntu: New Bug description: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270292] Re: linux: 3.11.0-17.30 -proposed tracker
** Description changed: This bug is for tracking the 3.11.0-17.30 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:Friday, 17. January 2014 20:58 UTC kernel-stable-Prepare-package-end:Saturday, 18. January 2014 05:10 UTC kernel-stable-Promote-to-proposed-start:Saturday, 18. January 2014 05:10 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 21. January 2014 18:54 UTC ppa-package-testing-start:Tuesday, 21. January 2014 18:54 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 12:04 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/1270292 Title: linux: 3.11.0-17.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-17.30 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:Friday, 17. January 2014 20:58 UTC kernel-stable-Prepare-package-end:Saturday, 18. January 2014 05:10 UTC kernel-stable-Promote-to-proposed-start:Saturday, 18. January 2014 05:10 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 21. January 2014 18:54 UTC ppa-package-testing-start:Tuesday, 21. January 2014 18:54 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 12:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1270292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267489] Re: linux-ti-omap4: 3.5.0-238.54 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the version to be filled 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:Thursday, 09. January 2014 14:38 UTC kernel-stable-master-bug:1266857 - kernel-stable-phase:ReadyToBePackaged - kernel-stable-phase-changed:Friday, 10. January 2014 21:03 UTC kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Tuesday, 28. January 2014 12:02 UTC + kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 12:02 UTC + kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 12:02 UTC + kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 12:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1267489 Title: linux-ti-omap4: 3.5.0-238.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-ti-omap4” source package in Raring: New Status in “linux-ti-omap4” source package in Saucy: New Bug description: This bug is for tracking the version to be filled 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:Thursday, 09. January 2014 14:38 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 28. January 2014 12:02 UTC kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 12:02 UTC kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 12:02 UTC kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267490] Re: linux-armadaxp: 3.5.0-1627.36 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Description changed: This bug is for tracking the 3.5.0-1627.36 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:Thursday, 09. January 2014 14:40 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 07:02 UTC kernel-stable-Security-signoff-end:Friday, 10. January 2014 07:03 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-start:Monday, 13. January 2014 04:04 UTC - kernel-stable-phase-changed:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Tuesday, 28. January 2014 12:03 UTC + kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 12:03 UTC + kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 12:03 UTC -- 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/1267490 Title: linux-armadaxp: 3.5.0-1627.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Quantal: In Progress Bug description: This bug is for tracking the 3.5.0-1627.36 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:Thursday, 09. January 2014 14:40 UTC kernel-stable-master-bug:1266857 kernel-stable-Certification-testing-end:Friday, 10. January 2014 07:02 UTC kernel-stable-Security-signoff-end:Friday, 10. January 2014 07:03 UTC kernel-stable-Prepare-package-end:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-start:Monday, 13. January 2014 04:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 10:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 28. January 2014 12:03 UTC kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 12:03 UTC kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 12:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1267490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 917829] Re: CVE-2011-4324
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/917829 Title: CVE-2011-4324 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: 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: Fix Committed Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package
[Kernel-packages] [Bug 917835] Re: CVE-2011-4325
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/917835 Title: CVE-2011-4325 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: 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: Fix Committed Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package
[Kernel-packages] [Bug 894373] Re: CVE-2011-4326
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/894373 Title: CVE-2011-4326 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in
[Kernel-packages] [Bug 1266857] Re: linux: 3.5.0-46.70 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the 3.5.0-46.70 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, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC kernel-stable-Prepare-package-end:Thursday, 09. January 2014 14:45 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. January 2014 14:45 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Monday, 27. January 2014 09:01 UTC ppa-package-testing-start:Monday, 27. January 2014 09:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 11:02 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Tuesday, 28. January 2014 13:01 UTC + kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 13:02 UTC + kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 13:01 UTC + kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 13:02 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/1266857 Title: linux: 3.5.0-46.70 -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: In Progress 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-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Quantal: New Bug description: This bug is for tracking the 3.5.0-46.70 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, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC kernel-stable-Prepare-package-end:Thursday, 09. January 2014 14:45 UTC kernel-stable-Promote-to-proposed-start:Thursday, 09. January 2014 14:45 UTC ppa-package-testing-start:Monday, 27. January 2014 09:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 11:02 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 28. January 2014 13:01 UTC kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 13:02 UTC kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 13:01 UTC kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 13:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 955892] Re: Failed name lookup - disconnected path error for long path names
Well, you can use Long Path Tool for such issues, it works good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/955892 Title: Failed name lookup - disconnected path error for long path names Status in “apparmor” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “apparmor” source package in Precise: Invalid Status in “linux” source package in Precise: Fix Released Status in “apparmor” source package in Quantal: Invalid Status in “linux” source package in Quantal: Fix Released Bug description: == Precise SRU Justification == This bug causes access failures when apparmor is mediating files with long pathnames. This problem is easy to trip when a confined application tries to access data encrypted with ecryptfs, but can occur on any filesystem. == Fix == Commit cffee16e8b997ab947de661e8820e486b0830c94 from security/next queue for 3.5 kernel fixes the issue == Impact == Users/application/daemons can not access the affected files while confined, which can result in application failures, users unable to access data, and confusion as the error message reported by the shell is Cannot open: Stale NFS file handle, whether or not NFS is in use. == Test Case == Run tests in from the updated apparmor regression test suite in qrt. or manually create a confined shell mount encryptfs, with file name obfuscation enabled from an unconfined shell created a 4 deep directory structure within the ecryptfs mount create a file in the deepest directory attempt to access the file from the confined shell AppArmor denies access to files with a path length 255 characters with the error message Failed name lookup - disconnected path. Example log entry: Mar 15 11:43:45 felix-desktop kernel: [ 6051.608954] type=1400 audit(1331808225.843:4896): apparmor=DENIED operation=mknod info=Failed name lookup - disconnected path error=-116 parent=24422 profile=/usr/bin/lintian name=temp-lintian-lab-xpvh_Pjhrm/pool/v/virtualbox/virtualbox_4.1.10-dfsg-1_source/virtualbox_4.1.10-dfsg.orig.tar.bz2.tmp-extract.5399h/virtualbox-4.1.10-dfsg/src/VBox/Devices/EFI/Firmware2/VBoxPkg/Library/VBoxOemHookStatusCodeLib/VBoxOemHookStatusCodeLib.c pid=24433 comm=tar requested_mask=c denied_mask=c fsuid=1000 ouid=1000 It seems to omit the mount point in the path name (/tmp/). The path_max parameter is much larger: % sudo cat /sys/module/apparmor/parameters/path_max 8192 % uname -a Linux felix-desktop 3.2.0-18-generic #29-Ubuntu SMP Fri Mar 9 21:36:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux % dpkg -l | grep apparmor ii apparmor 2.7.100-0ubuntu1 User-space parser utility for AppArmor ii apparmor-notify2.7.100-0ubuntu1 AppArmor notification system ii apparmor-utils 2.7.100-0ubuntu1 Utilities for controlling AppArmor ii dh-apparmor2.7.100-0ubuntu1 AppArmor debhelper routines ii libapparmor-perl 2.7.100-0ubuntu1 AppArmor library Perl bindings ii libapparmor1 2.7.100-0ubuntu1 changehat AppArmor library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/955892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 894374] Re: CVE-2011-4330
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/894374 Title: CVE-2011-4330 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-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Released Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid
[Kernel-packages] [Bug 912227] Re: CVE-2011-4915
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/912227 Title: CVE-2011-4915 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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: Invalid
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
** Changed in: neutron Milestone: None = icehouse-3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
I've run the related patch twice, and the kernel bug was hit even with SIGTERM rather than SIGKILL. I think this kind of confirms that failure to become ACTIVE error is related to issues while terminating metadata proxies and dnsmasq instances. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273532] Re: [Trusty Feature] New Intel CPU microcode-20140122
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (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/1273532 Title: [Trusty Feature] New Intel CPU microcode-20140122 Status in intel: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: The latest CPU microcode version 20140122 was uploaded on: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=23574 Please consider to update the microcode in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1273532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 912230] Re: CVE-2011-4916
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/912230 Title: CVE-2011-4916 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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: Invalid
[Kernel-packages] [Bug 1237296] Re: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic
Dear Uubuntu Team, I found a mailing [0] from AceLan Kao and got in contact with him. The sporadic working issue seems to be USB 3.0 xHCI related, I'm trying to evaluate this at the moment. However this has nothing todo with my initial problem where the bluetooth device wasn't recognized at all. So the patch from comment #44 which adds the missing device id is fine and should be implemented into saucy and trust, could you please arrange that? Thanks in advance Joshua [0] http://comments.gmane.org/gmane.linux.bluez.kernel/41109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237296 Title: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Saucy: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Hello, I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2. This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully deteced but I can't see any other Bluetooth devices and they can't see me too. Yours sincerly Joshua --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-031200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 1348 F pulseaudio /dev/snd/controlC0: joshua 1348 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: Acer Aspire E1-572 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 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.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-572 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 912231] Re: CVE-2011-4917
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/912231 Title: CVE-2011-4917 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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: Invalid
[Kernel-packages] [Bug 1273532] Re: [Trusty Feature] New Intel CPU microcode-20140122
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/intel-microcode /trusty-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273532 Title: [Trusty Feature] New Intel CPU microcode-20140122 Status in intel: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: The latest CPU microcode version 20140122 was uploaded on: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=23574 Please consider to update the microcode in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1273532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270292] Re: linux: 3.11.0-17.30 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the 3.11.0-17.30 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:Friday, 17. January 2014 20:58 UTC kernel-stable-Prepare-package-end:Saturday, 18. January 2014 05:10 UTC kernel-stable-Promote-to-proposed-start:Saturday, 18. January 2014 05:10 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Tuesday, 21. January 2014 18:54 UTC ppa-package-testing-start:Tuesday, 21. January 2014 18:54 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 12:04 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Tuesday, 28. January 2014 14:04 UTC + kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 14:04 UTC + kernel-stable-Certification-testing-start:Tuesday, 28. January 2014 14:04 UTC + kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 14:04 UTC + kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 14:04 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/1270292 Title: linux: 3.11.0-17.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-17.30 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:Friday, 17. January 2014 20:58 UTC kernel-stable-Prepare-package-end:Saturday, 18. January 2014 05:10 UTC kernel-stable-Promote-to-proposed-start:Saturday, 18. January 2014 05:10 UTC ppa-package-testing-start:Tuesday, 21. January 2014 18:54 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 28. January 2014 12:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 28. January 2014 14:04 UTC kernel-stable-Verification-testing-start:Tuesday, 28. January 2014 14:04 UTC kernel-stable-Certification-testing-start:Tuesday, 28. January 2014 14:04 UTC kernel-stable-Security-signoff-start:Tuesday, 28. January 2014 14:04 UTC kernel-stable-Regression-testing-start:Tuesday, 28. January 2014 14:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1270292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel
Hi Philipp, 12.04.4 is just the first appearance of the saucy kernel in the install media. As soon as a package is in main, it is supported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244627 Title: Please enable CONFIG_IMA in the ubuntu kernel Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Opinion Status in “linux” source package in Trusty: Fix Released Bug description: I would be doubly happy if this also went into the raring backport kernel. I chatted with apw and kees on #ubuntu-kernel earlier in the week. From a security engineer on our team: so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless you boot with ima_tcb=on. without ima_tcb=y, nothing is measured, nothing is audited, no performance/memory hit is incurred. Same is true for CONFIG_IMA_APPRAISE, except with the ima_appraise_tcb=on commandline parameter. ima appraise gives us the ability to sign binaries at installation time and check the signature at runtime. So we are asking that you enable CONFIG_IMA, but to not enable it via the kernel command line options. IMA would boot with an empty policy and should incur no overhead. Enterprising folks who want to run IMA can enable it in grub at their option. CONFIG_IMA=y and possibly: CONFIG_IMA_MEASURE_PCR_IDX=10 CONFIG_IMA_AUDIT=y CONFIG_IMA_LSM_RULES=y -A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
pasting one trace here for the record Jan 24 19:59:19 localhost kernel: [ 1028.120275] [ cut here ] Jan 24 19:59:19 localhost kernel: [ 1028.120848] kernel BUG at /build/buildd/linux-3.2.0/fs/buffer.c:2917! Jan 24 19:59:19 localhost kernel: [ 1028.121602] invalid opcode: [#1] SMP Jan 24 19:59:19 localhost kernel: [ 1028.122098] CPU 1 Jan 24 19:59:19 localhost kernel: [ 1028.122314] Modules linked in: xt_mac xt_physdev xt_conntrack ipt_REDIRECT xfs rmd160 crypto_null xfrm_user ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp xfrm6_tunnel tunnel6 af_key camellia lzo cast6 cast5 deflate zlib_deflate cts ctr gcm ccm serpent blowfish_generic blowfish_x86_64 blowfish_common twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common xcbc sha512_generic des_generic cryptd aes_x86_64 kvm ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge stp openvswitch(O) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_multipath nbd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables psmouse serio_raw virtio_balloon acpiphp floppy Jan 24 19:59:19 localhost kernel: [ 1028.130686] Jan 24 19:59:19 localhost kernel: [ 1028.130686] Pid: 12224, comm: dnsmasq Tainted: G O 3.2.0-58-virtual #88-Ubuntu Bochs Bochs Jan 24 19:59:19 localhost kernel: [ 1028.130686] RIP: 0010:[811a76d3] [811a76d3] submit_bh+0x113/0x120 Jan 24 19:59:19 localhost kernel: [ 1028.130686] RSP: :88015b2df738 EFLAGS: 00010246 Jan 24 19:59:19 localhost kernel: [ 1028.130686] RAX: 0005 RBX: 880072d71f08 RCX: 000b2a1e Jan 24 19:59:19 localhost kernel: [ 1028.130686] RDX: 008d RSI: 880072d71f08 RDI: 0211 Jan 24 19:59:19 localhost kernel: [ 1028.130686] RBP: 88015b2df758 R08: 811190c7 R09: 000180150015 Jan 24 19:59:19 localhost kernel: [ 1028.130686] R10: 8801ec485180 R11: 0100 R12: 0211 Jan 24 19:59:19 localhost kernel: [ 1028.130686] R13: 880004a8c824 R14: 0001 R15: 880072d71f08 Jan 24 19:59:19 localhost kernel: [ 1028.130686] FS: 7fd15c3aa700() GS:88021fc8() knlGS: Jan 24 19:59:19 localhost kernel: [ 1028.130686] CS: 0010 DS: ES: CR0: 8005003b Jan 24 19:59:19 localhost kernel: [ 1028.130686] CR2: 042c5560 CR3: 00020f9b6000 CR4: 06e0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] DR0: DR1: DR2: Jan 24 19:59:19 localhost kernel: [ 1028.130686] DR3: DR6: 0ff0 DR7: 0400 Jan 24 19:59:19 localhost kernel: [ 1028.130686] Process dnsmasq (pid: 12224, threadinfo 88015b2de000, task 8801a7178000) Jan 24 19:59:19 localhost kernel: [ 1028.130686] Stack: Jan 24 19:59:19 localhost kernel: [ 1028.130686] 8801ec485180 880072d71f08 0211 880004a8c824 Jan 24 19:59:19 localhost kernel: [ 1028.130686] 88015b2df788 811a9442 88015b2df7b8 8801ec485180 Jan 24 19:59:19 localhost kernel: [ 1028.130686] 880004a8c800 8800c3726c00 88015b2df798 811a94d3 Jan 24 19:59:19 localhost kernel: [ 1028.130686] Call Trace: Jan 24 19:59:19 localhost kernel: [ 1028.130686] [811a9442] __sync_dirty_buffer+0x52/0xd0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [811a94d3] sync_dirty_buffer+0x13/0x20 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [8125c578] journal_update_superblock+0x118/0x220 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [811ad575] ? bio_fs_destructor+0x15/0x20 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [811ac6eb] ? bio_put+0x2b/0x30 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [812f4e9d] ? blkdev_issue_flush+0xbd/0xe0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [81258463] cleanup_journal_tail.part.6+0x113/0x210 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [8125857d] cleanup_journal_tail+0x1d/0x30 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [81258d41] log_do_checkpoint+0x21/0x1f0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [8105053d] ? ttwu_do_wakeup+0x3d/0x120 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [8103dd05] ? pvclock_clocksource_read+0x55/0xf0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [81055db3] ? update_curr+0x143/0x1f0 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [8103dc39] ? default_spin_lock_flags+0x9/0x10 Jan 24 19:59:19 localhost kernel: [ 1028.130686] [81661680] ? kprobe_flush_task+0xc0/0x150 Jan 24 19:59:19 localhost
[Kernel-packages] [Bug 1264751] Re: [Asus G75VW] F2 Wifi Key Not Working
LPNow, 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 a Ubuntu repository 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 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. 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/1264751 Title: [Asus G75VW] F2 Wifi Key Not Working Status in “linux” package in Ubuntu: Incomplete Bug description: On my Asus G75VW from 12.04 through 13.10 x64 F2 does not toggle the WiFi. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sar1490 F pulseaudio /dev/snd/controlC0: sar1490 F pulseaudio Date: Sat Dec 28 12:14:12 2013 HibernationDevice: RESUME=UUID=c41137fa-5674-4ac7-b9ae-6cfd6fa16f29 InstallationDate: Installed on 2013-12-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. G75VW MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=b1a1b217-2d65-4a7c-a76e-701b097bf7ee ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.223 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW 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.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW 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/1264751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: [ASUS Sabertooth 990FX] Ubuntu 13.10/14.04 Catastrophic Random Kernel Crashes on Boot
Michael Murphy, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250321/comments/71 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** No longer affects: efibootmgr (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1250321 Title: [ASUS Sabertooth 990FX] Ubuntu 13.10/14.04 Catastrophic Random Kernel Crashes on Boot Status in “linux” package in Ubuntu: Invalid Bug description: The same issues are present both with GPT UEFI and simple MBR non-UEFI installs. I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine (maybe). However, after you reboot the system it will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It does not output anything to logs during these errors so the only thing you have to go by are screenshots of the errors. In general the errors are all indicating issues with systemd- udevd. I also had similar problems in Ubuntu 13.10, plus some extra problems. Ubuntu 13.10 fails at installing grub and the grub-efi-amd64 and outputs tons of errors regarding efibootmgr. It isn't related to the kernel since Ubuntu 13.04 with mainline kernel 3.12 works perfectly. It also doesn't seem to be related to firmware since I use linux-firmware-1.117 on Ubuntu 13.04 as well. It may be a bug related to efibootmgr and systemd. --- ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mmstick2398 F pulseaudio /dev/snd/controlC2: mmstick2398 F pulseaudio /dev/snd/controlC0: mmstick2398 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-11-13 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: fglrx Package: linux 3.8.0.34.52 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=1d566554-a73c-4ce0-9e48-45203b11c6f4 ro radeon.dpm=1 radeon.audio=1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.106 RfKill: Tags: third-party-packages raring Uname: Linux 3.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1264104] Re: 10de:0fd4 Asus G75VW F5/F6 doesn't change screen brightness
LPNow, 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 a Ubuntu repository 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 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. 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/1264104 Title: 10de:0fd4 Asus G75VW F5/F6 doesn't change screen brightness Status in “linux” package in Ubuntu: Incomplete Bug description: Via my Asus G75VW, I've tried 12.04 13.10 and the F5 F6 for screen brightness don't work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-34-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sar1704 F pulseaudio /dev/snd/controlC0: sar1704 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf731 irq 44' Mixer name : 'VIA VT1802' Components : 'HDA:11068446,10431487,0010' Controls : 40 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,10432119,00100100' Controls : 14 Simple ctrls : 2 Date: Wed Dec 25 03:03:22 2013 HibernationDevice: RESUME=UUID=1a59e00b-3953-4933-9a27-791a963642fc InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MachineType: ASUSTeK COMPUTER INC. G75VW MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=97cd6fd3-61e8-465f-8ebb-a54732d37062 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.79.9 SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.223 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW 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.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW 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/1264104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
** Summary changed: - Ubuntu UEFI install locks out UEFI firmware (~bios) access + [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access Status in “linux” package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-7ubuntu11 Candidate: 2.00-7ubuntu11 Pheonix Secure Core Tiano bios version 1.09 New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All functions worked normally when running Win7. Ubuntu 12.10 installed using whole disk. Installation successful Ubuntu boots and runs normally, however all access to the bios has now been lost. Pressing the default key (f2) during boot up is acknowledged by bios beep, but ignored and Ubuntu continues booting. In addition the 'boot choices' menu (f12) contains nothing but Ubuntu making it impossible to boot from USB or CD/DVD. The latter (f12) problem was overcome by opening up the machine, removing the ram and shorting the cl1/cl2 posts with a screwdriver. This restores the ability to boot from USB/CD by pressing f12 but does not restore bios access. The following recovery actions have been tried. 1) Install Boot-Repair, run repair, no change occurred. Boot repair report here: http://paste.ubuntu.com/1375041/ 2) Restore Windows from Clonezilla disk image (factory settings) - result - bios access is no longer possible from windows either, f2 now launches the Windows boot menu. 3) Update all drivers using Fujitsu driver update tool from within windows (which included a bios update). Result - no change, no bios. 4) Restored Ubuntu from Clonezilla disk image - no change. 5) Added second distro to disk. Installed successfully (uefi mode as that is all I have) no change to bios access. So overall result I have lost all bios access even from a reinstalled Windows. I repeat that bios access was perfectly normal before installing Ubuntu. I strongly suggest you read the contents of this thread in addition to the information here: http://ubuntuforums.org/showthread.php?t=2086602 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: grub-efi 2.00-7ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 23 15:50:07 2012 InstallationDate: Installed on 2012-11-22 (1 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
Satish, so to clarify, you personally with your hardware (not someone else with different hardware on another report) experienced it from Quantal through Trusty? ** 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/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access Status in “linux” package in Ubuntu: Incomplete Bug description: :~$ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-22 Candidate: 2.00-22 EFI installation of Ubuntu clears out the boot entries in firmware leaving user with no option but boot Ubuntu. Pressing (F2) to enter BIOS Setup has no effect as does pressing (F12) for Boot Order. The only way to get back firmware access is to flash the bios using manufacturer provided utilities. Unfortunately Fujitsu doesn't provide a BIOS flash utility for Linux/Ubuntu. It is to be noted that installed Windows in EFI mode on the same system does not clear out firmware access but just adds the 'Windows Boot Loader' entry at the top of the boot sequence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1852 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 27 11:06:37 2014 HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13 InstallationDate: Installed on 2014-01-26 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) MachineType: FUJITSU LIFEBOOK LH532 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=efd53305-1eac-42ba-b3f9-828b72cb5560 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1E dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 917706] Re: CVE-2012-0038
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/917706 Title: CVE-2012-0038 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: Fix Committed Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in
[Kernel-packages] [Bug 1092693] Re: cannot use A2DP profile on LG tone+ HBS-730 headset
Zach, 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 a Ubuntu repository 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 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. 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/1092693 Title: cannot use A2DP profile on LG tone+ HBS-730 headset Status in “linux” package in Ubuntu: Incomplete Bug description: When attempting to connect to a bluetooth headset from a laptop equipped with a CSR BS8510 bluetooth adapter (found in a RTL8188CEB8 mini-pci-express device), I get the following in syslog. KDE / bluedevil reports I have successfully connected to the device, but pulseaudio / kmix does not show that the device is connected. Ubuntu 12.10, bluez 4.101-0ubuntu6 Dec 20 14:24:39 ben-HP-Pavilion-dm4-Notebook-PC bluetoothd[14436]: Badly formated or unrecognized command: AT+BIA=0,0,0,1,1,1,0 Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC bluetoothd[14436]: Operation not supported (95) Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC pulseaudio[14301]: [pulseaudio] bluetooth-util.c: Failed to acquire transport fd: Input/output error Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC pulseaudio[14301]: [pulseaudio] module.c: Failed to load module module-bluetooth-device (argument: address=00:18:6B:15:AC:DC path=/org/bluez/14436/hci0/dev_00_18_6B_15_AC_DC): initialization failed. Dec 20 14:24:41 ben-HP-Pavilion-dm4-Notebook-PC kernel: [25660.054153] input: 00:18:6B:15:AC:DC as /devices/virtual/input/input14 Initially, this seemed similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400 or to https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=827692, but ultimately I beleive this is a different issue, since the chipset and unrecognized command are diffrent respectively. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben 14301 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=cfaa0aef-50a0-42c5-aa85-a1f6e060bcd4 InstallationDate: Installed on 2012-11-01 (49 days ago) InstallationMedia: This MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=4d3bbeef-14d0-4ef1-a45a-663fa6ea1fb1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 RelatedPackageVersions: linux-restricted-modules-3.5.0-19-generic N/A linux-backports-modules-3.5.0-19-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.28 dmi.chassis.asset.tag: CNU0440X2W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd02/14/2011:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr0587110002242B1022100:rvnHewlett-Packard:rn146A:rvr58.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.version: 0587110002242B1022100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234541] Re: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on
Geoff Kelsall, if it's outside your immediate ability to provide any further information, it would be fine to skip this one step. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234541 Title: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on Status in “linux” package in Ubuntu: Triaged Bug description: When I try to toggle my Novatech nfinity laptop bluetooth via Fn+F11 nothing happens. geoff@geoff-laptop:~$ lspci|grep Bluetooth 01:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth geoff@geoff-laptop:~$ ps aux| grep bluetooth geoff 2090 0.0 0.1 490248 6648 ?Sl 09:02 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service root 3328 0.0 0.0 19240 1752 ?Ss 09:41 0:00 /usr/sbin/bluetoothd geoff 3371 0.0 0.0 14984 1004 pts/3R+ 09:52 0:00 grep --color=auto bluetooth ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1957 F pulseaudio Date: Thu Oct 3 09:58:04 2013 HibernationDevice: RESUME=UUID=75bcd0bb-68ec-4ee2-a80d-e6cd4aa1d39d InstallationDate: Installed on 2013-10-03 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=286ca2cc-f79e-446b-9746-3865b1bfc022 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273392] Re: 0cf3:9271 [MSI FM2-A75IA-E53] ath9k_htc: AR9271 wireless device stops functioning
** Tags added: 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/1273392 Title: 0cf3:9271 [MSI FM2-A75IA-E53] ath9k_htc: AR9271 wireless device stops functioning Status in “linux” package in Ubuntu: Incomplete Bug description: A long time after a cold boot, my wireless connection starts dropping, will try to reconnect but will not come back again. When I'm in that state only a suspend, waiting a while and resuming gets my wireless connection back again. However, after that state it does not take long before it starts to drop again. WORKAROUND: I could not reproduce this problem again after setting nohwcrypt=1 on the ath9k_htc module. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1881 F pulseaudio /dev/snd/controlC0: sander 1881 F pulseaudio Date: Mon Jan 27 20:27:01 2014 HibernationDevice: RESUME=UUID=3f3e0b39-93b8-4c28-a8cd-91f2cf4a6890 InstallationDate: Installed on 2013-09-13 (136 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130912) MachineType: MSI MS-7792 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=add6edeb-2e13-438b-814e-d4995835e178 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A75IA-E53 (MS-7792) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd04/24/2013:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7792 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1181927] Re: [Aspire V5-431]13.04: Brightness control visible but does nothing
Upstream now marked this as a duplicate of: https://bugzilla.kernel.org/show_bug.cgi?id=51231 workaround for 3.13 (maybe previous versions as well) is the kernel option: video.use_native_backlight=1 ** Bug watch added: Linux Kernel Bug Tracker #51231 http://bugzilla.kernel.org/show_bug.cgi?id=51231 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1181927 Title: [Aspire V5-431]13.04: Brightness control visible but does nothing Status in “linux” package in Ubuntu: Triaged Bug description: Brightness control visible but does nothing on 13.04... The brightness up down buttons shows the overlay brightness icon going up and down but it does not change the brightness (backlight). I have tried adjusting the kernel options acpi_osi=x and acpi_backlight=y (that did work with 12.10) to make it work but to no avail. WORKAROUND: echo 20 /sys/class/backlight/intel_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-generic 3.8.0.21.37 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomasc2007 F pulseaudio Date: Mon May 20 12:45:35 2013 HibernationDevice: RESUME=UUID=2acc4a8c-a645-4f3c-bc8e-5c7a9d9df417 InstallationDate: Installed on 2013-04-11 (38 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Alpha amd64 (20130410) MachineType: Acer Aspire V5-431 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=4cfdb2ed-677a-4fd0-aa7d-5b118700bd35 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-21-generic N/A linux-backports-modules-3.8.0-21-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.20 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V1.20 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.20 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.20:bd12/12/2012:svnAcer:pnAspireV5-431:pvrV1.20:rvnAcer:rnAspireV5-431:rvrV1.20:cvnAcer:ct9:cvrV1.20: dmi.product.name: Aspire V5-431 dmi.product.version: V1.20 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
Geoff Kelsall, as per https://wiki.ubuntu.com/Bugs/Upstream/kernel : Second step: E-mail the maintainer mailinglist with Kernel.org format Please note, when E-Mailing a maintainer mailing list, do so in plain text, not html. Otherwise, it will be flagged as SPAM and bounced. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244643 Title: [Novatech N1402 NNB-978] Touchpad does not work at all Status in “linux” package in Ubuntu: Triaged Bug description: WORKAROUND: Kernel parameter: i8042.noloop When producing this bug report I got: ubuntu@ubuntu:~$ ubuntu-bug linux ubuntu@ubuntu:~$ (process:4162): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2918 F pulseaudio CasperVersion: 1.336ubuntu1 Date: Fri Oct 25 12:32:01 2013 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273392] Re: 0cf3:9271 [MSI FM2-A75IA-E53] ath9k_htc: AR9271 wireless device stops functioning
Sander Bradenburg, thank you for testing Trusty. Could you please provide the missing information following https://wiki.ubuntu.com/Kernel/LinuxWireless ? ** Tags added: kernel-wifi needs-wifi-debug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273392 Title: 0cf3:9271 [MSI FM2-A75IA-E53] ath9k_htc: AR9271 wireless device stops functioning Status in “linux” package in Ubuntu: Incomplete Bug description: A long time after a cold boot, my wireless connection starts dropping, will try to reconnect but will not come back again. When I'm in that state only a suspend, waiting a while and resuming gets my wireless connection back again. However, after that state it does not take long before it starts to drop again. WORKAROUND: I could not reproduce this problem again after setting nohwcrypt=1 on the ath9k_htc module. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1881 F pulseaudio /dev/snd/controlC0: sander 1881 F pulseaudio Date: Mon Jan 27 20:27:01 2014 HibernationDevice: RESUME=UUID=3f3e0b39-93b8-4c28-a8cd-91f2cf4a6890 InstallationDate: Installed on 2013-09-13 (136 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130912) MachineType: MSI MS-7792 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=add6edeb-2e13-438b-814e-d4995835e178 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A75IA-E53 (MS-7792) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd04/24/2013:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7792 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237296] Re: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic
Joshua, in order to send this issue upstream, could you please test the latest upstream kernel via http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.13-trusty/ and advise to the results? ** Tags removed: patch ** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237296 Title: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Saucy: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Hello, I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2. This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully deteced but I can't see any other Bluetooth devices and they can't see me too. Yours sincerly Joshua --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-031200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 1348 F pulseaudio /dev/snd/controlC0: joshua 1348 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: Acer Aspire E1-572 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 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.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-572 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 949905] Re: CVE-2012-1097
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/949905 Title: CVE-2012-1097 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-backport-oneiric” 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: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Fix Committed Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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 Released Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status
[Kernel-packages] [Bug 1273735] [NEW] Realtek r815x needed in the Ubuntu server kernel on the install media
Public bug reported: Howdy kernel guys, We need the Realtek r815x (usb network) driver added to the install media for the trusty server ISOs. Thanks! Dustin ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Incomplete ** Tags: micro-cluster -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273735 Title: Realtek r815x needed in the Ubuntu server kernel on the install media Status in “linux” package in Ubuntu: Incomplete Bug description: Howdy kernel guys, We need the Realtek r815x (usb network) driver added to the install media for the trusty server ISOs. Thanks! Dustin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273735] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1273735 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/1273735 Title: Realtek r815x needed in the Ubuntu server kernel on the install media Status in “linux” package in Ubuntu: Incomplete Bug description: Howdy kernel guys, We need the Realtek r815x (usb network) driver added to the install media for the trusty server ISOs. Thanks! Dustin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273735] Re: Realtek r815x needed in the Ubuntu server kernel on the install media
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Incomplete ** Changed in: linux (Ubuntu Trusty) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273735 Title: Realtek r815x needed in the Ubuntu server kernel on the install media Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: Howdy kernel guys, We need the Realtek r815x (usb network) driver added to the install media for the trusty server ISOs. Thanks! Dustin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272525] Re: SMBus host controller driver issue on ML
Looks like these should hopefully land into 3.14-rc1 or -rc2. Lets keep and eye on this and cherry-pick into Trusty once they've officially landed. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Leann Ogasawara (leannogasawara) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272525 Title: SMBus host controller driver issue on ML Status in amd: New Status in “linux” package in Ubuntu: In Progress Bug description: We implemented one patch (attached 0001. 0002 is optional for message fix) to support ML CZ SMBus ASIC changes, which was just accepted by Linux SMBus driver maintainer. [PATCH 1/2] i2c-piix4: Add support for AMD ML and CZ SMBus changes http://www.spinics.net/lists/linux-i2c/msg14430.html [PATCH 2/2] i2c-piix4: Use different message for AMD Auxiliary SMBus Controller http://www.spinics.net/lists/linux-i2c/msg14413.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1272525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1002505] Re: CVE-2012-2375
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/1002505 Title: CVE-2012-2375 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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 Released Status in “linux-armadaxp” source package in Precise: Fix Released 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-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid
[Kernel-packages] [Bug 1272525] Re: SMBus host controller driver issue on ML
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272525 Title: SMBus host controller driver issue on ML Status in amd: New Status in “linux” package in Ubuntu: In Progress Bug description: We implemented one patch (attached 0001. 0002 is optional for message fix) to support ML CZ SMBus ASIC changes, which was just accepted by Linux SMBus driver maintainer. [PATCH 1/2] i2c-piix4: Add support for AMD ML and CZ SMBus changes http://www.spinics.net/lists/linux-i2c/msg14430.html [PATCH 2/2] i2c-piix4: Use different message for AMD Auxiliary SMBus Controller http://www.spinics.net/lists/linux-i2c/msg14413.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1272525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1040557] Re: UEFI boot live-usb bricks SAMSUNG 530U3C, np700z5c laptop
I confirm Calant procedure: ON SAMSUNG 535U3C A03DE 1) Updated Bios to P07RAS 2) Disabled Fastboot on both Windows8 and bios 3) Run usb boot with SecureBoot Enabled and UEFI selected 4) Normally installed Ubuntu selecting Other during install and partitioning the hdd. 5) Selected the hdd for bootloader 6) On reboot Everything worked fine. IMPORTANT!! Using emulated bios..Ubuntu was really slow on AC-IN(100% CPU usage while charging)...but with UEFI Installation the problem seems to be solved. :D Oh i use AMD Catalyst Version 13.11 beta V9.95..Site version...wokrs wel.. FINALLY UBUNTU SEEMS TO BE FINE ON THIS MACHINE!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1040557 Title: UEFI boot live-usb bricks SAMSUNG 530U3C,np700z5c laptop Status in Ubuntu CD image build software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in Release Notes for Ubuntu quantal series: Fix Released Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Oneiric: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Bug description: I cannot provide detailed log massages because laptop is bricked right now. If you have courage to try it select UEFI boot from bios and than try to boot laptop using liveusb (made form Precise Pangolin 12.04.1 amd64). Laptop hangs up in black screen. If you force power-off, after it, laptop wont start. I mean it not event start bios, just black screen no sounds nothing. I filing this report, because i already bricked second laptop. At first i thought it was unrelated issue and laptop was fixed by warranty service (replaced motherboard), but after second time i quite sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273747] [NEW] linux: 3.13.0-6.21 -proposed tracker
Public bug reported: This bug is for tracking the 3.13.0-6.21 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-Prepare-package-start:Tuesday, 28. January 2014 16:22 UTC kernel-phase-changed:Tuesday, 28. January 2014 16:22 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug trusty ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Also affects: kernel-development-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New = In Progress ** Changed in: kernel-development-workflow Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) = Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu Trusty) 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/1273747 Title: linux: 3.13.0-6.21 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-6.21 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-Prepare-package-start:Tuesday, 28. January 2014 16:22 UTC kernel-phase-changed:Tuesday, 28. January 2014 16:22 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1273747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1273594] Re: [ASUSTeK Computer Inc. K53TA] suspend/resume failure
Aroiu Ovidiu, thank you for reporting this bug and helping make Ubuntu better. Could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, did this problem not occur in a release prior to Trusty? ** Tags added: latest-bios-214 needs-upstream-testing regression- potential ** Summary changed: - [ASUSTeK Computer Inc. K53TA] suspend/resume failure + [ASUS K53TA] suspend/resume failure ** 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/1273594 Title: [ASUS K53TA] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Unity stop responding when pluging power cord. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ovi1434 F pulseaudio /dev/snd/controlC0: ovi1434 F pulseaudio Date: Tue Jan 28 10:56:11 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2f83dc5f-6beb-4116-a122-76da673cb91f InstallationDate: Installed on 2014-01-26 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK Computer Inc. K53TA ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-5-generic root=UUID=3bfc8893-7f5d-4561-840d-b2f2df3d19bc ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K53TA] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TA 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.:bvr214:bd04/06/2012:svnASUSTeKComputerInc.:pnK53TA:pvr1.0:rvnASUSTeKComputerInc.:rnK53TA:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TA 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/1273594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273587] Re: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl]
** Tags added: latest-bios-v1.28 needs-suspend-logs needs-upstream- testing regression-potential -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273587 Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Confirmed Bug description: After start sytem ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mateusz2242 F pulseaudio Date: Tue Jan 28 09:43:59 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3e66ed3c-3b7c-43d9-a54e-389f1ec48223 InstallationDate: Installed on 2014-01-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) InterpreterPath: /usr/bin/python3.3 MachineType: Acer TravelMate 8572G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=04737bcf-4bff-4754-966c-3b1c85935572 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/20/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.28 dmi.board.name: BAP50-CP dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 8572G dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237296] Re: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237296 Title: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Saucy: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Hello, I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2. This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully deteced but I can't see any other Bluetooth devices and they can't see me too. Yours sincerly Joshua --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-031200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 1348 F pulseaudio /dev/snd/controlC0: joshua 1348 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: Acer Aspire E1-572 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 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.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-572 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1131331] Re: CVE-2012-4542
** No longer affects: linux-armadaxp (Ubuntu Raring) ** No longer affects: linux-ec2 (Ubuntu Raring) ** No longer affects: linux-lts-saucy (Ubuntu Raring) ** No longer affects: linux-lts-quantal (Ubuntu Raring) ** No longer affects: linux-mvl-dove (Ubuntu Raring) ** No longer affects: linux (Ubuntu Raring) ** No longer affects: linux-fsl-imx51 (Ubuntu Raring) ** No longer affects: linux-ti-omap4 (Ubuntu Raring) ** No longer affects: linux-lts-raring (Ubuntu Raring) -- 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/1131331 Title: CVE-2012-4542 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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: Won't Fix Status in “linux-lts-backport-oneiric” 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: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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: Invalid
[Kernel-packages] [Bug 1273536] Re: [Acer Extensa 5220] suspend/resume failure
Th. Sievers, thank you for reporting this bug and helping make Ubuntu better. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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. For example: kernel-fixed-upstream-3.13 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. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing 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 added: latest-bios-v1.35 needs-upstream-testing regression- potential ** 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/1273536 Title: [Acer Extensa 5220] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: as always ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1901 F pulseaudio CurrentDmesg: [9.598203] tg3 :02:00.0 eth0: Flow control is on for TX and on for RX [9.598222] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Mon Jan 27 15:58:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=dceef174-e6ec-4cf6-8d1e-c66678c0613d InstallationDate: Installed on 2013-11-24 (64 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Extensa 5220 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=22281f46-1fb6-4b8b-a48f-2290b8de35f0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer Extensa 5220] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-12-29 (29 days ago) UserGroups: dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5220 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273386] Related fix proposed to neutron (master)
Related fix proposed to branch: master Review: https://review.openstack.org/69653 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273587] Re: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl]
mmm, thank you for reporting this bug and helping make Ubuntu better. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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. For example: kernel-fixed-upstream-3.13 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. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing 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. ** 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/1273587 Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: After start sytem ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mateusz2242 F pulseaudio Date: Tue Jan 28 09:43:59 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3e66ed3c-3b7c-43d9-a54e-389f1ec48223 InstallationDate: Installed on 2014-01-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) InterpreterPath: /usr/bin/python3.3 MachineType: Acer TravelMate 8572G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=04737bcf-4bff-4754-966c-3b1c85935572 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer TravelMate 8572G] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/20/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.28 dmi.board.name: BAP50-CP dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 8572G dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273508] Re: Realtek ALC877-VD sound card is not supported
** Tags added: bios-outdated-v2.0 needs-upstream-testing regression- potential -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273508 Title: Realtek ALC877-VD sound card is not supported Status in “linux” package in Ubuntu: Incomplete Bug description: Any kernel (including mainline builds) fails to produce working sound. For example, in Kubuntu, there is only a buzzing noise from headphones or speakers plugged in to the front or back and the sound card is not recognized in Phonon. A log is worth a thousand words... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 27 20:23:12 2014 HibernationDevice: RESUME=UUID=05d521ea-3fd9-4ef8-bcae-6c6114e6c26f InstallationDate: Installed on 2013-09-03 (146 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: MSI MS-7786 MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=009f4aa2-4905-433f-8301-793c7955ec9f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: Upgraded to saucy on 2013-10-17 (102 days ago) dmi.bios.date: 02/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P25 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd02/13/2012:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P25(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273369] Re: [Acer Aspire V5-551G] late resume failure
** Tags added: bios-outdated-2.16 ** Tags added: needs-upstream-testing regression-potential ** 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/1273369 Title: [Acer Aspire V5-551G] late resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Resuming after suspension the screen remains all black. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1315 F pulseaudio leo2162 F pulseaudio /dev/snd/controlC0: lightdm1315 F pulseaudio leo2162 F pulseaudio Date: Mon Jan 27 19:36:39 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=fe7c6ec3-380a-4a91-bb5c-eebdc8c0e791 InstallationDate: Installed on 2014-01-17 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Aspire V5-551G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=9a1c801a-c943-4277-b910-0f1b7e02ce8c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [Acer Aspire V5-551G] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd11/02/2012:svnAcer:pnAspireV5-551G:pvrV2.10:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273419] Re: [TBD K8Upgrade-760GX] suspend/resume failure
gajdipajti, thank you for reporting this bug and helping make Ubuntu better. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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. For example: kernel-fixed-upstream-3.13 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. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing 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 added: latest-bios-1.80 needs-upstream-testing regression- potential ** Summary changed: - [TBD K8Upgrade-760GX] suspend/resume failure + [ASRock K8Upgrade-760GX] suspend/resume failure ** 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/1273419 Title: [ASRock K8Upgrade-760GX] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: duplicate ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: freeman1858 F pulseaudio CurrentDmesg: [ 26.557762] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Date: Mon Jan 27 21:04:48 2014 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1390836149 Failure: suspend/resume HibernationDevice: RESUME=UUID=5e8bc809-2c35--afb8-d1702a231429 InstallationDate: Installed on 2014-01-25 (2 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) InterpreterPath: /usr/bin/python3.3 MachineType: TBD K8Upgrade-760GX ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=0a7394b9-eb53-41af-b82d-d211ad086767 ro quiet splash radeon.dpm=1 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-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: SourcePackage: linux StagingDrivers: r8188eu Title: [TBD K8Upgrade-760GX] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/29/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: K8Upgrade-760GX dmi.board.vendor: TBD dmi.board.version: 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd08/29/2005:svnTBD:pnK8Upgrade-760GX:pvr1.00:rvnTBD:rnK8Upgrade-760GX:rvr1.00: dmi.product.name: K8Upgrade-760GX dmi.product.version: 1.00 dmi.sys.vendor: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273121] Re: [LENOVO ThinkPad T530] suspend/resume failure
Chris Johnston, as per http://download.lenovo.com/express/ddfm.html, an update to your BIOS is available (2.58). 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 . Thank you for your understanding. ** Summary changed: - [LENOVO 2359CTO] suspend/resume failure + [LENOVO ThinkPad T530] suspend/resume failure ** Tags added: bios-outdated-2.58 needs-upstream-testing regression- potential -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273121 Title: [LENOVO ThinkPad T530] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Error on boot ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2589 F pulseaudio /dev/snd/controlC0: chris 2589 F pulseaudio Date: Sun Jan 26 16:41:56 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=fa7cd523-ca40-49b4-bafe-5db8670dda7d InstallationDate: Installed on 2013-03-22 (311 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130312) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 2359CTO ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=e6bf556c-894e-40f4-9373-8767c33004c0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux Title: [LENOVO 2359CTO] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-12-16 (42 days ago) UserGroups: dmi.bios.date: 12/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273776] [NEW] same ext4 corruption in multiple systems
Public bug reported: We are using ext4 as the root filesystem for our server based on ubuntu precise 12.04.2 (kernel version 3.8.0-31-generic #46~precise1-Ubuntu). The same image for the root filesystem is copied over and over to different dom disks so all servers have the same partition data. It happened to three of our clients a root file system corruption. I'm attaching parted and e2fsck log output. Two systems have different motherboard and different cpu so it doesn't seem to be hardware dependent. I don't get errors while using dd to copy data from the drive but i have errors if i try to use tar: root:~/a# tar cf sda.tar m tar: m/lib/x86_64-linux-gnu: Cannot stat: Input/output error If i look at the partition's content i see that x86_64-linux-gnu is now a file and not a directory. I have exactly the same problem on the others servers. What can be the problem? What can i do? The system is 64bit and the root file system is created with: mkfs.ext4 -F -m 1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: precise ** Attachment added: e2fsck.log https://bugs.launchpad.net/bugs/1273776/+attachment/3960878/+files/e2fsck.log ** Tags added: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273776 Title: same ext4 corruption in multiple systems Status in “linux” package in Ubuntu: New Bug description: We are using ext4 as the root filesystem for our server based on ubuntu precise 12.04.2 (kernel version 3.8.0-31-generic #46~precise1-Ubuntu). The same image for the root filesystem is copied over and over to different dom disks so all servers have the same partition data. It happened to three of our clients a root file system corruption. I'm attaching parted and e2fsck log output. Two systems have different motherboard and different cpu so it doesn't seem to be hardware dependent. I don't get errors while using dd to copy data from the drive but i have errors if i try to use tar: root:~/a# tar cf sda.tar m tar: m/lib/x86_64-linux-gnu: Cannot stat: Input/output error If i look at the partition's content i see that x86_64-linux-gnu is now a file and not a directory. I have exactly the same problem on the others servers. What can be the problem? What can i do? The system is 64bit and the root file system is created with: mkfs.ext4 -F -m 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272959] Re: USB devices stop working
** Tags added: latest-bios-1301 needs-upstream-testing regression- potential ** Attachment removed: version.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272959/+attachment/3957870/+files/version.log ** Attachment removed: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272959/+attachment/3957887/+files/lspci-vnvn.log ** Summary changed: - USB devices stop working + [Asus M4N98TD EVO] USB devices stop working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272959 Title: [Asus M4N98TD EVO] USB devices stop working Status in “linux” package in Ubuntu: Incomplete Bug description: For the last few weeks I have been having this issue where my usb devices stop working. I have a Razer keyboard which is baclkit -- the lights stay on but none of the keys seem to do anything when the problem happens. If I unplug the keyboard and plug it back into any usb port it does not turn on at all. When the keyboard goes out and I unplug my mouse then plug it back in my mouse stays off. My computer becomes unusable untill I preform a restart. Looking at my logs the only thing I see that seems to be consistant when this occurs are lines like the following... [170244.083644] delay: estimated 432, actual 96 [170245.328423] delay: estimated 432, actual 96 [170247.707100] delay: estimated 432, actual 96 [170254.402556] delay: estimated 432, actual 96 [170254.810155] delay: estimated 432, actual 96 [170255.472507] delay: estimated 432, actual 96 --- Description: Ubuntu 13.10 Release: 13.10 --- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Jan 26 13:22:23 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=08c3c74f-e46e-4643-a70f-9362422b4b57 InstallationDate: Installed on 2014-01-19 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/Root0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N98TD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.00 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N98TDEVO:rvrRev2.00:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273024] Re: Ubuntu 13.10 64bit freezing
** Tags added: needs-crash-log needs-kernel-logs needs-upstream-testing regression-potential -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273024 Title: Ubuntu 13.10 64bit freezing Status in “linux” package in Ubuntu: Incomplete Bug description: For some reason Ubuntu Freezes. even when idle. Not sure if this is a bug But I don't know where else to turn. happening for To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273284] Re: Random but complete freeze with Asus UX31A
Free Rage, could you please capture the crash following https://wiki.ubuntu.com/DebuggingSystemCrash and attach a log of it to this report? ** Description changed: - Hello, - It's been some months, I'm experiencing complete freeze with my Ubuntu PC : mouse, keyboard are not responding, the fan accelerates to the max. - + It's been some months, I'm experiencing complete freeze with my Ubuntu + PC : mouse, keyboard are not responding, the fan accelerates to the max. It seems to me that it occurs randomly. Not exactly though because it never freezes when the screen is locked ! - - Thanks for updates if possible. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-58-generic 3.2.0-58.88 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pro2408 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pro2408 F pulseaudio Card0.Amixer.info: - Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46' -Mixer name : 'Intel PantherPoint HDMI' -Components : 'HDA:10ec0269,10431517,00100100 HDA:80862806,80860101,0010' -Controls : 23 -Simple ctrls : 11 + Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46' + Mixer name : 'Intel PantherPoint HDMI' + Components : 'HDA:10ec0269,10431517,00100100 HDA:80862806,80860101,0010' + Controls : 23 + Simple ctrls : 11 Date: Mon Jan 27 16:33:59 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b75418bb-ef61-4233-bf6d-da4ed6f698bd InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: ASUSTeK COMPUTER INC. UX31A MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic root=UUID=b58d6bf8-bc7b-4c42-8601-f74e95167153 ro quiet splash,pcie_aspm=force,rootfstype=ext4 RelatedPackageVersions: - linux-restricted-modules-3.2.0-58-generic N/A - linux-backports-modules-3.2.0-58-generic N/A - linux-firmware1.79.9 + linux-restricted-modules-3.2.0-58-generic N/A + linux-backports-modules-3.2.0-58-generic N/A + linux-firmware1.79.9 SourcePackage: linux StagingDrivers: rts5139 mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31A 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.:bvrUX31A.216:bd11/21/2012:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX31A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Tags added: bios-outdated-219 needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Summary changed: - Random but complete freeze with Asus UX31A + [ASUS ZENBOOK Touch UX31A] Intermittent complete freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273284 Title: [ASUS ZENBOOK Touch UX31A] Intermittent complete freeze Status in “linux” package in Ubuntu: Incomplete Bug description: It's been some months, I'm experiencing complete freeze with my Ubuntu PC : mouse, keyboard are not responding, the fan accelerates to the max. It seems to me that it occurs randomly. Not exactly though because it never freezes when the screen is locked ! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-58-generic 3.2.0-58.88 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog
[Kernel-packages] [Bug 1273089] Re: [MSI MS-7758] suspend/resume failure
** Tags added: bios-outdated-10.10 ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Summary changed: - [MSI MS-7758] suspend/resume failure + [MSI B75A-G43] suspend/resume failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273089 Title: [MSI B75A-G43] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Since the latest kernel update in trusty I've been unable to resume from suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dpm2650 F pulseaudio /dev/snd/controlC0: dpm2650 F pulseaudio Date: Mon Jan 27 08:34:21 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4980f964-44ac-44de-9747-13ddde0f5def InstallationDate: Installed on 2013-09-21 (127 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130921) InterpreterPath: /usr/bin/python3.3 MachineType: MSI MS-7758 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 RfKill: SourcePackage: linux StagingDrivers: r8712u Title: [MSI MS-7758] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-12-18 (39 days ago) UserGroups: dmi.bios.date: 07/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.4:bd07/24/2012:svnMSI:pnMS-7758:pvr2.0:rvnMSI:rnB75A-G43(MS-7758):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7758 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273776] Re: same ext4 corruption in multiple systems
** Attachment added: parted.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273776/+attachment/3960881/+files/parted.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/1273776 Title: same ext4 corruption in multiple systems Status in “linux” package in Ubuntu: New Bug description: We are using ext4 as the root filesystem for our server based on ubuntu precise 12.04.2 (kernel version 3.8.0-31-generic #46~precise1-Ubuntu). The same image for the root filesystem is copied over and over to different dom disks so all servers have the same partition data. It happened to three of our clients a root file system corruption. I'm attaching parted and e2fsck log output. Two systems have different motherboard and different cpu so it doesn't seem to be hardware dependent. I don't get errors while using dd to copy data from the drive but i have errors if i try to use tar: root:~/a# tar cf sda.tar m tar: m/lib/x86_64-linux-gnu: Cannot stat: Input/output error If i look at the partition's content i see that x86_64-linux-gnu is now a file and not a directory. I have exactly the same problem on the others servers. What can be the problem? What can i do? The system is 64bit and the root file system is created with: mkfs.ext4 -F -m 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272945] Re: Black screen and freeze after resume with i915 on Portege r200
peterthevicar, the next step is to fully commit bisect from mainline 3.9.9 to 3.10-rc1 in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? ** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-3.13 needs-bisect ** Tags added: bios-outdated-1.70 ** Summary changed: - Black screen and freeze after resume with i915 on Portege r200 + 8086:2592 [Toshiba Portégé R200-110] Black screen/freeze after resume with i915 ** Description changed: When I suspend (using either the session menu or by closing the lid) and resume, my Toshiba Portege R200 fails to wake. The flashing orange light changes to blue but the screen remains black and the keyboard is unresponsive (Caps Lock doesn't work, Ctrl-Alt-F keys don't work etc). - The only way to get out is to long-press the power button. + The only way to get out is to long-press the power button. This may be + due to the i915 kms module. This is a regression as it used to work in + 12.04 and 12.10. I did a chop using the mainline kernels and found that + kernel 3.9.9 (dated 3.Jul.13) works fine but 3.10-rc1 (13.May.13) + doesn't. In the mean time I'm running with 3.9.9. - I THINK it's the i915 kms module and suspend and resume certainly works - fine with the vesa driver. - - This is a regression as it used to work in 12.04 and 12.10. I did a chop - using the mainline kernels and found that kernel 3.9.9 (dated 3.Jul.13) - works fine but 3.10-rc1 (13.May.13) doesn't. - - Happy to help debug, but I'm not sure how to track changes between major - releases. In the mean time I'm running with 3.9.9 - - I'll attach the pm-suspend.log with debug on, but it shows nothing at - all after resume. - - TIA, Peter + WORKAROUND: Use the VESA driver. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: peter 1454 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: peter 1454 F pulseaudio CurrentDmesg: [ 136.627313] init: plymouth-stop pre-start process (2057) terminated with status 1 Date: Sun Jan 26 16:56:01 2014 HibernationDevice: RESUME=UUID=d4ddcbdb-5cdd-4c53-a3b4-2b7ef2bcb2c9 InstallationDate: Installed on 2013-10-14 (103 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Beta i386 (20130925.1) MachineType: TOSHIBA PORTEGE R200 MarkForUpload: True PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=78b72944-a92e-433a-837d-e66c5d9fefde ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.11.0-15-generic N/A - linux-backports-modules-3.11.0-15-generic N/A - linux-firmware 1.116 + linux-restricted-modules-3.11.0-15-generic N/A + linux-backports-modules-3.11.0-15-generic N/A + linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2005 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd10/25/2005:svnTOSHIBA:pnPORTEGER200:pvrPPR20E-01S02REN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R200 dmi.product.version: PPR20E-01S02REN dmi.sys.vendor: TOSHIBA ** 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/1272945 Title: 8086:2592 [Toshiba Portégé R200-110] Black screen/freeze after resume with i915 Status in “linux” package in Ubuntu: Incomplete Bug description: When I suspend (using either the session menu or by closing the lid) and resume, my Toshiba Portege R200 fails to wake. The flashing orange light changes to blue but the screen remains black and the keyboard is unresponsive (Caps Lock doesn't work, Ctrl-Alt-F keys don't work etc). The only way to get out is to long-press the power button. This may be due to the i915 kms module. This is a regression as it used to work in 12.04 and 12.10. I did a chop using the mainline kernels and found that kernel 3.9.9 (dated 3.Jul.13) works fine but 3.10-rc1 (13.May.13) doesn't. In the mean
[Kernel-packages] [Bug 1272916] Re: Bluetooth mouse connection
** Tags added: bios-outdated-r1043v7 needs-upstream-testing regression- potential resume suspend ** Summary changed: - Bluetooth mouse connection + [Sony VAIO SVP1321C5E] Bluetooth mouse connection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272916 Title: [Sony VAIO SVP1321C5E] Bluetooth mouse connection Status in “linux” package in Ubuntu: Incomplete Bug description: I use a bluetooth mouse from MS (Mouse 5000). It works perfect. Just after standby, the mouse has no more connection. I guess the bluetooth connection will not be rebooted? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fredrik1487 F pulseaudio /dev/snd/pcmC1D0p: fredrik1487 F...m pulseaudio /dev/snd/controlC0: fredrik1487 F pulseaudio Date: Sun Jan 26 15:04:16 2014 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=f4cd4363-fb42-4396-a760-ebf8c1cd6f1a HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2013-10-20 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Sony Corporation SVP1321C5E MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=8a2494e4-83e1-4a99-9b0d-61d525184510 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 15:05:26.570: The udisks-daemon is running (name-owner :1.47). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1021V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1021V7:bd08/08/2013:svnSonyCorporation:pnSVP1321C5E:pvrC60C41MT:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321C5E dmi.product.version: C60C41MT dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
