[Kernel-packages] [Bug 1265885] Re: regression with respect touchpad
I just tried another of the generic kernel. Here's some info: wt@braindead:~/Documents$ cat linux-3.9.0-030900.has_touchpad_controls.txt uname -a Linux braindead 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep syn [ 10.221126] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd40123/0x840300/0x126800, board id: 2734, fw id: 1522295 xinput list listing for touchpad: SynPS/2 Synaptics TouchPad FTR, the xinput listing on non-working kernels is the following: DLL060A:00 06CB:2734. I'm also attaching my dmesg from the working kernel version 3.9.0-030900. ** Attachment added: dmesg from working linux-3.9.0-030900 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+attachment/3961416/+files/linux-3.9.0-030900.dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265885 Title: regression with respect touchpad Status in “linux” package in Ubuntu: In Progress Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265885] Re: regression with respect touchpad
Bah, I guess that was expected since the 3.11 series of kernels worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265885 Title: regression with respect touchpad Status in “linux” package in Ubuntu: In Progress Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273991] [NEW] [Apple Inc. MacBookPro8, 2] suspend/resume failure
Public bug reported: Did not go into suspend. This happens from time to time, but usually it works. ProblemType: KernelOops 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 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nilsfr 3193 F pulseaudio /dev/snd/controlC0: root 2465 F pommed nilsfr 3193 F pulseaudio Date: Wed Jan 29 08:41:35 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c3531739-2648-4477-b93c-de992e205eb8 InstallationDate: Installed on 2011-12-02 (788 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3ce798cb-dd5f-4a73-841c-fed164c321d2 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.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [Apple Inc. MacBookPro8,2] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-12-05 (54 days ago) UserGroups: dmi.bios.date: 10/14/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B24.1110141131 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B24.1110141131:bd10/14/11:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops resume saucy suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273991 Title: [Apple Inc. MacBookPro8,2] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Did not go into suspend. This happens from time to time, but usually it works. ProblemType: KernelOops 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 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nilsfr 3193 F pulseaudio /dev/snd/controlC0: root 2465 F pommed nilsfr 3193 F pulseaudio Date: Wed Jan 29 08:41:35 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c3531739-2648-4477-b93c-de992e205eb8 InstallationDate: Installed on 2011-12-02 (788 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3ce798cb-dd5f-4a73-841c-fed164c321d2 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.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [Apple Inc. MacBookPro8,2] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-12-05 (54 days ago) UserGroups: dmi.bios.date: 10/14/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B24.1110141131 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10
[Kernel-packages] [Bug 1273991] 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/1273991 Title: [Apple Inc. MacBookPro8,2] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Did not go into suspend. This happens from time to time, but usually it works. ProblemType: KernelOops 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 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nilsfr 3193 F pulseaudio /dev/snd/controlC0: root 2465 F pommed nilsfr 3193 F pulseaudio Date: Wed Jan 29 08:41:35 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c3531739-2648-4477-b93c-de992e205eb8 InstallationDate: Installed on 2011-12-02 (788 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3ce798cb-dd5f-4a73-841c-fed164c321d2 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.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [Apple Inc. MacBookPro8,2] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-12-05 (54 days ago) UserGroups: dmi.bios.date: 10/14/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B24.1110141131 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B24.1110141131:bd10/14/11:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265885] Re: regression with respect touchpad
This bug is appears to be a duplicate of bug 1263319. However, I have not reinstalled. I would really like to help make sure this issue is handled properly so that other don't upgrade into this state like I did. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265885 Title: regression with respect touchpad Status in “linux” package in Ubuntu: In Progress Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Belkin F7D2301 Belkin Surf is based on Ralink RT3052 which support BGN 2x2:2 modes. Beside N is a Draft not End specification. Are use sure you use G and not N mode? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1274002] [NEW] [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure
Public bug reported: My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well. 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1356 F pulseaudio Date: Tue Jan 28 22:21:25 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-08-19 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ 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=fa95b2e7-43a7-4c3f-b083-956b3e8b3f53 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume saucy suspend trusty ** Tags added: saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274002 Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well. 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1356 F pulseaudio Date: Tue Jan 28 22:21:25 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-08-19 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux
[Kernel-packages] [Bug 1188025] Re: [Dell Vostro 5460] Right key on the touchpad is not working
** Also affects: hwe-next/trusty Importance: High Assignee: AceLan Kao (acelankao) Status: 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/1188025 Title: [Dell Vostro 5460] Right key on the touchpad is not working Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201211-12070, 201211-12071, 201211-12072, 201211-12073 Tried with 12.04.2 + update and 13.04 The right key on the touchpad of these four systems is not working. Verified with the pre-install version, right key does work on it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-32-generic 3.5.0-32.53~precise1 ProcVersionSignature: Ubuntu 3.5.0-32.53~precise1-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC290 Analog [ALC290 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1555 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf261 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0290,102805d9,0013 HDA:80862806,80860101,0010' Controls : 28 Simple ctrls : 12 Date: Thu Jun 6 14:18:49 2013 HibernationDevice: RESUME=UUID=6a753cbc-8331-4503-b189-7581e8fffe50 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Vostro 5460 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-32-generic root=UUID=e94d2ab1-eaf2-420f-87ae-7a5d6b5e4dd1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-32-generic N/A linux-backports-modules-3.5.0-32-generic N/A linux-firmware1.79.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X11 dmi.board.name: TIE3C1 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX11:bd11/19/2012:svnDellInc.:pnVostro5460:pvr:rvnDellInc.:rnTIE3C1:rvrX00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1188025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274002] Re: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure
** Description changed: - My laptop sometimes fail to come back from suspend. I will suspend it by - closing the lid, and the power light on the side of the laptop will + My laptop sometimes fails to come back from suspend. I will suspend it + by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. + This originally happened on Saucy. I upgraded to Trusty in the hopes + that the problem would be gone, but it's still there as well. + 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: david 1356 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: david 1356 F pulseaudio Date: Tue Jan 28 22:21:25 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-08-19 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=fa95b2e7-43a7-4c3f-b083-956b3e8b3f53 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 + 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 + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274002 Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well. 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
As far as I can see my email above was in plain text. Or have I missed something? Perhaps there is a fault with their spam filtering? -- You 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 1188025] Re: [Dell Vostro 5460] Right key on the touchpad is not working
@PHLin Can you give the mainline kernel, e.g. http://kernel.ubuntu.com/~kernel- ppa/mainline/daily/2014-01-23-trusty/, a try? There is a patch in current mainline that probably fixes this bug. commit c15bdfd5b9831e4cab8cfc118243956e267dd30e Commit: Dmitry Torokhov dmitry.torok...@gmail.com CommitDate: Wed Dec 18 08:47:29 2013 -0800 Input: elantech - improve clickpad detection The current assumption in the elantech driver that hw version 3 touchpads are never clickpads and hw version 4 touchpads are always clickpads is wrong. There are several bug reports for this, ie: https://bugzilla.redhat.com/show_bug.cgi?id=1030802 http://superuser.com/questions/619582/right-elantech-touchpad-button-not-working-in-linux I've spend a couple of hours wading through various bugzillas, launchpads and forum posts to create a list of fw-versions and capabilities for different laptop models to find a good method to differentiate between clickpads and versions with separate hardware buttons. Which shows that a device being a clickpad is reliable indicated by bit 12 being set in the fw_version. I've included the gathered list inside the driver, so that we've this info at hand if we need to revisit this later. Firmware of this touchpad is 0x461f04, so bit 12 is 1. ** Bug watch added: Red Hat Bugzilla #1030802 https://bugzilla.redhat.com/show_bug.cgi?id=1030802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188025 Title: [Dell Vostro 5460] Right key on the touchpad is not working Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201211-12070, 201211-12071, 201211-12072, 201211-12073 Tried with 12.04.2 + update and 13.04 The right key on the touchpad of these four systems is not working. Verified with the pre-install version, right key does work on it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-32-generic 3.5.0-32.53~precise1 ProcVersionSignature: Ubuntu 3.5.0-32.53~precise1-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC290 Analog [ALC290 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1555 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf261 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0290,102805d9,0013 HDA:80862806,80860101,0010' Controls : 28 Simple ctrls : 12 Date: Thu Jun 6 14:18:49 2013 HibernationDevice: RESUME=UUID=6a753cbc-8331-4503-b189-7581e8fffe50 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Vostro 5460 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-32-generic root=UUID=e94d2ab1-eaf2-420f-87ae-7a5d6b5e4dd1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-32-generic N/A linux-backports-modules-3.5.0-32-generic N/A linux-firmware1.79.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X11 dmi.board.name: TIE3C1 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX11:bd11/19/2012:svnDellInc.:pnVostro5460:pvr:rvnDellInc.:rnTIE3C1:rvrX00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1188025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] Re: [MacBookPro8, 2] Trusty linux kernel 3.12.0-2 doesn't boot
Sorry, I do not have the time to git bisect the kernel, however, 3.13.0-5-generic boots fine if I pass : radeon.modeset=1 i915.modeset=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272991] Re: dvb-usb: bulk message failed
sorry, I can not test with 3.13 ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272991 Title: dvb-usb: bulk message failed Status in “linux” package in Ubuntu: Incomplete Bug description: usb tuner - TT-connect CT-3650 CI The linux kernel spams the syslog with: Jan 26 22:32:01 laptop-2540p kernel: [ 7428.546358] dvb-usb: bulk message failed: -19 (5/0) Jan 26 22:32:01 laptop-2540p kernel: [ 7428.546364] ttusb2: there might have been an error during control message transfer. (rlen = 1, was 0) Jan 26 22:32:01 laptop-2540p kernel: [ 7428.546372] dvb-usb: bulk message failed: -19 (4/0) Jan 26 22:32:01 laptop-2540p kernel: [ 7428.546474] dvb-usb: bulk message failed: -19 (5/0) Jan 26 22:32:01 laptop-2540p kernel: [ 7428.546475] ttusb2: there might have been an error during control message transfer. (rlen = 1, was 0) 2 core 100% cpu i had to deactivate rsyslog to prevent a full disk now 1 core 100% cpu - from the system 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/controlC0: chronos2762 F pulseaudio Date: Sun Jan 26 22:35:13 2014 HibernationDevice: RESUME=UUID=04ed5b63-13e3-45ab-b507-9bc78dc47ec4 MachineType: Hewlett-Packard HP EliteBook 2540p MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=ce687e86-5c13-47e0-8e91-faab1a4e8c5c ro rootfstype=btrfs i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 pcie_aspm=force 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: Upgraded to saucy on 2013-09-28 (120 days ago) dmi.bios.date: 09/12/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.24 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: CZC1165484 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.24:bd09/12/2013:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248713] Re: CVE-2013-4483
** 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/1248713 Title: CVE-2013-4483 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug
[Kernel-packages] [Bug 1273595] Re: Xubuntu 14.104 Alpha 2 installer crashed
Initially, the issue was reproducible even after reporting the issue and unfortunately was not aware about apport-collect when the issue was reported. Surprisingly when retried today after your suggestion, I could install on couple of times without any issue. Thanks. But I do see 13.10 in most of the places like during startup, installation wizard instead of 14.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273595 Title: Xubuntu 14.104 Alpha 2 installer crashed Status in “linux” package in Ubuntu: Incomplete Bug description: Trying to install Xubuntu 14.04 Alpha2 on a VM using Virtual Box and it is has crashed during installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.3 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 CasperVersion: 1.336ubuntu1 Date: Tue Jan 28 14:37:25 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu) Importance: Undecided = High ** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273776 Title: same ext4 corruption in multiple systems Status in “linux” package in Ubuntu: Confirmed 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 1274002] 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/1274002 Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well. 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1356 F pulseaudio Date: Tue Jan 28 22:21:25 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-08-19 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ 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=fa95b2e7-43a7-4c3f-b083-956b3e8b3f53 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
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 = 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/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 1272525] Re: SMBus host controller driver issue on ML
** Tags added: kernel-da-key trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1274002] Re: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274002 Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up. One time I had to remove the battery, because the laptop refused to power up after I put it on suspend. On the next power up after a failed resume, I always get the Ubuntu An error happened dialog. This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well. 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 i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1356 F pulseaudio Date: Tue Jan 28 22:21:25 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-08-19 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ 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=fa95b2e7-43a7-4c3f-b083-956b3e8b3f53 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273799] Re: Gnome-Control-Center
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Package changed: linux (Ubuntu) = gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Medium = Undecided ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273799 Title: Gnome-Control-Center Status in “gnome-control-center” package in Ubuntu: New Bug description: I've got all the updates and recently found out that none of the buttons in Gnome-Control-Center works when i ran it through terminal no Out put came in when ya close the program it reopens it self up or if ya open something else it becomes on top of every thing and does not let u do hardly any thing. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darkangel 2755 F pulseaudio /dev/snd/controlC1: darkangel 2755 F pulseaudio /dev/snd/controlC0: darkangel 2755 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=838da5dd-9bfc-437d-9444-7759ecb65e03 InstallationDate: Installed on 2014-01-22 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121) MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=fdbca6d3-f474-49d6-b44e-441b6d515a5e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 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 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1273799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** 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/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 1234541] Re: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on
Mailed linux-blueto...@vger.kernel.org with requested info. Cannot see any url yet at http://www.spinics.net/lists/linux-bluetooth/ for my email. -- You 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 1273595] Re: Xubuntu 14.104 Alpha 2 installer crashed
** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Incomplete = 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/1273595 Title: Xubuntu 14.104 Alpha 2 installer crashed Status in “linux” package in Ubuntu: Invalid Bug description: Trying to install Xubuntu 14.04 Alpha2 on a VM using Virtual Box and it is has crashed during installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.3 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 CasperVersion: 1.336ubuntu1 Date: Tue Jan 28 14:37:25 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273815] Re: Iphone 5 cannot connect correctly to ubuntu
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.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 = 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/1273815 Title: Iphone 5 cannot connect correctly to ubuntu Status in “linux” package in Ubuntu: Incomplete Bug description: After I connect my iphone a message appears in my iphone saying trust this device? I press trust but it keeps repeating the message and does not connect fully to ubuntu. I have ubuntu 13.10. I expected to connect my iphone 5 to my computer and see and sync my music and videos. 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: christian 1854 F pulseaudio /dev/snd/controlC0: christian 1854 F pulseaudio Date: Tue Jan 28 14:26:44 2014 HibernationDevice: RESUME=UUID=f7e4fa68-f079-4668-9fed-8fe51a771d85 InstallationDate: Installed on 2014-01-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK Computer Inc. K52JT MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=f4026e73-626c-4935-99fe-3e2617c9e066 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K52JT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K52JT dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK52JT.204:bd12/01/2010:svnASUSTeKComputerInc.:pnK52JT:pvr1.0:rvnASUSTeKComputerInc.:rnK52JT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K52JT 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/1273815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Clicked the down triangle at the bottom right of gmail for more options, checked plain text and tried again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1273954] Re: Crashes randomly in Chrome and Firefox
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.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 = 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/1273954 Title: Crashes randomly in Chrome and Firefox Status in “linux” package in Ubuntu: Incomplete Bug description: Crashes and sends me back to the login screen gnome-session[15580]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 Updated arround 21:01 hours my Laptop and at arround 21:35:49 it started chrashing. SYSLOG is attached ! 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 NonfreeKernelModules: nvidia 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: VT1802 Analog [VT1802 Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick4980 F pulseaudio /dev/snd/controlC0: patrick4980 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf731 irq 48' Mixer name : 'VIA VT1802' Components : 'HDA:11068446,10431487,0010' Controls : 32 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Jan 28 23:13:47 2014 HibernationDevice: RESUME=UUID=347af211-349c-47f7-97a0-7f5793aef990 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) 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.2.0-58-generic root=UUID=c4068681-1c18-4d6f-ab5e-74ddc22e8d87 ro quiet splash 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 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.210 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.210:bd06/15/2012: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/1273954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273735 Title: Realtek r815x needed in the Ubuntu server kernel on the install media Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed 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 1188025] Re: [Dell Vostro 5460] Right key on the touchpad is not working
** Bug watch removed: Red Hat Bugzilla #1030802 https://bugzilla.redhat.com/show_bug.cgi?id=1030802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188025 Title: [Dell Vostro 5460] Right key on the touchpad is not working Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201211-12070, 201211-12071, 201211-12072, 201211-12073 Tried with 12.04.2 + update and 13.04 The right key on the touchpad of these four systems is not working. Verified with the pre-install version, right key does work on it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-32-generic 3.5.0-32.53~precise1 ProcVersionSignature: Ubuntu 3.5.0-32.53~precise1-generic 3.5.7.11 Uname: Linux 3.5.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC290 Analog [ALC290 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1555 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf261 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0290,102805d9,0013 HDA:80862806,80860101,0010' Controls : 28 Simple ctrls : 12 Date: Thu Jun 6 14:18:49 2013 HibernationDevice: RESUME=UUID=6a753cbc-8331-4503-b189-7581e8fffe50 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Vostro 5460 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-32-generic root=UUID=e94d2ab1-eaf2-420f-87ae-7a5d6b5e4dd1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-32-generic N/A linux-backports-modules-3.5.0-32-generic N/A linux-firmware1.79.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X11 dmi.board.name: TIE3C1 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX11:bd11/19/2012:svnDellInc.:pnVostro5460:pvr:rvnDellInc.:rnTIE3C1:rvrX00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1188025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Can you add the v option to tar to get verbose output, so it would be tar -cvf Also, have you been able to tar up that directory in the past? Did this just start happening after a recent update or upgrade? -- You 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: Confirmed 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 1254894] Re: CVE-2013-4563
** 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/1254894 Title: CVE-2013-4563 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Invalid Status in “linux-armadaxp” source package in Precise: Invalid 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed 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: Invalid 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1252422] Re: CVE-2013-4579
** 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/1252422 Title: CVE-2013-4579 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1261564] Re: CVE-2013-4587
** 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/1261564 Title: CVE-2013-4587 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1273776] Re: same ext4 corruption in multiple systems
Sorry maybe it was not clear, my fault. I can't boot the dom disk with problems so i've attached it to another system and mounted it in ~/a/m. I've run the tar command on the whole mounted partition (~/a/m - / on faulted disk). If you think you still need tar -cvf i can provide it, please tell me. I've never tried to tar that directory but it's not a tar problem. I can't access some files/directories on this partition because the ext4 filesystem is ruined. I always used this kernel so i don't know if it was working on previous versions. I'm also not able to test because i'm not able to replicate the problem. I can only wait for angry clients :) -- You 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: Confirmed 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 1254900] Re: CVE-2013-4592
** 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/1254900 Title: CVE-2013-4592 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed 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 Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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 Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in
[Kernel-packages] [Bug 1229591] [NEW] 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
You have been subscribed to a public bug: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) Ubuntu kernel version bisect revealed: First bad Ubuntu kernel: 3.11.0-0.2 last good Ubuntu kernel: 3.10.0-6.17 The results of a commit bisect are pending. --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2646 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2011-11-18 (675 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N411Z MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 RelatedPackageVersions: linux-restricted-modules-3.11.0-8-generic N/A linux-backports-modules-3.11.0-8-generic N/A linux-firmware1.114 Tags: saucy Uname: Linux 3.11.0-8-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare dmi.bios.date: 09/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0P01VP dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Low Status: New ** Tags: apport-collected kernel-bug-exists-upstream-v3.12-rc6 latest-bios-a06 needs-bisect needs-upstream-testing regression-release saucy trusty -- 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade https://bugs.launchpad.net/bugs/1229591 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270104] Re: CVE-2013-6123
** 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/1270104 Title: CVE-2013-6123 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description:
[Kernel-packages] [Bug 1254901] Re: CVE-2013-6282
** 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/1254901 Title: CVE-2013-6282 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: 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: Invalid 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1261566] Re: CVE-2013-6367
** 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/1261566 Title: CVE-2013-6367 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade Status in “linux” package in Ubuntu: New Bug description: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) Ubuntu kernel version bisect revealed: First bad Ubuntu kernel: 3.11.0-0.2 last good Ubuntu kernel: 3.10.0-6.17 The results of a commit bisect are pending. --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2646 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2011-11-18 (675 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N411Z MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 RelatedPackageVersions: linux-restricted-modules-3.11.0-8-generic N/A linux-backports-modules-3.11.0-8-generic N/A linux-firmware1.114 Tags: saucy Uname: Linux 3.11.0-8-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare dmi.bios.date: 09/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0P01VP dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173655] Re: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173655 Title: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver Status in “bcmwl” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Confirmed Status in “bcmwl” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Bug description: During 13.04 Live installation (I tried UBUNTU, UBUNTU GNOME and LUBUNTU), system crash because the WiFi Broadcom driver. It happen when system try to install and configure bcmwl-kernel- source, so I can't finish to install system successfully. I tried by minimal installation (http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-i386/current/images/netboot/mini.iso): installed ubuntu-desktop and everything ok, but after reboot I tried to install WiFi Broadcom driver and system crash again and it become instable, for example it can't turn off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.331 Date: Sat Apr 27 16:58:06 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade Status in “linux” package in Ubuntu: New Bug description: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) Ubuntu kernel version bisect revealed: First bad Ubuntu kernel: 3.11.0-0.2 last good Ubuntu kernel: 3.10.0-6.17 The results of a commit bisect are pending. --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2646 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2011-11-18 (675 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N411Z MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 RelatedPackageVersions: linux-restricted-modules-3.11.0-8-generic N/A linux-backports-modules-3.11.0-8-generic N/A linux-firmware1.114 Tags: saucy Uname: Linux 3.11.0-8-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare dmi.bios.date: 09/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0P01VP dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173655] Re: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173655 Title: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver Status in “bcmwl” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Confirmed Status in “bcmwl” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Bug description: During 13.04 Live installation (I tried UBUNTU, UBUNTU GNOME and LUBUNTU), system crash because the WiFi Broadcom driver. It happen when system try to install and configure bcmwl-kernel- source, so I can't finish to install system successfully. I tried by minimal installation (http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-i386/current/images/netboot/mini.iso): installed ubuntu-desktop and everything ok, but after reboot I tried to install WiFi Broadcom driver and system crash again and it become instable, for example it can't turn off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.331 Date: Sat Apr 27 16:58:06 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173655] Re: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173655 Title: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver Status in “bcmwl” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Confirmed Status in “bcmwl” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Bug description: During 13.04 Live installation (I tried UBUNTU, UBUNTU GNOME and LUBUNTU), system crash because the WiFi Broadcom driver. It happen when system try to install and configure bcmwl-kernel- source, so I can't finish to install system successfully. I tried by minimal installation (http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-i386/current/images/netboot/mini.iso): installed ubuntu-desktop and everything ok, but after reboot I tried to install WiFi Broadcom driver and system crash again and it become instable, for example it can't turn off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.331 Date: Sat Apr 27 16:58:06 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1089105] Re: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid
Verified with Trusty dailylive image (kernel 3.13.0-5) on 201204-10924 Trackpad works fine after closing and opening the lid. Left/right click, drag, two-finger scroll and multitouch all works fine. Steps: 1. Install dailylive image and boot to desktop 2. Suspend the system by closing the lid. 3. Wait for approx. 5 min. 4. Open the lid, check if the trackpad works. Expected results: * Touchpad should work after resumed from suspend. Actual result: * It works as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1089105 Title: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid Status in “lightdm” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “pm-utils” package in Ubuntu: New Status in “lightdm” source package in Precise: Invalid Status in “linux” source package in Precise: In Progress Status in “pm-utils” source package in Precise: New Status in “lightdm” source package in Quantal: Invalid Status in “linux” source package in Quantal: Confirmed Status in “pm-utils” source package in Quantal: New Status in “lightdm” source package in Raring: Invalid Status in “linux” source package in Raring: Confirmed Status in “pm-utils” source package in Raring: New Bug description: Problem: System does not resume from suspend properly. The issue is intermitent. However most of the time the system will exhibit three problematic symptoms: 1.) System will fail to resume and start x altogether 2.) System will resume with applications in frozen state and unity unresponsive to mouse-clicks. 3.) System will resume however trackpad will be disabled. kernel tested: 3.2.0-29-generic #46-Ubuntu Release: Ubuntu 12.04.1 Can reproduce? Yes Steps: 1.) Close laptop lid 2.) wait approx 5 minutes 3.) open laptop lid for system to resume. Expected result: System is able to suspend state and applications and resume when lid is opened in a proper and timely fashion. Command to recreate: fwts_test -s s3 --s3-sleep-delay=30 --s3-device-check | tee suspend_single_times.log WORKAROUND: Log into GNOME, and manually enable the touchpad through: dconf-editor-/org/gnome/settings-daemon/peripherals/touchpad/touchpad-enabled ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-29-generic 3.2.0-29.46 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1579 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9b61 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa500f,00100202 HDA:80862806,80860101,0010' Controls : 26 Simple ctrls : 12 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Dec 11 15:38:03 2012 HibernationDevice: RESUME=UUID=98d6d8c6-aa75-4069-9714-4f972d11aa61 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: LENOVO 814TF01 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=c1701df9-c6b6-4425-b6ec-5fede7c00ad6 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic N/A linux-backports-modules-3.2.0-29-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET26WW (0.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 814TF01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1274066] [NEW] iwlwifi fails with latest firmware
Public bug reported:
Reproduced on my x220:
ii linux-firmware1.122
all Firmware for Linux kernel drivers
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor
Peak]
[ 20.552702] iwlwifi :03:00.0: loaded firmware version 39.31.5.1 build
35138 op_mode iwldvm
--
[ 2994.296875] iwlwifi :03:00.0: fail to flush all tx fifo queues Q 0
[ 2994.296888] iwlwifi :03:00.0: Current SW read_ptr 11 write_ptr 12
[ 2994.316553] [ cut here ]
[ 2994.316592] WARNING: CPU: 2 PID: 15336 at
/build/buildd/linux-3.13.0/drivers/net/wireless/iwlwifi/pcie/trans.c:980
iwl_trans_pcie_grab_nic_access+0xcb/0xe0 [iwlwifi]()
[ 2994.316596] Timeout waiting for hardware access (CSR_GP_CNTRL 0x)
[ 2994.316600] Modules linked in: ctr ccm btusb overlayfs nls_iso8859_1
xt_conntrack ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables
xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc
iptable_filter ip_tables x_tables parport_pc ppdev rfcomm bnep bluetooth
binfmt_misc joydev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp
kvm_intel kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core arc4
videodev iwldvm mac80211 snd_hda_codec_hdmi thinkpad_acpi nvram microcode
snd_hda_codec_conexant snd_seq_midi snd_seq_midi_event snd_rawmidi psmouse
serio_raw snd_hda_intel snd_seq snd_hda_codec iwlwifi cfg80211 snd_hwdep
lpc_ich snd_pcm snd_seq_device snd_page_alloc snd_timer snd mei_me mei
soundcore mac_hid lp parport dm_crypt usb_storage crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel aesni_intel aes_x86_64 i915 lrw gf128mul glue_helper
ablk_helper cryptd e1000e i2c_algo_bit drm_kms_helper ptp ahci sdhci_pci
pps_core drm libahci sdhci video wmi
[ 2994.316740] CPU: 2 PID: 15336 Comm: kworker/u16:1 Not tainted
3.13.0-5-generic #20-Ubuntu
[ 2994.316745] Hardware name: LENOVO 42872WU/42872WU, BIOS 8DET55WW (1.25 )
11/01/2011
[ 2994.316787] Workqueue: phy0 ieee80211_beacon_connection_loss_work [mac80211]
[ 2994.316792] 0009 88009475db98 81705069
88009475dbe0
[ 2994.316801] 88009475dbd0 8106467d 88030963
880309633258
[ 2994.316808] 88009475dc78 0004
88009475dc30
[ 2994.316815] Call Trace:
[ 2994.316829] [81705069] dump_stack+0x45/0x56
[ 2994.316840] [8106467d] warn_slowpath_common+0x7d/0xa0
[ 2994.316848] [810646ec] warn_slowpath_fmt+0x4c/0x50
[ 2994.316870] [a0347eba] ? iwl_read32+0x1a/0x80 [iwlwifi]
[ 2994.316888] [a03492ab] iwl_trans_pcie_grab_nic_access+0xcb/0xe0
[iwlwifi]
[ 2994.316904] [a034a351] iwl_trans_pcie_read_mem+0x31/0x130
[iwlwifi]
[ 2994.316920] [a034838d] iwl_trans_pcie_wait_txq_empty+0x15d/0x3e0
[iwlwifi]
[ 2994.316939] [a0501090] iwlagn_mac_flush+0xa0/0x180 [iwldvm]
[ 2994.316973] [a0460bfd] ieee80211_flush_queues+0xbd/0x140
[mac80211]
[ 2994.317006] [a0477374] ieee80211_mgd_probe_ap_send+0xa4/0x140
[mac80211]
[ 2994.317036] [a0474892] ? ieee80211_cqm_rssi_notify+0x32/0x80
[mac80211]
[ 2994.317064] [a0476f1e] ? ieee80211_recalc_ps.part.24+0xce/0x200
[mac80211]
[ 2994.317091] [a0477515] ieee80211_mgd_probe_ap.part.25+0x105/0x160
[mac80211]
[ 2994.317118] [a0477b7d]
ieee80211_beacon_connection_loss_work+0x5d/0x90 [mac80211]
[ 2994.317127] [81080872] process_one_work+0x182/0x450
[ 2994.317134] [81081611] worker_thread+0x121/0x410
[ 2994.317142] [810814f0] ? rescuer_thread+0x3e0/0x3e0
[ 2994.317148] [81088262] kthread+0xd2/0xf0
[ 2994.317155] [81088190] ? kthread_create_on_node+0x190/0x190
[ 2994.317164] [8171597c] ret_from_fork+0x7c/0xb0
[ 2994.317171] [81088190] ? kthread_create_on_node+0x190/0x190
[ 2994.317175] ---[ end trace 2964175adf3c7828 ]---
[ 2994.317211] iwl data: : d0 92 7b 09 03 88 ff ff 00 86 7b 09 03 88 ff
ff ..{...{.
[ 2994.336899] iwlwifi :03:00.0: FH TRBs(0) = 0x5a5a5a5a
[ 2994.356657] iwlwifi :03:00.0: FH TRBs(1) = 0x5a5a5a5a
[ 2994.376374] iwlwifi :03:00.0: FH TRBs(2) = 0x5a5a5a5a
[ 2994.396066] iwlwifi :03:00.0: FH TRBs(3) = 0x5a5a5a5a
[ 2994.415752] iwlwifi :03:00.0: FH TRBs(4) = 0x5a5a5a5a
[ 2994.435437] iwlwifi :03:00.0: FH TRBs(5) = 0x5a5a5a5a
[ 2994.455215] iwlwifi :03:00.0: FH TRBs(6) = 0x5a5a5a5a
[ 2994.474958] iwlwifi :03:00.0: FH TRBs(7) = 0x5a5a5a5a
[ 2994.514336] [ cut here ]
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Reproduced on my x220:
ii linux-firmware1.122
all Firmware for Linux kernel drivers
[Kernel-packages] [Bug 1229591] 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/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) Ubuntu kernel version bisect revealed: First bad Ubuntu kernel: 3.11.0-0.2 last good Ubuntu kernel: 3.10.0-6.17 The results of a commit bisect are pending. --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2646 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2011-11-18 (675 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N411Z MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 RelatedPackageVersions: linux-restricted-modules-3.11.0-8-generic N/A linux-backports-modules-3.11.0-8-generic N/A linux-firmware1.114 Tags: saucy Uname: Linux 3.11.0-8-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare dmi.bios.date: 09/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0P01VP dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261568] Re: CVE-2013-6368
** 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/1261568 Title: CVE-2013-6368 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
Did you find out whether this actually was a regression compared to the previous kernel? Also, since the problem seems to be something submitting a bufferhead that is not mapped (anymore?) on releasing the mount namespace, maybe the content of /proc/pid/mount* of the process about to be killed. -- You 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 1273652] Re: apply of multi-monitor setting results in crash
That is not possble! My system do not recognize the crash an no report is created! -- 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: Incomplete 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 1237296] Re: 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic
Hello Christopher, I've already tested the final v3.13 kernel and the sporadic working issue does still exists. Same behavior than in the previouse kernel versions. I also created a bug report at the kernel bugzilla some time ago, no reaction until now. [0] [0] https://bugzilla.kernel.org/show_bug.cgi?id=68731 ** Bug watch added: Linux Kernel Bug Tracker #68731 http://bugzilla.kernel.org/show_bug.cgi?id=68731 -- You 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 1261570] Re: CVE-2013-6376
** 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/1261570 Title: CVE-2013-6376 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Invalid Status in “linux-armadaxp” source package in Precise: Invalid 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1256080] Re: CVE-2013-6378
** 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/1256080 Title: CVE-2013-6378 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released 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 Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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 Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1256083] Re: CVE-2013-6380
** 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/1256083 Title: CVE-2013-6380 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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 Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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 Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1273508] Re: Realtek ALC877-VD sound card is not supported
** Tags added: kernel-bug-exists-upstream ** Tags removed: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273508 Title: Realtek ALC877-VD sound card is not supported Status in “linux” package in Ubuntu: Confirmed 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 1256091] Re: CVE-2013-6382
** 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/1256091 Title: CVE-2013-6382 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1264472] Re: 05ac:12a9 [Medion E7218] Can't pair iPad / iOS7 with Ubuntu via USB
Still not working with IOS 7 7.0.4(11B554a) and Ubuntu 12.04 uname -a Linux pcname 3.8.0-35-generic #50~precise1-Ubuntu SMP Wed Dec 4 17:25:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Error Message: (attached) IOS7 Prompts user to Thrust this Computer dialog. User press Thrust message pops-up again. Installing libmobildevice makes no difference. ** Attachment added: This is due to the Thrust this computer item in IOS7 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1264472/+attachment/3961670/+files/dbus_error_while_connectiong_ipod_touch.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1264472 Title: 05ac:12a9 [Medion E7218] Can't pair iPad / iOS7 with Ubuntu via USB Status in “libimobiledevice” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: Here, I am trying to connect my ipad 2 running iOS 7.0.4 to a laptop running Ubuntu 12.04 via usb. After connecting the two devices via USB, Ubuntu displays the following message in a popup: The device 'Stephens iPad' is locked. Enter the passcode on the device and click 'Try again'. A second later on the ipad a modal popup appears saying something like the following in English: Trust this computer? Trust / Don't trust After clicking 'Trust', a popup appears on Ubuntu: Unable to mount Stephens iPad DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) On the ipad, the modal popup reappears. Clicking 'Trust' again gives the same result as before. Via dmesg, the following entries can be seen: [ 282.768166] usb 1-1.2: new high-speed USB device number 4 using ehci_hcd [ 289.694066] usb 1-1.2: USB disconnect, device number 4 [ 289.957594] usb 1-1.2: new high-speed USB device number 5 using ehci_hcd [ 293.528294] usb 1-1.2: USB disconnect, device number 5 [ 293.727877] usb 1-1.2: new high-speed USB device number 6 using ehci_hcd [ 342.606892] usb 1-1.2: USB disconnect, device number 6 Also occurs in Trusty 2014-01-02: ***Unable to mount iPad. Unhandled Lockdown error (-12) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-57-generic 3.2.0-57.87 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stkn 2039 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f0 irq 49' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,17c010e8,00100100 HDA:80862805,80860101,0010' Controls : 29 Simple ctrls : 13 Date: Fri Dec 27 10:09:43 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=221507c4-dcf9-491f-9a91-a67e0bb44c00 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: MEDION E7218 MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=UUID=78b87c2f-a47c-4216-8b83-554c5fdcc1d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-57-generic N/A linux-backports-modules-3.2.0-57-generic N/A linux-firmware1.79.9 SourcePackage: linux StagingDrivers: rts5139 mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E7218 dmi.board.vendor: MEDION dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0.30:bd04/26/2011:svnMEDION:pnE7218:pvrTobefilledbyO.E.M.:rvnMEDION:rnE7218:rvrTobefilledbyO.E.M.:cvnMEDION:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: E7218 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1264472/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
Hi Stefan, I have a few more info. I am trying to run the tests which trigger the issue on two machines, one with 3.2.0-57 and the other with 3.2.0-58. So far, after 20 runs on each machine, the crash did not happen, so I can't yet confirm the regression. However, back in october we had another kernel issue, which we solved by not executing anymore the process which was causing it (arping). This was originally tracked under bug 1224001. I've looked at a crash dump I saved from the time [1], and it's exactly the same. So I think that the update from 3.2.0-57 to 58 rather than introduce a bug exacerbated a pre-existent condition. Indeed I also verified that the diff did not introduce any change in the do_exit code path. Finally, just for the sake of it, I tried to apply [2], but just ended up crashing the kernel at every exit call Stefan, let me know if there is anything I can do to help you nail down the issue once the bug manifests; I'm not trying to write a script which just obsessively reproduces the sequence of operations which leads to the crash in the hope to have something easily reproducible. [1] http://paste.openstack.org/show/48056/ [2] https://kernel.googlesource.com/pub/scm/linux/kernel/git/khilman/linux-omap-pm/+/8aac62706adaaf0fab02c4327761561c8bda9448%5E%21/#F0 -- You 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
forgot to mention that when we dealt with bug 1224001 we were running 3.2.0-54 -- You 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 1256095] Re: CVE-2013-6392
** 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/1256095 Title: CVE-2013-6392 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-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: Won't Fix Status in “linux-lts-backport-natty” 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The
[Kernel-packages] [Bug 1256094] Re: CVE-2013-6383
** 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/1256094 Title: CVE-2013-6383 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” 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: 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: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released 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: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix 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: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix 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” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove”
[Kernel-packages] [Bug 1041790]
*** Bug 74180 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274143] Re: kernel backtrace triggered by rt2800usb driver
** Attachment added: sudo lshw -c network https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+attachment/3961769/+files/lsusb_-c_network.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: New Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274143] [NEW] kernel backtrace triggered by rt2800usb driver
Public bug reported: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: dmesg.txt.gz https://bugs.launchpad.net/bugs/1274143/+attachment/3961751/+files/dmesg.txt.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: New Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273954] Re: Crashes randomly in Chrome and Firefox
Will try installing the latest Upstream Kernel . I will let you know how it went ! Thanks for your rapid response ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273954 Title: Crashes randomly in Chrome and Firefox Status in “linux” package in Ubuntu: Incomplete Bug description: Crashes and sends me back to the login screen gnome-session[15580]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 Updated arround 21:01 hours my Laptop and at arround 21:35:49 it started chrashing. SYSLOG is attached ! 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 NonfreeKernelModules: nvidia 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: VT1802 Analog [VT1802 Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick4980 F pulseaudio /dev/snd/controlC0: patrick4980 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf731 irq 48' Mixer name : 'VIA VT1802' Components : 'HDA:11068446,10431487,0010' Controls : 32 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Jan 28 23:13:47 2014 HibernationDevice: RESUME=UUID=347af211-349c-47f7-97a0-7f5793aef990 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) 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.2.0-58-generic root=UUID=c4068681-1c18-4d6f-ab5e-74ddc22e8d87 ro quiet splash 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 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.210 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.210:bd06/15/2012: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/1273954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274143] 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/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: Confirmed Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274143] Re: kernel backtrace triggered by rt2800usb driver
Is this a new issue in Trusty? Do you happen to know if it happened in Saucy or prior releases? ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: Confirmed Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274143] Re: kernel backtrace triggered by rt2800usb driver
Also, can you attach a digital image or log of the backtrace? ** 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/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: Incomplete Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug 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 i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable 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: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 721896] Re: kswapd0 100% cpu usage
same here running under hyper-v my situation is as described above multiple times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/721896 Title: kswapd0 100% cpu usage Status in “linux” package in Ubuntu: Incomplete Bug description: After the running the latest ubuntu for at least 2 weeks, I've noticed that kswapd0 started using 100% CPU on one of my cores. However, I have enough of RAM and not using swap (Swap: 11876344k total, 62336k used). The only thing I can do to remove the problem is reboot the system. I'm using Ubuntu 10.04.1 LTS server version without any kernel modifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: quantal -- You 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 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
Satish, thank you for providing the requested information. Just to clarify, could you please provide a click-for-click on what you did when you were installing it? For example, you had a Windows 7/8 UEFI partition installed first, put CD in, Install Ubuntu, Install Ubuntu alongside them, etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1048817] Re: Connectivity issues with BCM5722 based Nic on Dell T110ii server running 12.04 LTS
The debian bug for this hasn't been touched since January of last year and this bug has sat idle about as long. Can we close this bug now? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1048817 Title: Connectivity issues with BCM5722 based Nic on Dell T110ii server running 12.04 LTS Status in “linux” package in Ubuntu: Opinion Status in “firmware-nonfree” package in Debian: Incomplete Bug description: NOTE: I am NOT the requester, I am converting a question from answers.launchpad.net to a bug for the real requester: https://launchpad.net/~robert-grizilo OS: Ubuntu 12.04 Server LTS x64 HW: Dell PowerEdge T110 ii Integrated nic BCM5722 has connectivity issues, from time to time stops working, kicks out from running any session (web, ssh... whatever), and sometimes comes back, sometimes not, and in between you can't connect, you can't even ping. I've tried to disable all bios IPMI features, but the problem didn't go away. I've tried on all speeds (10/100/1000) using ethtool, but the problem didn't go away. I've tried disabling various offload features using ethtool, but the problem didn't go away. I've installed second nic Intel 82579 and is working perfectly on the same network switch and cables. After every reboot the bcm5722 is working but then again after fiew minutes behave strange (the LED are showing correct states) and no connectivity. The server is brand new so I think is not a hardware issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1048817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hi Salvatore, so that old crash really looks quite similar. One interesting difference is that this process did simply exit and was not killed. Which sounds, like you did suspect as well, that this is not a regression in a recent kernel but something in the way things are executed changed and makes it just happen more often now. I hear from James Page that right now some changes in OpenStack will cause more things happen in parallel. That maybe causes some races to get triggered which haven't been observed (that often) before. To get a better understanding what the exact state of things is when this happens, would it be possible to enable crashdump on one of the development machines experiencing the issue and set it to panic on the oops? A description how to set up crashdump you would find at https://wiki.ubuntu.com/Kernel/CrashdumpRecipe. To cause the oops to become a panic you would have to echo 1 into /proc/sys/kernel/panic_on_oops after boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1250909] Re: [MacBookPro8, 2] Trusty linux kernel 3.12.0-2 doesn't boot
** Description changed: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully - boot on my machine. I have to use the older 3.11 kernel to boot. + boot on my machine. I have to use the older 3.11 kernel to boot. The + 3.12.0 kernel tries to boot but then seems to fail at some stage. - The 3.12.0 kernel tries to boot but then seems to fail at some stage. + WORKAROUND: 3.13.0-5-generic boots fine if I pass: + radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: shadeslayer 2482 F pulseaudio - /dev/snd/controlC0: shadeslayer 2482 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: shadeslayer 2482 F pulseaudio + /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: - 0 inteldrmfb - 1 radeondrmfb + 0 inteldrmfb + 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: - linux-restricted-modules-3.11.0-12-generic N/A - linux-backports-modules-3.11.0-12-generic N/A - linux-firmware 1.117 + linux-restricted-modules-3.11.0-12-generic N/A + linux-backports-modules-3.11.0-12-generic N/A + linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Changed in: linux (Ubuntu) Importance: High = 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/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias:
[Kernel-packages] [Bug 571977] Re: [Dell Alienware M15x] Possible race condition involving rtc wakealarm when hibernating a system
This was an issue in 2010 on Lucid. Give that it's 2014 and I'm on
Saucy at this point, I have no idea, nor any interest in pursuing this.
:(
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/571977
Title:
[Dell Alienware M15x] Possible race condition involving rtc wakealarm
when hibernating a system
Status in “linux” package in Ubuntu:
Invalid
Bug description:
I'm working on a test script that sets a time in the future in
/sys/class/rtc/rtc0/wakealarm and then uses pm-suspend to hibernate a
system. I believe I've found a race condition that's causing my tests
to fail.
First, the steps to recreate:
0: cat /proc/driver/rtc and verify that alarm_IRQ says 'no'
1: echo '+180' /sys/class/rtc/rtc0/wakealarm
1.5: cat /proc/driver/rtc and verify that alarm_IRQ says 'yes' and the
correct alarm time is set
2: sudo pm-suspend
3: wait 3 minutes
4: system wakes itself
5: wait for system to fully wake (disk activity to stop, or at the very
least, keyboard and mouse function to resume on desktop)
6: cat /proc/driver/rtc and verify that current time is alarm time and
alarm_IRQ still says 'yes'
The test, when putting the system into an S3 state, does not suffer
from this issue. It DOES when I'm using S4. I think the reason is
that S3 wakes quickly enough that the kernel can register that the
alarm fired and reset /proc/driver/rtc accordingly, however, when
waking from suspend, the kernel takes far longer to wake, causing it
to think that even though the rtc's alarm_IRQ fired the IRQ didn't
fire, so the kernel does not reset /proc/driver/rtc.
For example, this is the output from (my comments highlighted with ##
# watch -n 5 'cat /proc/driver/rtc |head -5'
## First observation, note alarm_date is empty, this is after echoing '0' to
/sys/class/rtc/rtc0/wakealarm
rtc_time: 20:35:11
rtc_date: 2010-04-29
alrm_time : 20:38:03
alrm_date : -**-29
alarm_IRQ : no
## wakealarm set
rtc_time: 20:35:16
rtc_date: 2010-04-29
alrm_time : 20:37:11
alrm_date : 2010-04-29
alarm_IRQ : yes
## executing pm-hibernate now
rtc_time: 20:35:21
rtc_date: 2010-04-29
alrm_time : 20:37:11
alrm_date : 2010-04-29
alarm_IRQ : yes
rtc_time: 20:35:26
rtc_date: 2010-04-29
alrm_time : 20:37:11
alrm_date : 2010-04-29
alarm_IRQ : yes
## System is now asleep.
## IRQ must be firing, because system wakes itself at this point after
sleeping for the proscribed number of seconds (180)
rtc_time: 20:38:16
rtc_date: 2010-04-29
alrm_time : 20:37:11
alrm_date : 2010-04-30
alarm_IRQ : yes
## first report after system is fully awake. Note that rtc_time is now a
full 60 seconds ahead of alarm time.
I'm not sure what's actually causing this behaviour, but what it seems
as though the kernel isn't actually registering that the IRQ actually
fired during a hibernate (or the rtc is broken, but it works fine
during S3 tests and I can verify that the IRQ fires and alarm_IRQ
resets to 'no' in S3 tests).
In any case, a race is created that isn't met in S3 testing due to the
nearly instantaneous kernel resumption from that sleep state, where it
is created (or at least the race is lost) when resuming from S4 due to
the length of time it takes to resume from that state.)
because of this, subsequent setting of /sys/class/rtc/rtc0/wakealarm
will fail without first clearing it with a '0' and if a piece of
software is actually looking to see if the RTC fired it's alarm_IRQ,
that software will believe that the IRQ has not been fired due to
/driver/proc/rtc incorrectly reporting the event.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bladernr 2029 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0f2 irq 22'
Mixer name : 'IDT
[Kernel-packages] [Bug 1218973] Re: [Dell XPS 12-9Q33] Touchpad not recognized
I merged the rmi4 code from the rmi4hid branch of https://github.com/mightybigcar/synaptics-rmi4/tree/rmihid into the ubuntu-saucy kernel, master branch and compiled my own kernel and tested it successfully. I created the following patch set: http://paste.ubuntu.com/6838915/ OR http://techerrata.com/dees_troy/rmi4.patch So it should be easier for others to apply the rmi4 driver and compile their own now as they see fit. Let me know if I can be of any further assistance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1218973 Title: [Dell XPS 12-9Q33] Touchpad not recognized Status in “linux” package in Ubuntu: Triaged Bug description: With the new XPS 12 (haswell), the touchpad gets detected as PS/2 Generic Mouse. cat /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input13 U: Uniq= H: Handlers=mouse2 event13 B: PROP=0 B: EV=7 B: KEY=700 Upstream URL: http://www.spinics.net/lists/linux-input/msg27737.html ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oli1862 F pulseaudio /dev/snd/controlC0: oli1862 F pulseaudio Date: Fri Aug 30 17:03:26 2013 HibernationDevice: RESUME=UUID=6d351a70-8a00-4f2c-a48d-a79cb070a939 InstallationDate: Installed on 2013-08-25 (4 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130825) MachineType: Dell Inc. XPS 12-9Q33 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic.efi.signed root=UUID=5d13cb7e-817c-4234-b758-0d79e4eade0b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/26/2013:svnDellInc.:pnXPS12-9Q33:pvrA02:rvnDellInc.:rnXPS12-9Q33:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] AudioDevicesInUse.txt
apport information ** Attachment added: AudioDevicesInUse.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961876/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 removed: kernel-bug-exists-upstream-v3.12-rc5 needs-upstream-testing ** Tags added: kernel-bug-exists-upstream-3.13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1250909] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961886/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1260825] Re: 168c:0032 ath3k built-in bluetooth cannot load firmware - sporadic
** This bug is no longer a duplicate of bug 1237296 168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1260825 Title: 168c:0032 ath3k built-in bluetooth cannot load firmware - sporadic Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: This is on an ASUS N550JV. Basically, the Bluetooth is sporadically available after restart/login. When not available, we get an error msg in dmesg about a patch that failed to load. This bug seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1102622. $ sudo lsusb -v Bus 003 Device 016: ID 13d3:3402 IMC Networks Device Descriptor: bDeviceProtocol 1 Bluetooth idVendor 0x13d3 IMC Networks idProduct 0x3402 bcdDevice0.02 iManufacturer 1 Atheros Communications iProduct2 Bluetooth USB Host Controller iSerial 3 Alaska Day 2006 $ sudo lspci 04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) dmesg: [ 13.663135] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 13.663173] Bluetooth: Loading patch file failed [ 13.663198] ath3k: probe of 3-5:1.0 failed with error -110 [ 13.663229] usbcore: registered new interface driver ath3k Things already tried (to no much avail) - - Update BIOS to latest version - Install bluetooth package - Enable ath9k bt coexistence (as per http://5thpeephole.blogspot.be/2013/10/install-ubuntu-1310-in-asus-n550jv.html) - unload / reload ath3k module: $ sudo modprobe -r ath3k; sleep 1; sudo modprobe ath3k ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-firmware 1.116 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 13 18:18:34 2013 Dependencies: InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1260825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961880/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961884/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961891/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961890/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961883/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961881/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961882/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961887/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961889/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961885/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961877/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961888/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961879/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250909] Re: [MacBookPro8, 2] Trusty linux kernel 3.12.0-2 doesn't boot
apport information ** Tags added: apport-collected ** Description changed: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. + --- + ApportVersion: 2.13.2-0ubuntu2 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 + InstallationDate: Installed on 2014-01-17 (12 days ago) + InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) + MachineType: Apple Inc. MacBookPro8,2 + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 + ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-5-generic N/A + linux-backports-modules-3.13.0-5-generic N/A + linux-firmware1.122 + Tags: trusty + Uname: Linux 3.13.0-5-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/24/12 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MBP81.88Z.0047.B27.1201241646 + dmi.board.asset.tag: Base Board Asset Tag# + dmi.board.name: Mac-94245A3940C91C80 + dmi.board.vendor: Apple Inc. + dmi.board.version: MacBookPro8,2 + dmi.chassis.type: 10 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-94245A3940C91C80 + dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: + dmi.product.name: MacBookPro8,2 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961875/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1
[Kernel-packages] [Bug 1250909] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1250909/+attachment/3961878/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250909 Title: [MacBookPro8,2] Trusty linux kernel 3.12.0-2 doesn't boot Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. WORKAROUND: 3.13.0-5-generic boots fine if I pass: radeon.modeset=1 i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=78835c1e-3239-4400-a197-5a9e13dd5dd6 InstallationDate: Installed on 2014-01-17 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140116) MachineType: Apple Inc. MacBookPro8,2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-5-generic.efi.signed ro root=UUID=9c924b5c-ab48-4ac9-8987-383dff3ce194 initrd=boot\initrd.img-3.13.0-5-generic radeon.dpm=1 radeon.modeset=1 i915.modeset=0 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 Tags: trusty Uname: Linux 3.13.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-28 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1264472] Re: 05ac:12a9 [Medion E7218] Can't pair iPad / iOS7 with Ubuntu via USB
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1264472 Title: 05ac:12a9 [Medion E7218] Can't pair iPad / iOS7 with Ubuntu via USB Status in “libimobiledevice” package in Ubuntu: Confirmed Bug description: Here, I am trying to connect my ipad 2 running iOS 7.0.4 to a laptop running Ubuntu 12.04 via usb. After connecting the two devices via USB, Ubuntu displays the following message in a popup: The device 'Stephens iPad' is locked. Enter the passcode on the device and click 'Try again'. A second later on the ipad a modal popup appears saying something like the following in English: Trust this computer? Trust / Don't trust After clicking 'Trust', a popup appears on Ubuntu: Unable to mount Stephens iPad DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) On the ipad, the modal popup reappears. Clicking 'Trust' again gives the same result as before. Via dmesg, the following entries can be seen: [ 282.768166] usb 1-1.2: new high-speed USB device number 4 using ehci_hcd [ 289.694066] usb 1-1.2: USB disconnect, device number 4 [ 289.957594] usb 1-1.2: new high-speed USB device number 5 using ehci_hcd [ 293.528294] usb 1-1.2: USB disconnect, device number 5 [ 293.727877] usb 1-1.2: new high-speed USB device number 6 using ehci_hcd [ 342.606892] usb 1-1.2: USB disconnect, device number 6 Also occurs in Trusty 2014-01-02: ***Unable to mount iPad. Unhandled Lockdown error (-12) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-57-generic 3.2.0-57.87 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stkn 2039 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f0 irq 49' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,17c010e8,00100100 HDA:80862805,80860101,0010' Controls : 29 Simple ctrls : 13 Date: Fri Dec 27 10:09:43 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=221507c4-dcf9-491f-9a91-a67e0bb44c00 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: MEDION E7218 MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=UUID=78b87c2f-a47c-4216-8b83-554c5fdcc1d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-57-generic N/A linux-backports-modules-3.2.0-57-generic N/A linux-firmware1.79.9 SourcePackage: linux StagingDrivers: rts5139 mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E7218 dmi.board.vendor: MEDION dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0.30:bd04/26/2011:svnMEDION:pnE7218:pvrTobefilledbyO.E.M.:rvnMEDION:rnE7218:rvrTobefilledbyO.E.M.:cvnMEDION:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: E7218 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1264472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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, thank you for testing the latest mainline kernel. The issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel (which would not be bugzilla, and your bugzilla report wouldn't have the information developers would want to see) by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked. Thank you for your understanding. -- You 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 1260825] Re: 168c:0032 ath3k built-in bluetooth cannot load firmware - sporadic
Fuujuhi, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux REPLACE-WITH-BUG-NUMBER If reproducible, could you also 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. ** Description changed: - This is on an ASUS N550JV. - - Basically, the Bluetooth is sporadically available after restart/login. - When not available, we get an error msg in dmesg about a patch that - failed to load. - - This bug seems similar to - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1102622. + This is on an ASUS N550JV. Basically, the Bluetooth is sporadically + available after restart/login. When not available, we get an error msg + in dmesg about a patch that failed to load. $ sudo lsusb -v - Bus 003 Device 016: ID 13d3:3402 IMC Networks + Bus 003 Device 016: ID 13d3:3402 IMC Networks Device Descriptor: - bDeviceProtocol 1 Bluetooth - idVendor 0x13d3 IMC Networks - idProduct 0x3402 - bcdDevice0.02 - iManufacturer 1 Atheros Communications - iProduct2 Bluetooth USB Host Controller - iSerial 3 Alaska Day 2006 + bDeviceProtocol 1 Bluetooth + idVendor 0x13d3 IMC Networks + idProduct 0x3402 + bcdDevice0.02 + iManufacturer 1 Atheros Communications + iProduct2 Bluetooth USB Host Controller + iSerial 3 Alaska Day 2006 $ sudo lspci 04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) dmesg: [ 13.663135] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 13.663173] Bluetooth: Loading patch file failed [ 13.663198] ath3k: probe of 3-5:1.0 failed with error -110 [ 13.663229] usbcore: registered new interface driver ath3k - - Things already tried (to no much avail) - - + Things already tried (to no much avail): - Update BIOS to latest version - Install bluetooth package - Enable ath9k bt coexistence (as per http://5thpeephole.blogspot.be/2013/10/install-ubuntu-1310-in-asus-n550jv.html) - unload / reload ath3k module: $ sudo modprobe -r ath3k; sleep 1; sudo modprobe ath3k ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-firmware 1.116 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 13 18:18:34 2013 Dependencies: - + InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Dependencies: - + DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - --- + --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Dependencies: - + DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-12-07 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
@salvatore-orlando I've built a test kernel with: 8aac6270 and a pre-req c99fe536 I've been able to boot it but haven't done much testing. Here it is: http://people.canonical.com/~arges/lp1273386/ If you have time you can try reproducing on this kernel to see if it fixes the issue as your originally suspected. However, the crashdump should be prioritized in solving this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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
Re: [Kernel-packages] [Bug 1273815] Re: Iphone 5 cannot connect correctly to ubuntu
'kernel-unable-to-test-upstream'. On 29/01/14 05:57, Joseph Salisbury wrote: Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.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 = 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/1273815 Title: Iphone 5 cannot connect correctly to ubuntu Status in “linux” package in Ubuntu: Incomplete Bug description: After I connect my iphone a message appears in my iphone saying trust this device? I press trust but it keeps repeating the message and does not connect fully to ubuntu. I have ubuntu 13.10. I expected to connect my iphone 5 to my computer and see and sync my music and videos. 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: christian 1854 F pulseaudio /dev/snd/controlC0: christian 1854 F pulseaudio Date: Tue Jan 28 14:26:44 2014 HibernationDevice: RESUME=UUID=f7e4fa68-f079-4668-9fed-8fe51a771d85 InstallationDate: Installed on 2014-01-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK Computer Inc. K52JT MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=f4026e73-626c-4935-99fe-3e2617c9e066 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K52JT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K52JT dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK52JT.204:bd12/01/2010:svnASUSTeKComputerInc.:pnK52JT:pvr1.0:rvnASUSTeKComputerInc.:rnK52JT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K52JT 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/1273815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
