[Kernel-packages] [Bug 1501818] onza (i386) - tests ran: 170, failed: 1
tests ran: 170, failed: 1; http://kernel.ubuntu.com/testing/4.2.0-14.16/onza__4.2.0-14.16__2015-10-02_20-50-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473596] Re: resume from suspend fails, works thereafter
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1473596 Title: resume from suspend fails, works thereafter Status in linux package in Ubuntu: Expired Bug description: when I resume from suspend the system drops back to suspend before the display can fully come back up. if I then try a second time it works, but the wireless connection is dropped and can only be re-connected via the connect to hidden network option in unity's network manager. I had this problem previously in 15.04 and finding no solution I switched to 15.10 where the issue had resolved. since updating, presumably the kernel, the problem has resumed in 15.10. I will boot in to my most recent prior kernel and see if the problem persists. let me know any other information I can provide. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.0.0-4-generic 4.0.0-4.6 ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7 Uname: Linux 4.0.0-4-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robbie 2229 F pulseaudio /dev/snd/controlC1: robbie 2229 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 10 16:35:51 2015 HibernationDevice: RESUME=UUID=1be1e682-410a-490f-a136-54b071211892 InstallationDate: Installed on 2015-06-24 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150609) MachineType: Hewlett-Packard p6706f ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.0-4-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.0.0-4-generic N/A linux-backports-modules-4.0.0-4-generic N/A linux-firmware 1.145 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.11 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: MXX1020D7B dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6706f dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478799] Re: bluetooth not working in 15.10
I can send files, but no dialog comes up to recive files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1478799 Title: bluetooth not working in 15.10 Status in Linux: Unknown Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 15.10 Wily No bluetooth indicator visible. I can't activate bluetooth in the bluetooth system-settings. Bluetooth mouse not working (I can't pair it). syslog: Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Starting SDP server Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: DIS cannot start: GATT is disabled Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init deviceinfo plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init proximity plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init time plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init alert plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init thermometer plugin Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]: VPN: loaded org.freedesktop.NetworkManager.pptp Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]: DNS: loaded plugin dnsmasq Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Starting SDP server Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: DIS cannot start: GATT is disabled Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init deviceinfo plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init proximity plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init time plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init alert plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init thermometer plugin Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully called chroot(). Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully dropped remaining capabilities. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: No service file found in /etc/avahi/services. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Network interface enumeration completed. Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Avahi mDNS/DNS-SD Stack. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Registering HINFO record with values 'X86_64'/'LINUX'. Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Bluetooth service. hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:15:A3:0B ACL MTU: 672:4 SCO MTU: 48:1 DOWN RX bytes:445 acl:0 sco:0 events:15 errors:0 TX bytes:63 acl:0 sco:0 commands:15 errors:0 rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1478799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498307] cavac (i386) - tests ran: 66, failed: 66
tests ran: 66, failed: 66; http://kernel.ubuntu.com/testing/3.19.0-30.33~14.04.1/cavac__3.19.0-30.33~14.04.1__2015-10-03_03-06-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1498307 Title: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC kernel-stable-master-bug:1498065 kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502345] Re: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure
Campbell Boyd, thank you for reporting this and helping make Ubuntu better. As per http://www.gigabyte.com/products/product- page.aspx?pid=4713#bios an update to your computer's buggy and outdated BIOS is available (F6). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-f6 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502345 Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: Crashed on wakiing from Suspend. Had to power off and on. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: campbell 2747 F pulseaudio /dev/snd/controlC0: campbell 2747 F pulseaudio Date: Fri Oct 2 19:24:41 2015 DuplicateSignature: suspend/resume:NOVATECH LTD PERSONAL COMPUTER:F5 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER 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-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502302] Re: general protection fault: 0000 [#1] SMP
Jose Gómez, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/xps-15-9530/drivers/advanced an update to your computer's buggy and outdated BIOS is available (A09). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-a09 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502302 Title: general protection fault: [#1] SMP Status in linux package in Ubuntu: Incomplete Bug description: Had some issues, the computer locked a couple of times. May or may not be related to this, as there was another error with Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-12-generic 4.2.0-12.14 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2466 F pulseaudio jose 3166 F pulseaudio /dev/snd/controlC0: gdm2466 F pulseaudio jose 3166 F pulseaudio Date: Fri Oct 2 19:54:40 2015 Failure: oops HibernationDevice: RESUME=UUID=be9ce8a7-7662-4da6-810c-14ff26282803 InstallationDate: Installed on 2014-02-04 (605 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic.efi.signed root=UUID=d7bcaffd-60e1-4fef-93fb-3d73a8d18907 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: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: Upgraded to wily on 2015-10-01 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 429942] Re: ASUS 1101HA brightness hotkeys don't work, generate ACPI errors
** Changed in: acpi-support (Ubuntu) Assignee: (unassigned) => Rachid (rachchood) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/429942 Title: ASUS 1101HA brightness hotkeys don't work, generate ACPI errors Status in acpi-support package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Hi, some of the hotkeys don't work correct. I'm using Ubuntu UNR 9.04. The keyboard layout is set to Asus-Laptop (the installer set it to Generic 105 (itel) I think) but ther is no change. Correct are: Fn+F1: Hibranate Fn+F7: disable display backlight Fn+F10,F11,F12: audio volume keys Fn+Space: wake-up Fn+Arrowkeys: Page up/down, end, pos1 Fn+Insert: Numlock Wrong is: Fn+F8: it should enable or disable the VGA output ... instead it increases audio volume (just like Fn+F12) Nonefunctional are: Fn+F2: Disable Wlan/Bluetooth Fn+F3: Disable touthpad Fn+F4: toggle fullscreen Fn+F6,F7: Display brightnes/backlight control Fn+F9: open taskmanager (in MS Win) also nonefunctional is the extra buttom on the left above the keybord to disable touchpad. --Fn+F2--Wlan-- for this key I get in 'xev': xev | grep keycode request MappingKeyboard, first_keycode 8, count 247 state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES, state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES, and acpi_listen: hotkey ATKD 0010 0024 -- --Fn+F3/additional Touchpadkey-- nothing in xev but in acpi_listen: hotkey ATKD 0037 0009 hotkey ATKD 0037 000a -- --Fn+F4-toggle Fulscreen-- nothing in xev acpi_listen: hotkey ATKD 0038 0006 -- --Fn+F5-decreas display-brightness/backlight-- nothing in xev and acpi_listen, but these messages in dmesg: [ 2684.513714] ACPI Exception (exoparg2-0444): AE_AML_PACKAGE_LIMIT, Index (00010) is beyond end of object [20080926] [ 2684.513767] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q0B] (Node f6c18900), AE_AML_PACKAGE_LIMIT - --Fn+F6-increas display-brightness/backlight-- nothing in xev and acpi_listen, but these messages in dmesg: [ 2844.889690] ACPI Exception (exoparg2-0444): AE_AML_PACKAGE_LIMIT, Index (00010) is beyond end of object [20080926] [ 2844.889743] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q0D] (Node f6c18918), AE_AML_PACKAGE_LIMIT --Fn+F8-VGA-Output-- xev | grep keycode request MappingKeyboard, first_keycode 8, count 247 request MappingKeyboard, first_keycode 8, count 248 request MappingKeyboard, first_keycode 8, count 247 sudo acpi_listen hotkey ATKD 0030 0006 - --Fn+F9-Taskmanager-- xev | grep keycode request MappingKeyboard, first_keycode 8, count 247 state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, sudo acpi_listen hotkey ATKD 0012 0007 -- That's what I got. If you need anything else then tell me. THX --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2824 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf3f38000 irq 23' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,104383ce,0014' Controls : 12 Simple ctrls : 7 DistroRelease: Ubuntu 10.04 LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) MachineType: ASUSTeK Computer INC. 1101HA Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Regression: Yes RelatedPackageVersions: linux-firmware 1.32 Reproducible: Yes Tags: lucid needs-upstream-testing regression-potential TestedUpstream: No Uname: Linux 2.6.32-16-generi
[Kernel-packages] [Bug 1502055] Re: Crypt password screen not responding
Piotr Piwonski, now that you can boot into Ubuntu, please perform the previously requested apport-collect. ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop
Pending https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502155/comments/4 . ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Incomplete Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.cha
[Kernel-packages] [Bug 1501993] Re: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
Martin Smith, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/latitude-e7440-ultrabook/drivers/advanced an update to your computer's buggy and outdated BIOS is available (A15). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-a15 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501993 Title: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: Hi there -- I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this happens with 4.2, specifically with: linux-image-extra-4.2.0-11-generic linux-image-extra-4.2.0-12-generic Oct 1 21:38:33 mart6985-laptop kernel: [ 876.317186] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:34 mart6985-laptop kernel: [ 877.156378] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995466] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995698] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting Oct 1 21:38:36 mart6985-laptop kernel: [ 878.825806] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:37 mart6985-laptop kernel: [ 879.664854] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:38 mart6985-laptop kernel: [ 880.503908] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821042] ACPI Error: Index value 0x0083 overflows field width 0x7 (20150619/exfldio-341) Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821046] ACPI Error: Method parse/execution failed [\NEVT] (Node 88040e0c7258), AE_AML_REGISTER_LIMIT (20150619/pspa rse-536) Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821050] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node 88040e0c4b90), AE_AML_REGISTER_ LIMIT (20150619/psparse-536) Oct 1 21:38:38 mart6985-laptop kernel: [ 881.343010] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998373] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998374] [ cut here ] Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998386] WARNING: CPU: 1 PID: 1038 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_c rtc_state+0x2c5/0x440 [i915]() Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998387] pipe state doesn't match! Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998387] Modules linked in: hid_generic usbhid iptable_filter ip_tables x_tables ctr ccm rfcomm btusb btrtl btbcm btinte l pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep bluetooth binfmt_misc pn544_mei mei_phy pn544 arc4 hci nfc dell_wmi iwlmvm sparse_keymap mac8021 1 dell_laptop dcdbas dell_smm_hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi uvcvideo input_leds videobuf2_vmalloc kvm_intel videobu f2_memops kvm cfg80211 joydev serio_raw videobuf2_core v4l2_common snd_hda_codec_hdmi videodev media lpc_ich snd_hda_codec_realtek snd_soc_rt5640 snd_soc_rl6231 snd_h da_codec_generic snd_soc_core shpchp snd_compress ac97_bus snd_hda_intel snd_pcm_dmaengine snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_hwdep snd_ra wmidi mei_me snd_pcm mei snd_seq snd_seq_device snd_timer 8250_fintek snd dell_smo8800 soundcore dw_dmac snd_soc_sst_acpi dw_dmac_core 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_pla
[Kernel-packages] [Bug 1502054] Re: Frequent freezes
Iveta Georgieva, thank you for reporting this and helping make Ubuntu better. As per http://us.acer.com/ac/en/US/content/drivers an update to your computer's buggy and outdated BIOS is available (1.11). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1.11 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502054 Title: Frequent freezes Status in linux package in Ubuntu: Incomplete Bug description: I am experiencing systematic freezes. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-12-generic 4.2.0-12.14 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: iveta 1639 F pulseaudio /dev/snd/controlC0: iveta 1639 F pulseaudio CurrentDesktop: MATE Date: Fri Oct 2 12:04:32 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=628c1a00-1f74-48b5-a16a-f562f8944eb0 InstallationDate: Installed on 2015-09-28 (3 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150729) MachineType: Acer Aspire VN7-791 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic root=UUID=70d28ac5-92d3-4537-8dfb-9cffcb39c368 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-791 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2014:svnAcer:pnAspireVN7-791:pvrV1.07:rvnAcer:rnAspireVN7-791:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire VN7-791 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501986] Re: Wifi signals are unstable and drops after sometime in RTL8723BE
Aakash Dabas, thank you for reporting this and helping make Ubuntu better. Could you please post the results of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501986 Title: Wifi signals are unstable and drops after sometime in RTL8723BE Status in linux package in Ubuntu: Incomplete Bug description: I'm using ubuntu 14.04 on my new laptop from HP( HP pavillion 15-ab032tx). It has got a network card from realtek which seems to be really buggy as of now. When I'm connected to a network either the wifi signals are damn low or they just vanish. And at the same time my other devices captures full wifi signals. Moreover the wifi just ain't works after suspend. Also I've tried updating the drivers. The current version of network driver is : rtl8723be. My kernel version is :3.13.0-65-generic. But nothing changes. Please help me out. Also I'm not so experienced with ubuntu so kindly tell me everything in details so that I can follow the commands. Thanks in advance. Other Details : Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-65-generic 3.13.0-65.105 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: entangler 1822 F pulseaudio /dev/snd/controlC0: entangler 1822 F pulseaudio CRDA: country IN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) CurrentDesktop: Unity Date: Fri Oct 2 07:44:13 2015 HibernationDevice: RESUME=UUID=b0be136a-5f24-44d5-a36d-3b5e7ea2ab7f InstallationDate: Installed on 2015-09-01 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 064e:930a Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed root=UUID=81ab3f87-cfd4-4f97-b7f3-a73cf5ead0c9 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-65-generic N/A linux-backports-modules-3.13.0-65-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.11 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd03/31/2015:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501876] Re: Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71
Jonathan Brier, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501876 Title: Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71 Status in linux package in Ubuntu: Incomplete Bug description: On the University of Maryland College Park Campus I am experiencing wifi connectivity issues where I get an initial connection, but it will drop frequently and have difficulty reconnecting to this secured wifi. This is at multiple locations on campus, but not off campus that I've found at this time. My Android Phone and Tablet do not have wifi issues connecting. Today I tried to work around the build in WiFi by adding the USB adapter Linksys AE1000. It was working for a while until it lost connection like the build in wifi on this laptop. After the loss of connection I saw a repeated: ieee80211 phy1: rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x0500, value=0x8804 ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71 Before the wifi connection loss I saw repeated: ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -71 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.33 ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jonathan 2145 F pulseaudio /dev/snd/controlC0: jonathan 2145 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 1 15:10:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-29 (244 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015) MachineType: Hewlett-Packard HP ENVY TS 15 Notebook PC ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=1cc26cb0-3476-4abf-a12e-acac53ba8537 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (177 days ago) dmi.bios.date: 01/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 198A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.14 dmi.chassis.asset.tag: 5CG32129MN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.19:bd01/26/2015:svnHewlett-Packard:pnHPENVYTS15NotebookPC:pvr088810305B032:rvnHewlett-Packard:rn198A:rvrKBCVersion03.14:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY TS 15 Notebook PC dmi.product.version: 088810305B032 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501789] Re: Mounting encrypted home and video driver fail at kernel update
Andras Muranyi, thank you for reporting this and helping make Ubuntu better. As per https://www.asus.com/Motherboards/M5A97/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (1605). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1605 ** 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/1501789 Title: Mounting encrypted home and video driver fail at kernel update Status in linux package in Ubuntu: Incomplete Bug description: Updated from linux-image-3.13.0-63-lowlatency to linux-image-3.13.0-65-lowlatency and at the following boot login failed and row-res mode appeared. I tried `update-initramfs -k -u` in recovery mode but it didn't help. It seems that the graphical login fails because of a failure to mount the encrypted home. On all the previous kernel updates, no such problem occurred. Booting into the older kernel works fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-lowlatency 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25 Uname: Linux 3.13.0-63-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: muranyia 3049 F pulseaudio /dev/snd/controlC0: muranyia 3049 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: Unity Date: Thu Oct 1 16:30:02 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=66f8ebeb-7c0a-4732-872c-94560438765b InstallationDate: Installed on 2013-06-10 (842 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-lowlatency root=UUID=991e27c8-91ce-4695-b75f-f1647644d93c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-lowlatency N/A linux-backports-modules-3.13.0-63-lowlatency N/A linux-firmware1.127.15 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-29 (397 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd05/30/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501765] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb012040f, found 0x00000000)
Alvin, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com /~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: kernel-fixed-upstream ** Tags added: latest-bios ** 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/1501765 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb012040f, found 0x) Status in linux package in Ubuntu: Incomplete Bug description: No actual trouble, (except having to restart plasmashell manually after each login, but that might not be related). Logs are full of warnings: Oct 01 14:52:39 pc-alvin kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb012040f, found 0x) Oct 01 14:52:39 pc-alvin kernel: [ cut here ] Oct 01 14:52:39 pc-alvin kernel: WARNING: CPU: 3 PID: 1033 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() Oct 01 14:52:39 pc-alvin kernel: pipe state doesn't match! Oct 01 14:52:39 pc-alvin kernel: Modules linked in: rfcomm bnep nls_iso8859_1 xfs libcrc32c intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi snd_h Oct 01 14:52:39 pc-alvin kernel: nf_conntrack_ftp nf_conntrack iptable_filter parport_pc ip_tables ppdev x_tables lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg uas usb_storage hid_gener Oct 01 14:52:39 pc-alvin kernel: CPU: 3 PID: 1033 Comm: Xorg Tainted: G W 4.2.0-12-generic #14-Ubuntu Oct 01 14:52:39 pc-alvin kernel: Hardware name: FUJITSU D3222-B1/D3222-B1, BIOS V4.6.5.4 R1.37.0 for D3222-B1x 08/06/2015 Oct 01 14:52:39 pc-alvin kernel: c027eab0 8804087737e8 817b0cd5 Oct 01 14:52:39 pc-alvin kernel: 880408773838 880408773828 81076536 880408773858 Oct 01 14:52:39 pc-alvin kernel: 8804087738c0 88040ba1e800 0001 88040ba1eb50 Oct 01 14:52:39 pc-alvin kernel: Call Trace: Oct 01 14:52:39 pc-alvin kernel: [] dump_stack+0x45/0x57 Oct 01 14:52:39 pc-alvin kernel: [] warn_slowpath_common+0x86/0xc0 Oct 01 14:52:39 pc-alvin kernel: [] warn_slowpath_fmt+0x46/0x50 Oct 01 14:52:39 pc-alvin kernel: [] ? intel_pipe_config_compare+0xa67/0xc60 [i915] Oct 01 14:52:39 pc-alvin kernel: [] check_crtc_state+0x2c5/0x440 [i915] Oct 01 14:52:39 pc-alvin kernel: [] intel_modeset_check_state+0x20e/0x6b0 [i915] Oct 01 14:52:39 pc-alvin kernel: [] intel_crtc_set_config+0x4c7/0x580 [i915] Oct 01 14:52:39 pc-alvin kernel: [] ? drm_mode_create+0x25/0x60 [drm] Oct 01 14:52:39 pc-alvin kernel: [] drm_mode_set_config_internal+0x66/0x100 [drm] Oct 01 14:52:39 pc-alvin kernel: [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] Oct 01 14:52:39 pc-alvin kernel: [] drm_ioctl+0x125/0x610 [drm] Oct 01 14:52:39 pc-alvin kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Oct 01 14:52:39 pc-alvin kernel: [] do_vfs_ioctl+0x285/0x470 Oct 01 14:52:39 pc-alvin kernel: [] ? recalc_sigpending+0x1f/0x60 Oct 01 14:52:39 pc-alvin kernel: [] ? __set_task_blocked+0x32/0x70 Oct 01 14:52:39 pc-alvin kernel: [] SyS_ioctl+0x79/0x90 Oct 01 14:52:39 pc-alvin kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Oct 01 14:52:39 pc-alvin kernel: ---[ end trace 9b3399ab2e633e05 ]--- ProblemType: Bug DistroRelease: Ubuntu 1
[Kernel-packages] [Bug 1501760] Re: ftdi USB<->TTL adapter stops working with 3.13.0-65-generic
benpicco, as per http://www.asrock.com/mb/Intel/H81M- DGS%20R2.0/?cat=Download&os=BIOS an update to your computer's buggy and outdated BIOS is available (1.60). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-160 ** Tags removed: bios-outdated-160 ** Tags added: bios-outdated-1.60 regression-update ** Changed in: linux (Ubuntu) Status: Triaged => 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/1501760 Title: ftdi USB<->TTL adapter stops working with 3.13.0-65-generic Status in linux package in Ubuntu: Incomplete Bug description: After yesterday's update I'm unable to connect to /dev/ttyUSB0, works fine when I boot 3.13.0-63-generic Affected devices: Bus 003 Device 005: ID 0403:bcda Future Technology Devices International, Ltd Stellaris ICDI Board Bus 003 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC This has already been reported as a bug in Python, but it doesn't just affect Python programs but everything trying to access the device. https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1501240 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-65-generic 3.13.0-65.105 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benpicco 2661 F pulseaudio /dev/snd/controlC0: benpicco 2661 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 1 15:21:24 2015 HibernationDevice: RESUME=UUID=9b23d804-46bf-4b3b-a691-2b45363a9d0e InstallationDate: Installed on 2014-09-22 (374 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed root=UUID=67abec1c-41a2-45e9-8772-4a5930f9e310 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-65-generic N/A linux-backports-modules-3.13.0-65-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H81M-DGS R2.0 dmi.board.vendor: ASRock 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.:bvrP1.30:bd07/02/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-DGSR2.0:rvr: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/1501760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501736] Re: Kernel lock up on reboot/shutdown since upgrade
Chris Clarke, as per http://people.canonical.com/~kernel/info/kernel- version-map.html testing mainline 3.19.8 is similar to testing Ubuntu-3.19.0-20.20. As you noted this is a regression in Ubuntu kernel version going from 3.19.0-28 to 3.19.0-30, will the bug not being reproduced with that kernel was expected, the criteria for kernel-fixed- upstream has not been met as outlined in https://wiki.ubuntu.com/Bugs/Tags . Despite this, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Tags removed: kernel-fixed-upstream ** Tags added: needs-upstream-testing ** Tags added: bios-outdated-a05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501736 Title: Kernel lock up on reboot/shutdown since upgrade Status in linux package in Ubuntu: Incomplete Bug description: When trying to shut down or reboot the system, the system freezes and is not responsive. A kernel error is shown on the screen (I will attach after posting this) This is with the radeon module. When reverting back to 3.19.0-28 this works as expected. I'm using XUbuntu 15.04 - fully updated. This is my first bug report, so please be gentle. I'll endeavor to attach and do whatever is needed to provide the right information but I'm currently a little lost in this whole process. Chris. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cclarke1469 F pulseaudio /dev/snd/controlC1: cclarke1469 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=b3f4c068-1eb6-4038-9604-82237679d7a2 InstallationDate: Installed on 2015-09-18 (13 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: Dell Inc. Inspiron 7548 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0AM6R0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/13/2015:svnDellInc.:pnInspiron7548:pvrA04:rvnDellInc.:rn0AM6R0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482273] Re: Dell Ubuntu 3551: failure to boot without nolapic option
** Tags removed: confirmed ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.3-rc3 ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482273 Title: Dell Ubuntu 3551: failure to boot without nolapic option Status in linux package in Ubuntu: Triaged Bug description: This laptop came with Ubuntu 14.04 preinstalled. It is a Dell Inspiron 3551 15" Ubuntu Laptop. A problem was introduced in the linux- image-3.13.0-58-generic kernel update which prevents the laptop from booting unless nolapic is added to the grub boot command. This problem persists in the current latest stable ubuntu kernel linux- image-3.13.0-61-generic. This bug affects a clean, factory restored install. The system passes all of Dell's included hardware diagnostic tests. Boot fails with: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0009 The following kernels are able to boot without issue: linux-image-3.13.0-57-generic linux-image-3.13.0-55-generic linux-image-3.13.0-38-generic Please let me know if I can be of further assistance. lsb_release: Ubuntu 14.04.3 LTS Thanks, Mark Standridge ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 2223 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 6 10:24:22 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=00b41433-b7f7-4ddb-83c4-fca2ea939b57 InstallationDate: Installed on 2015-06-18 (48 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=a4f79951-02f5-41f5-aa89-e4f77082c51f ro nolapic quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0CMF7W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn0CMF7W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
chris pollock, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** 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/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Incomplete Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] tarf (amd64) - tests ran: 197, failed: 2
tests ran: 197, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-14.16/tarf__4.2.0-14.16__2015-10-02_20-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501431] Re: Various i915 Intel display driver crashes reported on syslog
Eric Carvalho, if all the mainline kernels boot, then it indicates a downstream Ubuntu patch that is causing this issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501431 Title: Various i915 Intel display driver crashes reported on syslog Status in linux package in Ubuntu: Triaged Bug description: Computer: Dell Latitude E5440. Ubuntu: 15.10 Kernel: 4.2.0-12-generic The following error messages are logged at system startup, although there seems to be no side effects (i.e. everything works): [4.426224] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [4.426227] [ cut here ] [4.426240] WARNING: CPU: 0 PID: 293 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() [4.426241] pipe state doesn't match! [4.426242] Modules linked in: arc4 dell_wmi sparse_keymap dell_laptop dcdbas uvcvideo intel_rapl dell_smm_hwmon iosf_mbi x86_pkg_temp_thermal videobuf2_vmalloc btusb intel_powerclamp snd_hda_codec_hdmi btrtl kvm_intel btbcm videobuf2_memops snd_hda_codec_realtek btintel videobuf2_core snd_hda_codec_generic v4l2_common bluetooth kvm iwlmvm mac80211 videodev snd_hda_intel crct10dif_pclmul media crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core snd_hwdep aesni_intel snd_pcm aes_x86_64 lrw gf128mul snd_seq_midi glue_helper iwlwifi ablk_helper snd_seq_midi_event cryptd snd_rawmidi snd_seq snd_seq_device cfg80211 snd_timer joydev input_leds serio_raw snd soundcore mei_me lpc_ich shpchp mei 8250_fintek dell_rbtn dell_smo8800 mac_hid coretemp parport_pc ppdev lp parport autofs4 i915 psmouse sdhci_pci [4.426275] e1000e sdhci ahci i2c_algo_bit ptp libahci drm_kms_helper pps_core drm wmi video [4.426282] CPU: 0 PID: 293 Comm: plymouthd Not tainted 4.2.0-12-generic #14-Ubuntu [4.426283] Hardware name: Dell Inc. Latitude E5440/078YP3, BIOS A12 05/19/2015 [4.426284] c0259ab0 8800d319b7e8 817b0cd5 [4.426286] 8800d319b838 8800d319b828 81076536 8800d319b858 [4.426288] 8800d319b8c0 8801190e4800 0001 8801190e4b50 [4.426290] Call Trace: [4.426295] [] dump_stack+0x45/0x57 [4.426299] [] warn_slowpath_common+0x86/0xc0 [4.426301] [] warn_slowpath_fmt+0x46/0x50 [4.426313] [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] [4.426323] [] check_crtc_state+0x2c5/0x440 [i915] [4.426336] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [4.426348] [] intel_crtc_set_config+0x4c7/0x580 [i915] [4.426361] [] ? drm_mode_create+0x25/0x60 [drm] [4.426370] [] drm_mode_set_config_internal+0x66/0x100 [drm] [4.426379] [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] [4.426385] [] drm_ioctl+0x125/0x610 [drm] [4.426392] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [4.426396] [] do_vfs_ioctl+0x285/0x470 [4.426398] [] ? SyS_mmap_pgoff+0xe8/0x270 [4.426400] [] SyS_ioctl+0x79/0x90 [4.426403] [] entry_SYSCALL_64_fastpath+0x16/0x75 [4.426404] ---[ end trace 5386212d0bc499d7 ]--- [4.427646] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [4.427648] [ cut here ] [4.427658] WARNING: CPU: 0 PID: 293 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() [4.427659] pipe state doesn't match! [4.427660] Modules linked in: arc4 dell_wmi sparse_keymap dell_laptop dcdbas uvcvideo intel_rapl dell_smm_hwmon iosf_mbi x86_pkg_temp_thermal videobuf2_vmalloc btusb intel_powerclamp snd_hda_codec_hdmi btrtl kvm_intel btbcm videobuf2_memops snd_hda_codec_realtek btintel videobuf2_core snd_hda_codec_generic v4l2_common bluetooth kvm iwlmvm mac80211 videodev snd_hda_intel crct10dif_pclmul media crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core snd_hwdep aesni_intel snd_pcm aes_x86_64 lrw gf128mul snd_seq_midi glue_helper iwlwifi ablk_helper snd_seq_midi_event cryptd snd_rawmidi snd_seq snd_seq_device cfg80211 snd_timer joydev input_leds serio_raw snd soundcore mei_me lpc_ich shpchp mei 8250_fintek dell_rbtn dell_smo8800 mac_hid coretemp parport_pc ppdev lp parport autofs4 i915 psmouse sdhci_pci [4.427688] e1000e sdhci ahci i2c_algo_bit ptp libahci drm_kms_helper pps_core drm wmi video [4.427694] CPU: 0 PID: 293 Comm: plymouthd Tainted: GW 4.2.0-12-generic #14-Ubuntu [4.427694] Hardware name: Dell Inc. Latitude E5440/078YP3, BIOS A12 05/19/2015 [4.427696] c0259ab0 8800d319b7e8 817b0cd5 [4.427697] 8800d
[Kernel-packages] [Bug 1324095] Re: [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless
Daniel d'Andrada, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1324095 Title: [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Unknown Bug description: With the ideapad_laptop module loaded there is no wlan0 (or other wifi device) present. Booting without any explicit blacklist config the ideapad_laptop kernel module gets loaded, and there are no wlan0 device present. If I yet again load the ideapad_laptop module, using modprobe, the wlan0 device goes away. Here is the dmesg output from that. [ 234.351406] input: Ideapad extra buttons as /devices/platform/VPC2004:00/input/input17 [ 234.353261] wlan0: deauthenticating from d8:5d:4c:bb:1a:f2 by local choice (reason=3) [ 234.398900] cfg80211: Calling CRDA to update world regulatory domain [ 234.401410] cfg80211: World regulatory domain updated: [ 234.401412] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 234.401414] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 234.401415] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 234.401416] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 234.401418] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 234.401419] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 234.555068] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready WORKAROUND: For the wireless network to work on my Lenovo Yoga 2 Pro Laptop I need blacklist/rmmod the ideapad_laptop kernel module. Running rmmod on the module results in the wlan0 device becoming present, and NetworkManager being able to connect to a local wifi network. Here is the dmesg output after the rmmod command: [ 74.908411] iwlwifi :01:00.0: L1 Disabled; Enabling L0S [ 74.908627] iwlwifi :01:00.0: L1 Disabled; Enabling L0S [ 74.920538] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 76.371036] wlan0: authenticate with d8:5d:4c:bb:1a:f2 [ 76.372069] wlan0: send auth to d8:5d:4c:bb:1a:f2 (try 1/3) [ 76.376670] wlan0: authenticated [ 76.378169] wlan0: associate with d8:5d:4c:bb:1a:f2 (try 1/3) [ 76.381908] wlan0: RX AssocResp from d8:5d:4c:bb:1a:f2 (capab=0x411 status=0 aid=2) [ 76.383305] wlan0: associated [ 76.38] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas2492 F pulseaudio /dev/snd/controlC0: andreas2492 F pulseaudio CurrentDesktop: Unity Date: Wed May 28 14:00:22 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-20 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20266 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed root=UUID=e70835c5-4ffe-49d3-aecc-403dbf538c1a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900056PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900056PRO:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1324095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501623] Re: UFS rw support fails with 3.19.0-26-generic
One more log which is generated by remount command mount -t ufs -o ufstype=ufs2,remount,rw /dev/nbd0p2 /mnt Fyi. ** Attachment added: "another syslog when remount ufs with rw" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501623/+attachment/4482483/+files/report.jenkins1.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/1501623 Title: UFS rw support fails with 3.19.0-26-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Vivid: Incomplete Bug description: Hi guys, I'd like to enable rw support for ufs file system with kernel 3.19.0-26-generic. Basically, I follow steps as below from http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support- debian/ sudo apt-get build-dep --no-install-recommends linux-image-$(uname -r) mkdir ufs_rw cd ufs_rw apt-get source linux-image-$(uname -r) cp -v /usr/src/linux-headers-$(uname -r)/Module.symvers . cd linux-*/ cp -v /boot/config-$(uname -r) . make EXTRAVERSION=-4 O=~/ufs_rw oldconfig sed -i 's/# CONFIG_UFS_FS_WRITE is not set/CONFIG_UFS_FS_WRITE=y/' ~/ufs_rw/.config make EXTRAVERSION=-4 O=~/ufs_rw prepare make EXTRAVERSION=-4 O=~/ufs_rw outputmakefile make EXTRAVERSION=-4 O=~/ufs_rw archprepare make EXTRAVERSION=-4 O=~/ufs_rw modules SUBDIRS=scripts make EXTRAVERSION=-4 O=~/ufs_rw modules SUBDIRS=fs/ufs I get ufs.ko under ufs_rw/fs/ufs and try it with below commands. modprobe nbd qemu-nbd -c /dev/nbd0 freebsd10u1x64 mount -t ufs -o ufstype=ufs2,rw /dev/nbd0p2 /mnt There is no error or warning when I run mount -t ufs -o ufstype=ufs2,rw /dev/nbd0p2 /mnt However, when I try to write something to /mnt or even umount /mnt, there is kernel panic. And further more, the way above works for 3.8.0-34-generic/3.11.0-26-generic. That means I can read/write correctly with ufs2 file system. It breaks with 3.19.0-26-generic, from my view. Please let me know if more info is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 922037] Re: 10de:1057 "reduce brightness" key freezes system
Andreas Hasenack, while that's fine you provided some new information, nothing has really changed regarding this report as it is still missing the information requested 2+ years ago in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922037/comments/23 . ** Tags removed: bios-outdated-1.46 ** Tags added: latest-bios-1.46 ** Tags added: vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/922037 Title: 10de:1057 "reduce brightness" key freezes system Status in linux package in Ubuntu: Incomplete Bug description: When I have the Nvidia discrete graphics selected in the bios, pressing the "reduce brightness" key (blue fn + end), the system freezes. It doesn't matter if I'm in X or in text mode, it happens all the time. I did it while watching the logs (/var/log/syslog, ~/.xsession-errors) and even the debug console when in text mode (F8 iirc), but nothing was written there. The machine was also unreachable from the network after the fact. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13 Uname: Linux 3.0.0-15-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas2535 F pulseaudio /dev/snd/controlC0: andreas2535 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf532 irq 46' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa21ce,0012' Controls : 9 Simple ctrls : 6 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf300 irq 17' Mixer name : 'Nvidia GPU 1c HDMI/DP' Components : 'HDA:10de001c,17aa21ce,00100100' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] 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: Thu Jan 26 09:44:29 2012 HibernationDevice: RESUME=UUID=0e0159cb-88a6-4653-9902-6c3934f00ef7 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: LENOVO 4177CTO ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-15-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-15-generic N/A linux-backports-modules-3.0.0-15-generic N/A linux-firmware1.60 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO 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:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296224] Re: Horrible noise via DisplayPort [regression]
Andreas Schildbach, the mailing list address as per the wiki references to http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS which states : intel-...@lists.freedesktop.org -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296224 Title: Horrible noise via DisplayPort [regression] Status in linux package in Ubuntu: Triaged Bug description: This issue has been present and fixed two years ago and with Trusty Tahr it re-appeared: When logging in and my display is extended to two monitors, and also when the screen blanks, I get 3-5 seconds of horrible noise via DisplayPort audio out. The noise is loud enough to damage ears and loudspeakers, if volume has been set to a normal listening level. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 23 10:18:08 2014 DistUpgraded: 2014-01-03 23:25:11,434 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2011-08-05 (960 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MachineType: LENOVO 29123AG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=b9fb2d9e-d248-4294-bd6b-9abe27dfcea4 ro quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-01-03 (78 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 29123AG 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:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn29123AG:pvrThinkPadT410s:rvnLENOVO:rn29123AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 29123AG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Mar 23 10:09:13 2014 xserver.configfile: default xserver.errors: N-Trig Pen stylus: Invalid type 'cursor' for this device. N-Trig Pen stylus: Invalid type 'touch' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16438 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328727] Re: [Asus 1000HE] s2disk/hibernate hangs during saving of image data
Javier Fernández Aparicio / effell, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328727 Title: [Asus 1000HE] s2disk/hibernate hangs during saving of image data Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hibernation with the pm-hibernate command works fine on a freshly booted system, but when a significant portion of the RAM is in use, for instance by starting gimp, google-chrome and firefox at the same time, it stalls at the start of the saving of the image data: s2disk: Snapshotting system s2disk: System snapshot ready. Preparing to write s2disk: Image size: 441652 kilobytes s2disk: Free swap: 1798624 kilobytes s2disk: Saving 110413 image data pages (press backspace to abort) ... 0% The system is not usable at this point, although alt-sysrq still works. It looks like some sort of deadlock. The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04 LTS. The kernel package is linux-image-3.13.0-27-generic version 3.13.0-27.50 (32 bit). I found a kernel bug report that looks exactly the same: https://bugzilla.kernel.org/show_bug.cgi?id=75101 In that bug report, the problem was bisected to commit a1c3bfb2. This commit is part of the 3.14 kernel, but was apparently backported to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this commit reverted, and it seems to fix this issue for me. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dick 1719 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c6b78f80-b4a1-4b1a-91b4-8ae5c41b36f4 InstallationDate: Installed on 2013-04-28 (408 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: ASUSTeK Computer INC. 1000HE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=54684f57-2a33-403f-ae4d-ad6b3d0168ea ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-27.50hib-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-26 (45 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000HE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/24/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000HE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1328727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
@Fredrik Jonson (fredrik-jonson), @Sean Sosik-Hamor (sciri) : In the original bad kernel, 3.19.0-30.33, if I typed many characters (maybe 30) and some carriage returns. the text did show up as described by @Fredrik Jonson (fredrik-jonson) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] onibi (i386) - tests ran: 167, failed: 0
tests ran: 167, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-14.16/onibi__4.2.0-14.16__2015-10-02_23-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498307] cavac (amd64) - tests ran: 66, failed: 66
tests ran: 66, failed: 66; http://kernel.ubuntu.com/testing/3.19.0-30.33~14.04.1/cavac__3.19.0-30.33~14.04.1__2015-10-03_01-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1498307 Title: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC kernel-stable-master-bug:1498065 kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501345] Re: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication
Broke Python serial with RFCOMM bluetooth binding. ** No longer affects: weewx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65 Kernel on Lubuntu 14.04.3 LTS two different programs that rely on PySerial quit working. miniterm.py and my ROS (Robot Operating System) based Python node quit working. When rebooted and selected 3.13.0-63-generic via GRUB everything worked again. Here are the steps to create the issue with miniterm.py, note that you need something connected via a USB to Serial adapter for this to work. I am working with a Parallax Activity Board, but an Arduino should also exhibit the same behavior. sudo apt install linux-image-3.13.0-65-generic sudo apt install linux-image-extra-3.13.0-65-generic reboot $ miniterm.py /dev/ttyUSB0 115200 --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- --- exit --- Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/bin/miniterm.py", line 220, in reader data = character(self.serial.read(1)) File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in read raise SerialException('device reports readiness to read but returned no data (device disconnected?)') SerialException: device reports readiness to read but returned no data (device disconnected?) Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python Serial based programs to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] fozzie (i386) - tests ran: 167, failed: 0
tests ran: 167, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-14.16/fozzie__4.2.0-14.16__2015-10-02_23-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501345] Re: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication
** Also affects: weewx Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication Status in Weewx: New Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65 Kernel on Lubuntu 14.04.3 LTS two different programs that rely on PySerial quit working. miniterm.py and my ROS (Robot Operating System) based Python node quit working. When rebooted and selected 3.13.0-63-generic via GRUB everything worked again. Here are the steps to create the issue with miniterm.py, note that you need something connected via a USB to Serial adapter for this to work. I am working with a Parallax Activity Board, but an Arduino should also exhibit the same behavior. sudo apt install linux-image-3.13.0-65-generic sudo apt install linux-image-extra-3.13.0-65-generic reboot $ miniterm.py /dev/ttyUSB0 115200 --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- --- exit --- Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/bin/miniterm.py", line 220, in reader data = character(self.serial.read(1)) File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in read raise SerialException('device reports readiness to read but returned no data (device disconnected?)') SerialException: device reports readiness to read but returned no data (device disconnected?) Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python Serial based programs to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/weewx/+bug/1501345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493579] Re: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
** Changed in: linux-lts-vivid (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-lts-vivid (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: linux-lts-vivid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1493579 Title: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux-lts-vivid package in Ubuntu: Fix Released Bug description: 14.04 Lubuntu on old Gateway M275. E: Sub-process /usr/bin/dpkg returned an error code (1) No documented fix seems to FIX, the download says failed on several files, I have tried different servers, and no extra repositorie. I like ubuntu, but until we get past this sort of thing that even causes IT people a bit of pain its not going to kill windows. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-28-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 Date: Tue Sep 8 17:20:17 2015 DpkgTerminalLog: Preparing to unpack .../linux-image-3.19.0-28-generic_3.19.0-28.30~14.04.1_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.19.0-28-generic_3.19.0-28.30~14.04.1_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 DuplicateSignature: package:linux-image-3.19.0-28-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-31 (8 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1493579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493579] Re: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1493579 Title: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux-lts-vivid package in Ubuntu: Fix Released Bug description: 14.04 Lubuntu on old Gateway M275. E: Sub-process /usr/bin/dpkg returned an error code (1) No documented fix seems to FIX, the download says failed on several files, I have tried different servers, and no extra repositorie. I like ubuntu, but until we get past this sort of thing that even causes IT people a bit of pain its not going to kill windows. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-28-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 Date: Tue Sep 8 17:20:17 2015 DpkgTerminalLog: Preparing to unpack .../linux-image-3.19.0-28-generic_3.19.0-28.30~14.04.1_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.19.0-28-generic_3.19.0-28.30~14.04.1_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 DuplicateSignature: package:linux-image-3.19.0-28-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-31 (8 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1493579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501623] Re: UFS rw support fails with 3.19.0-26-generic
Sorry for late reply. Attach call stack from var/log/syslog. Please help review it. ** Attachment added: "syslog with ufs rw enabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501623/+attachment/4482445/+files/report.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/1501623 Title: UFS rw support fails with 3.19.0-26-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Vivid: Incomplete Bug description: Hi guys, I'd like to enable rw support for ufs file system with kernel 3.19.0-26-generic. Basically, I follow steps as below from http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support- debian/ sudo apt-get build-dep --no-install-recommends linux-image-$(uname -r) mkdir ufs_rw cd ufs_rw apt-get source linux-image-$(uname -r) cp -v /usr/src/linux-headers-$(uname -r)/Module.symvers . cd linux-*/ cp -v /boot/config-$(uname -r) . make EXTRAVERSION=-4 O=~/ufs_rw oldconfig sed -i 's/# CONFIG_UFS_FS_WRITE is not set/CONFIG_UFS_FS_WRITE=y/' ~/ufs_rw/.config make EXTRAVERSION=-4 O=~/ufs_rw prepare make EXTRAVERSION=-4 O=~/ufs_rw outputmakefile make EXTRAVERSION=-4 O=~/ufs_rw archprepare make EXTRAVERSION=-4 O=~/ufs_rw modules SUBDIRS=scripts make EXTRAVERSION=-4 O=~/ufs_rw modules SUBDIRS=fs/ufs I get ufs.ko under ufs_rw/fs/ufs and try it with below commands. modprobe nbd qemu-nbd -c /dev/nbd0 freebsd10u1x64 mount -t ufs -o ufstype=ufs2,rw /dev/nbd0p2 /mnt There is no error or warning when I run mount -t ufs -o ufstype=ufs2,rw /dev/nbd0p2 /mnt However, when I try to write something to /mnt or even umount /mnt, there is kernel panic. And further more, the way above works for 3.8.0-34-generic/3.11.0-26-generic. That means I can read/write correctly with ufs2 file system. It breaks with 3.19.0-26-generic, from my view. Please let me know if more info is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498307] cavac (i386) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-30.33~14.04.1/cavac__3.19.0-30.33~14.04.1__2015-10-03_00-41-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1498307 Title: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC kernel-stable-master-bug:1498065 kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] larsen (i386) - tests ran: 167, failed: 0
tests ran: 167, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-14.16/larsen__4.2.0-14.16__2015-10-02_21-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498307] cavac (i386) - tests ran: 2, failed: 1
tests ran: 2, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-30.33~14.04.1/cavac__3.19.0-30.33~14.04.1__2015-10-02_20-11-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1498307 Title: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC kernel-stable-master-bug:1498065 kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] fozzie (amd64) - tests ran: 194, failed: 2
tests ran: 194, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-14.16/fozzie__4.2.0-14.16__2015-10-02_20-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] onibi (amd64) - tests ran: 194, failed: 2
tests ran: 194, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-14.16/onibi__4.2.0-14.16__2015-10-02_20-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502345] 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/1502345 Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Crashed on wakiing from Suspend. Had to power off and on. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: campbell 2747 F pulseaudio /dev/snd/controlC0: campbell 2747 F pulseaudio Date: Fri Oct 2 19:24:41 2015 DuplicateSignature: suspend/resume:NOVATECH LTD PERSONAL COMPUTER:F5 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER 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-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502345] Re: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502345 Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure Status in linux package in Ubuntu: New Bug description: Crashed on wakiing from Suspend. Had to power off and on. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: campbell 2747 F pulseaudio /dev/snd/controlC0: campbell 2747 F pulseaudio Date: Fri Oct 2 19:24:41 2015 DuplicateSignature: suspend/resume:NOVATECH LTD PERSONAL COMPUTER:F5 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER 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-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502345] [NEW] [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure
Public bug reported: Crashed on wakiing from Suspend. Had to power off and on. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: campbell 2747 F pulseaudio /dev/snd/controlC0: campbell 2747 F pulseaudio Date: Fri Oct 2 19:24:41 2015 DuplicateSignature: suspend/resume:NOVATECH LTD PERSONAL COMPUTER:F5 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER 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-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops need-duplicate-check resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502345 Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure Status in linux package in Ubuntu: New Bug description: Crashed on wakiing from Suspend. Had to power off and on. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: campbell 2747 F pulseaudio /dev/snd/controlC0: campbell 2747 F pulseaudio Date: Fri Oct 2 19:24:41 2015 DuplicateSignature: suspend/resume:NOVATECH LTD PERSONAL COMPUTER:F5 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER 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-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux Title: [NOVATECH LTD PERSONAL COMPUTER] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Mega
[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613
** Description changed: - While working on KernelThreadSanitizer (KTSAN), a data race detector - for kernels, Dmitry Vyukov found a data race that can trick the kernel - into using uninitialized memory. - - This can at least give access to arbitrary SysV shared memory and - Dmitry developed a proof of concept exploit for this. (On many - systems, this can be used to escalate privileges). - - While we didn't investigate this deeply, it is almost certain that - this vulnerability can be used to gain arbitrary code execution in the + While working on KernelThreadSanitizer (KTSAN), a data race detector for + kernels, Dmitry Vyukov found a data race that can trick the kernel into + using unitialized memory. - This can at least give access to arbitrary + SysV shared memory and Dmitry developed a proof of concept exploit for + this. (On many systems, this can be used to escalate privileges). - + While we didn't investigate this deeply, it is almost certain that this + vulnerability can be used to gain arbitrary code execution in the kernel. Exercise left to the reader. Break-Fix: - b9a532277938798b53178d5a66af6e2915cb27cf -- 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/1502032 Title: CVE-2015-7613 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
Any of you noticed a decreasing signal with this driver, with the same machine and os (Ubuntu 14.04) i had a decrease on wifi signal (and wifi is still the same i checked it) any of you noticed about this? -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] Re: linux: 4.2.0-14.16 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502238] Re: bridge does not forward neighbor solicitation packets
** 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/1502238 Title: bridge does not forward neighbor solicitation packets Status in linux package in Ubuntu: Triaged Bug description: 3 hosts involved here: kailan is connected to a cisco switch, which is also connected to kurrat (eth3), which is running a bridge with tigernut connected to eth1. kurrat's controllers are 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection, using the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 ^C 10 packets captured 11 packets received by filter 0 packets dropped by kernel +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast listener query v2 [gaddr ::], length 28 10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel 1 packet dropped by interface +kurrat 326 : uname -a Linux kurrat 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Adding a host route for the 2001:: IP via the link IP on kailan works as a workaround, but the neighbor solicitiation packets are clearly not getting through the bridge. No firewall is configured on kurrat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502238] Re: bridge does not forward neighbor solicitation packets
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502238 Title: bridge does not forward neighbor solicitation packets Status in linux package in Ubuntu: Triaged Bug description: 3 hosts involved here: kailan is connected to a cisco switch, which is also connected to kurrat (eth3), which is running a bridge with tigernut connected to eth1. kurrat's controllers are 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection, using the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 ^C 10 packets captured 11 packets received by filter 0 packets dropped by kernel +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast listener query v2 [gaddr ::], length 28 10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel 1 packet dropped by interface +kurrat 326 : uname -a Linux kurrat 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Adding a host route for the 2001:: IP via the link IP on kailan works as a workaround, but the neighbor solicitiation packets are clearly not getting through the bridge. No firewall is configured on kurrat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482273] Re: Dell Ubuntu 3551: failure to boot without nolapic option
** Tags added: confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482273 Title: Dell Ubuntu 3551: failure to boot without nolapic option Status in linux package in Ubuntu: Confirmed Bug description: This laptop came with Ubuntu 14.04 preinstalled. It is a Dell Inspiron 3551 15" Ubuntu Laptop. A problem was introduced in the linux- image-3.13.0-58-generic kernel update which prevents the laptop from booting unless nolapic is added to the grub boot command. This problem persists in the current latest stable ubuntu kernel linux- image-3.13.0-61-generic. This bug affects a clean, factory restored install. The system passes all of Dell's included hardware diagnostic tests. Boot fails with: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0009 The following kernels are able to boot without issue: linux-image-3.13.0-57-generic linux-image-3.13.0-55-generic linux-image-3.13.0-38-generic Please let me know if I can be of further assistance. lsb_release: Ubuntu 14.04.3 LTS Thanks, Mark Standridge ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 2223 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 6 10:24:22 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=00b41433-b7f7-4ddb-83c4-fca2ea939b57 InstallationDate: Installed on 2015-06-18 (48 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=a4f79951-02f5-41f5-aa89-e4f77082c51f ro nolapic quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0CMF7W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn0CMF7W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
@Fredrik Jonson (fredrik-jonson): Yes, in the original bug I reported, there was no input possible at all -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
You can add one more XPS 13 to the list of affected systems. I'm about to EOD but can also test additional kernels starting on Monday. All my system info attached to duplicate LP Bug #1502171. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613
** Description changed: - While working on KernelThreadSanitizer (KTSAN), a data race detector for - kernels, Dmitry Vyukov found a data race that can trick the kernel into - using unitialized memory. - This can at least give access to arbitrary - SysV shared memory and Dmitry developed a proof of concept exploit for - this. (On many systems, this can be used to escalate privileges). - - While we didn't investigate this deeply, it is almost certain that this - vulnerability can be used to gain arbitrary code execution in the + While working on KernelThreadSanitizer (KTSAN), a data race detector + for kernels, Dmitry Vyukov found a data race that can trick the kernel + into using uninitialized memory. + - This can at least give access to arbitrary SysV shared memory and + Dmitry developed a proof of concept exploit for this. (On many + systems, this can be used to escalate privileges). + - While we didn't investigate this deeply, it is almost certain that + this vulnerability can be used to gain arbitrary code execution in the kernel. Exercise left to the reader. Break-Fix: - b9a532277938798b53178d5a66af6e2915cb27cf -- 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/1502032 Title: CVE-2015-7613 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
** Attachment added: "kern.log from 02102015 freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4482288/+files/kernlog10022015.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/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Confirmed Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
** Attachment added: "syslog from 02102015 freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4482287/+files/syslog10022015.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/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Confirmed Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
** Attachment added: "gpu-manager.log from 02102015 freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4482286/+files/gpumanagerlog10022015.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/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Confirmed Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
** Attachment added: "dmesg from 02102015 freeze after reboot." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4482289/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Confirmed Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481039] Re: CVE-2015-5697
** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Invalid -- 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/1481039 Title: CVE-2015-5697 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package
[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Tested version 3.19.0-29.31~lp1500751Commit50031c9d and it also/still has the bug. This time it was slightly different compared to how I recall it from the original case. I still cannot enter text in the cryptsetup area, but rather than emitting the password at the upper left corner of the same virtual console, the text appears in another virtual console - the same where the systemd version is printed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.
Today, 2 Oct 2015 at 12:39:07 video froze again. Mouse cursor would move can't switch to any windows. Uptime at freeze was 1d20h12m. I'm attaching: Gpu-Manager.log (don't know if this means anything) kern.log syslog for today until time of reboot dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1497627 Title: Periodically video will freeze for no reason at all and no specific time between freezes. Status in linux package in Ubuntu: Confirmed Bug description: What I expect to happen is the video to not freeze every so often. What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2095 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6 InstallationDate: Installed on 2014-10-24 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LE0006476 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380025] Re: linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR
** Also affects: linux (Ubuntu Wily) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Wily) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380025 Title: linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Here is the relevant kernel config: $ grep STACKPROTECTOR /boot/config-3.16.0-22-generic CONFIG_HAVE_CC_STACKPROTECTOR=y CONFIG_CC_STACKPROTECTOR=y # CONFIG_CC_STACKPROTECTOR_NONE is not set CONFIG_CC_STACKPROTECTOR_REGULAR=y # CONFIG_CC_STACKPROTECTOR_STRONG is not set Since linux is built with gcc 4.9 in Ubuntu 14.10, it could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 3741 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 11 10:03:30 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26 IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Latitude E6520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482273] Re: Dell Ubuntu 3551: failure to boot without nolapic option
I have tested the attached patch against ubuntu kernels 3.13.0-58, 3.13.0-63, 3.13.0-64, and 3.13.0-65 for over a month. Never once has this laptop suffered a kernel panic with the applied patch to reinstate the optimization to stepwise.c. It has never failed to boot. As I said earlier, I found the origin of the regression through a git bisect. I also have tested the latest upstream kernel, version 4.3.0-040300rc3-generic #201509271225. It has no issue booting. Looking at: https://github.com/torvalds/linux/blob/master/drivers/thermal/step_wise.c I see that the commit which introduces this issue has not been applied upstream. Probably because commit 178c2490b99f898efc06d1ad75cadc84f13021a6 (thermal: step_wise: Revert optimization) is not needed due to 8c8dd64345ba2a8c41556095c7adacb1c8af7c1 ("acerhdf: Use bang-bang thermal governor") fixing the issue for the fan control upstream. So the issue I'm experiencing is not so much fixed upstream, as rather it never existed upstream. I do have an old Acer Aspire 1410 which uses the acerhdf fan control module if you would like assistance in testing a backport of 8c8dd64345ba2a8c41556095c7adacb1c8af7c1 ("acerhdf: Use bang-bang thermal governor") to 3.13.0. Ubuntu kernel 3.13.0-65-generic is still unable to reliably boot without a kernel panic. Thanks ** Attachment added: "reinstate the optimization to stepwise.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482273/+attachment/4482285/+files/patch ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482273 Title: Dell Ubuntu 3551: failure to boot without nolapic option Status in linux package in Ubuntu: Incomplete Bug description: This laptop came with Ubuntu 14.04 preinstalled. It is a Dell Inspiron 3551 15" Ubuntu Laptop. A problem was introduced in the linux- image-3.13.0-58-generic kernel update which prevents the laptop from booting unless nolapic is added to the grub boot command. This problem persists in the current latest stable ubuntu kernel linux- image-3.13.0-61-generic. This bug affects a clean, factory restored install. The system passes all of Dell's included hardware diagnostic tests. Boot fails with: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0009 The following kernels are able to boot without issue: linux-image-3.13.0-57-generic linux-image-3.13.0-55-generic linux-image-3.13.0-38-generic Please let me know if I can be of further assistance. lsb_release: Ubuntu 14.04.3 LTS Thanks, Mark Standridge ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 2223 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 6 10:24:22 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=00b41433-b7f7-4ddb-83c4-fca2ea939b57 InstallationDate: Installed on 2015-06-18 (48 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=a4f79951-02f5-41f5-aa89-e4f77082c51f ro nolapic quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0CMF7W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn0CMF7W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469315] Re: CVE-2015-4692
** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Invalid -- 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/1469315 Title: CVE-2015-4692 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source pack
[Kernel-packages] [Bug 1501818] Re: linux: 4.2.0-14.16 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492193] Re: CVE-2015-6666
** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Invalid -- 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/1492193 Title: CVE-2015- Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in linux-lt
[Kernel-packages] [Bug 1489314] Re: CVE-2015-6252
** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Invalid -- 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/1489314 Title: CVE-2015-6252 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package
[Kernel-packages] [Bug 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
We use the vm86() system call extensively with our applications, primarily for performance reasons with DOS binaries that cannot be changed. Switching to CPU emulation is not possible as the applications run considerably slower than if using the hardware features of the real CPU. For this very same reason we run only 32 bit x86 on the servers to support this single system call. Of course the answer could be proposed that we compile our own kernels with this feature enabled, but this is in a production environment running stable existing software for business and not some desktop PC to just run DOS games, so we really need kernels with a proper provenance. Again for performance reasons we track the very latest hardware and chipsets, so it means we usually have to use the hardware enablement stack for LTS 14.04, currently this is based on kernel 3.19 and runs vm86() syscalls just fine out of the box, but soon the Wily based kernel 4.2 will be used for that. Kernel 4.2 in Wily has the vm86() syscall compile time disabled at present. If you could change the Kconfig to allow vm86() to be runtime enabled that would be the ideal solution and remove the regression. I suspect that you might want to backport this simple patch to set the runtime default to disabled https://github.com/torvalds/linux/commit/76fc5e7b2355af167dea1a32e93c57fc37900a5b I can only hope you understand the importance of this to our business, if this isn't fixed we will be unable to update our servers and also that they wouldn't be viable without the full x86 support for the vm86() syscall. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 Status in linux package in Ubuntu: Triaged Bug description: In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://www.spinics.net/lists/linux-tip-commits/msg30360.html the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502055] Re: Crypt password screen not responding
I've applied workaround and till now the issue did not appear. I've removed from /etc/default/grub options spash and quiet from the GRUB_CMDLINE_LINUX_DEFAULT. used: # sudo update-grub to apply changes and now the "nice" screen promping for password is not showing up. The issue also is not appearing. I've notice that when I removed that option temporary by editing GRUB options during start (via e) I did not hit this issue. This would indicate that the problem is with the graphical env for the crypt screen. Not sure if this will help anyone but this is what I've got. Regards, Peter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Confirmed Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498307] cavac (amd64) - tests ran: 2, failed: 1
tests ran: 2, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-30.33~14.04.1/cavac__3.19.0-30.33~14.04.1__2015-10-02_16-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1498307 Title: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC kernel-stable-master-bug:1498065 kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489314] Re: CVE-2015-6252
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489314 Title: CVE-2015-6252 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-b
[Kernel-packages] [Bug 1484793] Re: CVE-2015-5156
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: [virt-io max-skb-frags heap overflow] + + Break-Fix: - 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 -- 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/1484793 Title: CVE-2015-5156 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Inval
[Kernel-packages] [Bug 1489318] Re: CVE-2015-6526
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed => Fix Released ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489318 Title: CVE-2015-6526 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Inval
[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484799 Title: CVE-2015-5707 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty
[Kernel-packages] [Bug 1496232] Re: CVE-2015-6937
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1496232 Title: CVE-2015-6937 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in
[Kernel-packages] [Bug 1499606] Re: CVE-2015-5257
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: [USB: whiteheat: potential null-deref at probe] + + Break-Fix: - cbb4be652d374f64661137756b8f357a1827d6a4 -- 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/1499606 Title: CVE-2015-5257 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-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux
[Kernel-packages] [Bug 1499609] Re: CVE-2015-5283
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: [Creating multiple sockets when SCTP module isn't loaded leads to kernel panic] + + Break-Fix: 4db67e808640e3934d82ce61ee8e2e89fd877ba8 + 8e2d61e0aed2b7c4ecb35844fe07e0b2b762dee4 -- 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/1499609 Title: CVE-2015-5283 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-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily:
[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: While working on KernelThreadSanitizer (KTSAN), a data race detector for kernels, Dmitry Vyukov found a data race that can trick the kernel into using unitialized memory. - This can at least give access to arbitrary SysV shared memory and Dmitry developed a proof of concept exploit for this. (On many systems, this can be used to escalate privileges). - While we didn't investigate this deeply, it is almost certain that this vulnerability can be used to gain arbitrary code execution in the kernel. Exercise left to the reader. + + Break-Fix: - b9a532277938798b53178d5a66af6e2915cb27cf -- 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/1502032 Title: CVE-2015-7613 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: In
[Kernel-packages] [Bug 1502302] 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/1502302 Title: general protection fault: [#1] SMP Status in linux package in Ubuntu: Confirmed Bug description: Had some issues, the computer locked a couple of times. May or may not be related to this, as there was another error with Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-12-generic 4.2.0-12.14 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2466 F pulseaudio jose 3166 F pulseaudio /dev/snd/controlC0: gdm2466 F pulseaudio jose 3166 F pulseaudio Date: Fri Oct 2 19:54:40 2015 Failure: oops HibernationDevice: RESUME=UUID=be9ce8a7-7662-4da6-810c-14ff26282803 InstallationDate: Installed on 2014-02-04 (605 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic.efi.signed root=UUID=d7bcaffd-60e1-4fef-93fb-3d73a8d18907 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: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: Upgraded to wily on 2015-10-01 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499612] Re: CVE-2015-7312
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: [Use-after-free in Linux kernel with aufs mmap patch] + + Break-Fix: - local-2015-7312-fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1499612 Title: CVE-2015-7312 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily
[Kernel-packages] [Bug 1502302] [NEW] general protection fault: 0000 [#1] SMP
Public bug reported: Had some issues, the computer locked a couple of times. May or may not be related to this, as there was another error with Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-12-generic 4.2.0-12.14 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2466 F pulseaudio jose 3166 F pulseaudio /dev/snd/controlC0: gdm2466 F pulseaudio jose 3166 F pulseaudio Date: Fri Oct 2 19:54:40 2015 Failure: oops HibernationDevice: RESUME=UUID=be9ce8a7-7662-4da6-810c-14ff26282803 InstallationDate: Installed on 2014-02-04 (605 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic.efi.signed root=UUID=d7bcaffd-60e1-4fef-93fb-3d73a8d18907 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: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: Upgraded to wily on 2015-10-01 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops kernel-driver-cifs kernel-oops wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502302 Title: general protection fault: [#1] SMP Status in linux package in Ubuntu: Confirmed Bug description: Had some issues, the computer locked a couple of times. May or may not be related to this, as there was another error with Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-12-generic 4.2.0-12.14 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2466 F pulseaudio jose 3166 F pulseaudio /dev/snd/controlC0: gdm2466 F pulseaudio jose 3166 F pulseaudio Date: Fri Oct 2 19:54:40 2015 Failure: oops HibernationDevice: RESUME=UUID=be9ce8a7-7662-4da6-810c-14ff26282803 InstallationDate: Installed on 2014-02-04 (605 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic.efi.signed root=UUID=d7bcaffd-60e1-4fef-93fb-3d73a8d18907 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: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: Upgraded to wily on 2015-10-01 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447364] Re: CVE-2014-9717
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: [USERNS allows circumventing MNT_LOCKED] + + Break-Fix: - e0c9c0afd2fc958ffa34b697972721d81df8a56f -- 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/1447364 Title: CVE-2014-9717 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: N
[Kernel-packages] [Bug 1492189] Re: CVE-2015-0272
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: remote DoS using IPv6 RA with bogus MTU + + Break-Fix: - 77751427a1ff25b27d47a4c36b12c3c8667855ac -- 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/1492189 Title: CVE-2015-0272 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Inv
[Kernel-packages] [Bug 1500860] Re: 3.13.0-65 upgrade vs. usb serial adapter
Based on this thread, it looks like the fix is on the way: https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg137245.html but I don't know how long these things take to go "live". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1500860 Title: 3.13.0-65 upgrade vs. usb serial adapter Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: affects ubuntu Hi there, I'm using Kubuntu 14.04 32bit and 64bit on two different machines. Doing embedded programming on a daily base, I'm using USB to serial adapters based on the CP2102 IC. No problem so far. Today (September 29th) I upgraded both computers from 3.13.0-63 to 3.13.0-65 as usual with this command and passwd: sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get dist-upgrade -y After this and reboot, on both machines none of my several USB-serial Adapters seem to work properly. I can receive with e.g. cutecom, but I cannot send anymore. Any help will be apppreciated. Thanks Andreas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1500860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501345] Re: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication
Based on this thread, it looks like the fix is on the way: https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg137245.html but I don't know how long these things take to go "live". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65 Kernel on Lubuntu 14.04.3 LTS two different programs that rely on PySerial quit working. miniterm.py and my ROS (Robot Operating System) based Python node quit working. When rebooted and selected 3.13.0-63-generic via GRUB everything worked again. Here are the steps to create the issue with miniterm.py, note that you need something connected via a USB to Serial adapter for this to work. I am working with a Parallax Activity Board, but an Arduino should also exhibit the same behavior. sudo apt install linux-image-3.13.0-65-generic sudo apt install linux-image-extra-3.13.0-65-generic reboot $ miniterm.py /dev/ttyUSB0 115200 --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- --- exit --- Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/bin/miniterm.py", line 220, in reader data = character(self.serial.read(1)) File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in read raise SerialException('device reports readiness to read but returned no data (device disconnected?)') SerialException: device reports readiness to read but returned no data (device disconnected?) Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python Serial based programs to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501818] Re: linux: 4.2.0-14.16 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
I built the next test kernel, up to the following commit: 50031c9d633345cd2d5353fcd1ef954a0766026c The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1500751 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502171] Re: Unable to boot Dell Sputnik (XPS 13 Developer Edition) after upgrading to linux-image-3.19.0-30-generic.
*** This bug is a duplicate of bug 1500751 *** https://bugs.launchpad.net/bugs/1500751 ** This bug has been marked a duplicate of bug 1500751 Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502171 Title: Unable to boot Dell Sputnik (XPS 13 Developer Edition) after upgrading to linux-image-3.19.0-30-generic. Status in linux package in Ubuntu: Confirmed Bug description: My XPS 13 has been online for a few days on linux- image-3.19.0-28-generic and I just got around to rebooting after the linux-image-3.19.0-30-generic update. I have a BIOS password then full-disk encryption. After rebooting (both soft reboot and hard poweroff/on) I can enter my BIOS password but no longer have keyboard at the full-disk encryption unlock screen and can't enter my password. Also, nothing shows up on my external monitor with 3.19.0-30 while it does show up on 3.19.0-28. I can hit Ctrl-Alt-Del on that screen so my XPS 13 is seeing my keyboard; I just can't type my password. Rebooting, selecting Advanced, and booting into 3.19.0-28 "fixes" my system, everything works as expected. Rebooting, selecting Advanced, and booting into 3.19.0-30 exhibits the same symptoms. No keyboard or external monitor. Sometimes the full- disk encryption unlock screen doesn't even appear. Just the aubergineish colored background and nothing else shows up. Hitting Ctrl-Alt-Del reboots the system as expected. Rebooting, selecting Advanced, and booting in 3.19.0-30 recovery allows me to enter my password during the console bootup but nothing shows up on my external monitor. When I Resume the normal bootup sequence I get into Ubuntu Desktop but I have no external monitor, the system is at a constant 25% CPU across all four cores, and every keypress, click, or action is lagged by a second or two. When doing any task that involves fades (like Alt-Tab) it takes two to five seconds for each fade to finish. It took almost 30 seconds to Alt-Tab between two windows. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.33 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sciri 2284 F pulseaudio /dev/snd/controlC0: sciri 2284 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 2 09:53:35 2015 InstallationDate: Installed on 2015-07-13 (80 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=0afea0af-5fcc-489a-bb6f-37670c00aaa0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop
https://bugzilla.redhat.com/show_bug.cgi?id=1255577 other users with T450s have same problem ** Bug watch added: Red Hat Bugzilla #1255577 https://bugzilla.redhat.com/show_bug.cgi?id=1255577 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Info
[Kernel-packages] [Bug 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop
https://bugzilla.redhat.com/show_bug.cgi?id=1255577 and also me on Launchpad have the issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502155 On Launchpad I collected all bugreports regarding this issue. It exist in Fedora 23 Beta Workstation, Debian Testing, Ubuntu 15.10 Beta 2 and Daily build from 2nd Oktober -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Availabl
[Kernel-packages] [Bug 1484793] Re: CVE-2015-5156
** Changed in: linux (Ubuntu Precise) Status: Fix Committed => New ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed => New ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => New -- 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/1484793 Title: CVE-2015-5156 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-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: N
[Kernel-packages] [Bug 1501818] Re: linux: 4.2.0-14.16 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502262] Re: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502262 Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This bug happens everytime I install something. Is 3.13 a new version of the kernel? It seems to be broken. Also, if I boot up into this version through advanced options for Ubuntu from GRUB, it fails. I can boot from 3.11 or 3.12 I can't remember which one it is. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: usbmount: Remove linux-image-3.13.0-63-generic: Configure linux-image-extra-3.13.0-63-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 1810 F pulseaudio /dev/snd/controlC0: anton 1810 F pulseaudio Date: Fri Oct 2 10:50:34 2015 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9e64815e-43ec-4671-8dc7-0270be4d032a InstallationDate: Installed on 2015-03-04 (212 days ago) InstallationMedia: It MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=d978abfb-8d1b-422e-9f60-3d4e81247e47 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502262] 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/1502262 Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This bug happens everytime I install something. Is 3.13 a new version of the kernel? It seems to be broken. Also, if I boot up into this version through advanced options for Ubuntu from GRUB, it fails. I can boot from 3.11 or 3.12 I can't remember which one it is. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: usbmount: Remove linux-image-3.13.0-63-generic: Configure linux-image-extra-3.13.0-63-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 1810 F pulseaudio /dev/snd/controlC0: anton 1810 F pulseaudio Date: Fri Oct 2 10:50:34 2015 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9e64815e-43ec-4671-8dc7-0270be4d032a InstallationDate: Installed on 2015-03-04 (212 days ago) InstallationMedia: It MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=d978abfb-8d1b-422e-9f60-3d4e81247e47 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502262] [NEW] package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: This bug happens everytime I install something. Is 3.13 a new version of the kernel? It seems to be broken. Also, if I boot up into this version through advanced options for Ubuntu from GRUB, it fails. I can boot from 3.11 or 3.12 I can't remember which one it is. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: usbmount: Remove linux-image-3.13.0-63-generic: Configure linux-image-extra-3.13.0-63-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 1810 F pulseaudio /dev/snd/controlC0: anton 1810 F pulseaudio Date: Fri Oct 2 10:50:34 2015 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9e64815e-43ec-4671-8dc7-0270be4d032a InstallationDate: Installed on 2015-03-04 (212 days ago) InstallationMedia: It MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=d978abfb-8d1b-422e-9f60-3d4e81247e47 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502262 Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This bug happens everytime I install something. Is 3.13 a new version of the kernel? It seems to be broken. Also, if I boot up into this version through advanced options for Ubuntu from GRUB, it fails. I can boot from 3.11 or 3.12 I can't remember which one it is. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 AptOrdering: usbmount: Remove linux-image-3.13.0-63-generic: Configure linux-image-extra-3.13.0-63-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 1810 F pulseaudio /dev/snd/controlC0: anton 1810 F pulseaudio Date: Fri Oct 2 10:50:34 2015 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9e64815e-43ec-4671-8dc7-0270be4d032a InstallationDate: Installed on 2015-03-04 (212 days ago) InstallationMedia: It MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=d978abfb-8d1b-422e-9f60-3d4e81247e47 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/03/2013:svnD
[Kernel-packages] [Bug 1502155] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482177/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LEN
[Kernel-packages] [Bug 1502155] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482176/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.v
[Kernel-packages] [Bug 1502155] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482173/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.v
[Kernel-packages] [Bug 1502155] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482169/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.v
[Kernel-packages] [Bug 1502155] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482168/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.v
[Kernel-packages] [Bug 1502155] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482170/+files/JournalErrors.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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chas
[Kernel-packages] [Bug 1502155] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1502155/+attachment/4482175/+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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Confirmed Status in Debian: Confirmed Status in Fedora: Unknown Status in Suse: Fix Released Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.v