[Kernel-packages] [Bug 1547838] Re: ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops
Sorry for the delay in posting this. It took forever to actually show up. Here's my post to the mailing list. http://marc.info/?l=linux- usb&m=145985232019173&w=2 I've also been in contact with the maintainer off-list (he got me to test another change). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1547838 Title: ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops Status in linux package in Ubuntu: Triaged Bug description: This is a rather old USB ethernet adapter. It worked fine for me with older distributions (including Ubuntu 10.04). I noticed it causing problems after upgrading to 14.04 and stopped using it as a result (since I needed reliable USB ethernet for work). I was also not completely sure if it was this device causing the issue or interplay between this device and a number of other networking USB devices that were used at work. I'd like to use this ethernet adapter at home but the machine is running Ubuntu 14.04 and the issue persists. I have collected some information that might help. I'm happy to try more things to collect information if that will help. I'm running Ubuntu 14.04 server 64-bit. I just rebooted so I'm running the latest updates. I was told to run ubuntu-bug linux but I'm not sure how much useful stuff is included in that. I'm including the kernel log which has some bad stuff happening in it. Not sure if it got the system-freezing oops or just the errors leading up to that. It feels like a bug in the driver that corrupts memory because I see issues with network-related things (eg. a ping crashed, but the next ping didn't), leading to a full-system freeze. This machine has been happily running Ubuntu for a looong time (though it was only recently upgraded to Ubuntu 14.04, previously it had been running 10.04). I have not had stability issues with the machine but plugging in the USB Ethernet reliably makes it freeze within minutes. The symptoms also match what I saw on my machine at work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sat Feb 20 21:23:29 2016 InstallationDate: Installed on 2015-12-31 (50 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-49-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955 InstallationDate: Installed on 2015-12-31 (67 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP EliteBook 8530w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel crashkernel=384M-:128M ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 RelatedPackageVersions: linux-restricted-modules-3.19.0-49-generic N/A linux-backports-modules-3.19.0-49-generic N/A linux-firmware 1.127.20 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/08/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDV Ver. F.12 dmi.board.name: 30E7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.27 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8530w dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notificati
[Kernel-packages] [Bug 1571791] bantam (i386) - tests ran: 155, failed: 6
tests ran: 155, failed: 6; http://kernel.ubuntu.com/testing/4.4.0-21.37/bantam__4.4.0-21.37__2016-04-19_17-04-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/1571791 Title: linux: 4.4.0-21.37 -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 Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-21.37 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:Monday, 18. April 2016 18:15 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1571791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527444] Re: Intel 7260 Wifi not working on Ubuntu 15.10
[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/1527444 Title: Intel 7260 Wifi not working on Ubuntu 15.10 Status in linux package in Ubuntu: Expired Bug description: I'm unable to use my Intel 7260 Wifi card on a clean Ubuntu 15.10 install. It is able to connect to my wifi network but after a few seconds the connection stop working. The same card on the same notebook used to work without problems on Ubuntu 15.04. I'm sending below the output of lspci and dmesg. # lspci | grep Wireless 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 93) # dmesg | grep iwl [ 10.383735] iwlwifi :08:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2 [ 10.385170] iwlwifi :08:00.0: Direct firmware load for iwlwifi-7260-14.ucode failed with error -2 [ 10.390440] iwlwifi :08:00.0: loaded firmware version 25.30.13.0 op_mode iwlmvm [ 10.418883] iwlwifi :08:00.0: Detected Intel(R) Wireless N 7260, REV=0x144 [ 10.418958] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 10.419195] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 10.651196] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 10.653379] iwlwifi :08:00.0 wlp8s0: renamed from wlan0 [ 11.247868] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 11.248149] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 11.469207] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 11.469447] iwlwifi :08:00.0: L1 Enabled - LTR Enabled [ 11.913946] Modules linked in: bnep arc4 drbg ansi_cprng nls_iso8859_1 dm_crypt dell_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp dell_laptop coretemp kvm_intel dcdbas dell_smm_hwmon kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul iwlmvm glue_helper ablk_helper cryptd mac80211 serio_raw snd_hda_codec_hdmi iwlwifi cfg80211 snd_hda_codec_realtek snd_hda_codec_generic lpc_ich rtsx_pci_ms snd_usb_audio memstick snd_seq_midi snd_usbmidi_lib snd_hda_intel snd_seq_midi_event snd_hda_codec shpchp mei_me snd_hda_core snd_hwdep mei snd_rawmidi btusb btrtl btbcm btintel snd_seq snd_pcm bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops hid_multitouch videobuf2_core joydev v4l2_common videodev input_leds media snd_seq_device snd_timer snd soundcore intel_smartconnect [ 13.284231] Modules linked in: rfcomm ctr ccm bnep arc4 drbg ansi_cprng nls_iso8859_1 dm_crypt dell_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp dell_laptop coretemp kvm_intel dcdbas dell_smm_hwmon kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul iwlmvm glue_helper ablk_helper cryptd mac80211 serio_raw snd_hda_codec_hdmi iwlwifi cfg80211 snd_hda_codec_realtek snd_hda_codec_generic lpc_ich rtsx_pci_ms snd_usb_audio memstick snd_seq_midi snd_usbmidi_lib snd_hda_intel snd_seq_midi_event snd_hda_codec shpchp mei_me snd_hda_core snd_hwdep mei snd_rawmidi btusb btrtl btbcm btintel snd_seq snd_pcm bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops hid_multitouch videobuf2_core joydev v4l2_common videodev input_leds media snd_seq_device snd_timer snd [ 13.312469] Modules linked in: rfcomm ctr ccm bnep arc4 drbg ansi_cprng nls_iso8859_1 dm_crypt dell_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp dell_laptop coretemp kvm_intel dcdbas dell_smm_hwmon kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul iwlmvm glue_helper ablk_helper cryptd mac80211 serio_raw snd_hda_codec_hdmi iwlwifi cfg80211 snd_hda_codec_realtek snd_hda_codec_generic lpc_ich rtsx_pci_ms snd_usb_audio memstick snd_seq_midi snd_usbmidi_lib snd_hda_intel snd_seq_midi_event snd_hda_codec shpchp mei_me snd_hda_core snd_hwdep mei snd_rawmidi btusb btrtl btbcm btintel snd_seq snd_pcm bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops hid_multitouch videobuf2_core joydev v4l2_common videodev input_leds media snd_seq_device snd_timer snd [ 22.109657] Modules linked in: rfcomm ctr ccm bnep arc4 drbg ansi_cprng nls_iso8859_1 dm_crypt dell_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp dell_laptop coretemp kvm_intel dcdbas dell_smm_hwmon kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul iwlmvm glue_helper ablk_helper cryptd mac80211 serio_raw snd_hda_codec_hdmi iwlwifi cfg80211 snd_hda_codec_realtek snd_hda_codec_generic lpc_ich rtsx_pci_ms snd_usb_audio memstick snd_seq_midi snd_usbmidi_lib snd_hda_intel snd_seq_midi_event snd_hda_codec shpchp mei_me snd_hda_core snd_hwdep mei snd_rawmidi btusb btrtl btbcm btintel snd_seq snd_pcm bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops hid_multitouch videob
[Kernel-packages] [Bug 1547880] Re: Wireless Network Adaptor not functional using Linux Kernel 4.2.0-29
[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/1547880 Title: Wireless Network Adaptor not functional using Linux Kernel 4.2.0-29 Status in linux package in Ubuntu: Expired Bug description: Ralink RT3090 wireless adaptor not functional using kernel 4.2.0-29. Booted with kernel 4.2.0-28 and wireless adaptor worked. Able to reproduce issue by booting 4.2.0-29 kernel. Ubuntu 4.2.0-28.33-generic 4.2.8-ckt3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1562076] Re: Ubuntu freezes a few seconds after plugin a screen
** 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/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570664] Re: [ASUSTeK COMPUTER INC. N551JK] suspend/resume failure [non-free: nvidia]
Same problem after update to Ubuntu 16.04 LTS could not update to the last upstream kernel (4.6)l, got a dependency error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570664 Title: [ASUSTeK COMPUTER INC. N551JK] suspend/resume failure [non-free: nvidia] Status in linux package in Ubuntu: Incomplete Bug description: starting up the system ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: henkspi3572 F pulseaudio /dev/snd/controlC0: henkspi3572 F pulseaudio Date: Wed Mar 30 08:33:45 2016 DuplicateSignature: suspend/resume:ASUSTeK COMPUTER INC. N551JK:N551JK.203 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=53c9ffba-5991-4041-ae32-9429b25e1318 InstallationDate: Installed on 2016-01-27 (78 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. N551JK ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=3e5024c7-70c6-4e33-920b-db866ec81e35 ro onsplash init=/sbin/upstart PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. N551JK] suspend/resume failure [non-free: nvidia] UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507505] Re: NVME partition names incorrect; should be nvme0p1, not nvme0n1
** Bug watch added: Linux Kernel Bug Tracker #116991 http://bugzilla.kernel.org/show_bug.cgi?id=116991 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=116991 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1507505 Title: NVME partition names incorrect; should be nvme0p1, not nvme0n1 Status in grub-installer: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: On T460s, I tried to install the wily daily build, it could detect the nvme partition, at the end of installation, it prompt ' Unable to install GRUB in /dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: Installing grub on '/dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: grub-install does not support --no-floppy Oct 19 16:47:01 ubuntu grub-installer: info: Running chroot /target grub-install --force "/dev/nvme" Oct 19 16:47:01 ubuntu grub-installer: Installing for i386-pc platform. Oct 19 16:47:02 ubuntu grub-installer: grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. Oct 19 16:47:02 ubuntu grub-installer: error: Running 'grub-install --force "/dev/nvme"' failed. Oct 19 16:48:30 ubuntu systemd[1]: Started Session c2 of user ubuntu. Why it install to /dev/nvme, while not the /dev/nvme0n1? $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme Installing for i386-pc platform grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0 Installing for i386-pc platform grub-install: error: attempt to read or write outside of disk `hostdisk/dev/nvme0'. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0n1 Installing for i386-pc platform Inatalltion finished. No error reported. But even it's no error reported, I still cant' find any grub after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/grub-installer/+bug/1507505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507505] Re: Unable to install GRUB in /dev/nvme
Wait, the partitions on nvme devices are named /dev/nvme0n1? That's a bug in the kernel then; it should be named /dev/nvmd0p1. The 'p' is the partition separator character linux has used since the dawn of time for devices whose base name ends in a digit. ** Package changed: grub-installer (Ubuntu) => linux (Ubuntu) ** Tags added: bot-stop-nagging ** Summary changed: - Unable to install GRUB in /dev/nvme + NVME partition names incorrect; should be nvme0p1, not nvme0n1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1507505 Title: NVME partition names incorrect; should be nvme0p1, not nvme0n1 Status in grub-installer: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: On T460s, I tried to install the wily daily build, it could detect the nvme partition, at the end of installation, it prompt ' Unable to install GRUB in /dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: Installing grub on '/dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: grub-install does not support --no-floppy Oct 19 16:47:01 ubuntu grub-installer: info: Running chroot /target grub-install --force "/dev/nvme" Oct 19 16:47:01 ubuntu grub-installer: Installing for i386-pc platform. Oct 19 16:47:02 ubuntu grub-installer: grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. Oct 19 16:47:02 ubuntu grub-installer: error: Running 'grub-install --force "/dev/nvme"' failed. Oct 19 16:48:30 ubuntu systemd[1]: Started Session c2 of user ubuntu. Why it install to /dev/nvme, while not the /dev/nvme0n1? $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme Installing for i386-pc platform grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0 Installing for i386-pc platform grub-install: error: attempt to read or write outside of disk `hostdisk/dev/nvme0'. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0n1 Installing for i386-pc platform Inatalltion finished. No error reported. But even it's no error reported, I still cant' find any grub after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/grub-installer/+bug/1507505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507505] [NEW] Unable to install GRUB in /dev/nvme
You have been subscribed to a public bug: On T460s, I tried to install the wily daily build, it could detect the nvme partition, at the end of installation, it prompt ' Unable to install GRUB in /dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: Installing grub on '/dev/nvme' Oct 19 16:47:01 ubuntu grub-installer: info: grub-install does not support --no-floppy Oct 19 16:47:01 ubuntu grub-installer: info: Running chroot /target grub-install --force "/dev/nvme" Oct 19 16:47:01 ubuntu grub-installer: Installing for i386-pc platform. Oct 19 16:47:02 ubuntu grub-installer: grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. Oct 19 16:47:02 ubuntu grub-installer: error: Running 'grub-install --force "/dev/nvme"' failed. Oct 19 16:48:30 ubuntu systemd[1]: Started Session c2 of user ubuntu. Why it install to /dev/nvme, while not the /dev/nvme0n1? $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme Installing for i386-pc platform grub-install: error: cannot find a GRUB drive for /dev/nvme. Check your device.map. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0 Installing for i386-pc platform grub-install: error: attempt to read or write outside of disk `hostdisk/dev/nvme0'. $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0n1 Installing for i386-pc platform Inatalltion finished. No error reported. But even it's no error reported, I still cant' find any grub after reboot. ** Affects: grub-installer Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- Unable to install GRUB in /dev/nvme https://bugs.launchpad.net/bugs/1507505 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573864] 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/1573864 Title: "HDMI: invalid ELD buf size -1" after connecting external display Status in linux package in Ubuntu: Confirmed Bug description: dmesg shows a lot of repated "snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1" errors after connecting external UHD display over USB Type-C. Sound played over the display's speaker works fine non-the-less. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:59:48 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573863] 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/1573863 Title: Screen garbled, dmesg errors and compiz segfault after connecting external display over USB-C Status in linux package in Ubuntu: Confirmed Bug description: I resumed my DELL XPS 9350 today and connected external UHD display over USB Type-C, which caused compiz to die and a number of warnings/errors in dmesg, as well as garbling the screen on the built- in display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:52:53 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573864] [NEW] "HDMI: invalid ELD buf size -1" after connecting external display
Public bug reported: dmesg shows a lot of repated "snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1" errors after connecting external UHD display over USB Type-C. Sound played over the display's speaker works fine non- the-less. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:59:48 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573864 Title: "HDMI: invalid ELD buf size -1" after connecting external display Status in linux package in Ubuntu: New Bug description: dmesg shows a lot of repated "snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1" errors after connecting external UHD display over USB Type-C. Sound played over the display's speaker works fine non-the-less. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:59:48 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
@Alberto Milone yet , 362 driver only works if the PRIME profile set to Intel Graphics power save. If the profile is set to NVIDIA Geforce then black screen after login. With Nouveu there is no way to turn of Nvidia GeForce. 16.04 in fact ruin the PC, toast it really heat. Driver 351 run fine in 15.10 http://i.imgur.com/ubN15iq.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573863] [NEW] Screen garbled, dmesg errors and compiz segfault after connecting external display over USB-C
Public bug reported: I resumed my DELL XPS 9350 today and connected external UHD display over USB Type-C, which caused compiz to die and a number of warnings/errors in dmesg, as well as garbling the screen on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:52:53 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573863 Title: Screen garbled, dmesg errors and compiz segfault after connecting external display over USB-C Status in linux package in Ubuntu: Confirmed Bug description: I resumed my DELL XPS 9350 today and connected external UHD display over USB Type-C, which caused compiz to die and a number of warnings/errors in dmesg, as well as garbling the screen on the built- in display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cromo 2664 F pulseaudio /dev/snd/controlC0: cromo 2664 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 20:52:53 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
I can confirm that ubuntu 16.04 LTS is exhibiting this behavior with three separate bluetooth headsets (JABRA REVO 2.0, Sony MDRXB950BT, and Sennheiser Urbanite XL WIreless). 14.04, 14.10, 15.04, and 15.10 all worked quite well with no additional configuration necessary. By "worked quite well" I mean I could pair all three headsets, they would remain paired through reboots, and I could get A2DP output from each. On 16.04, in both gnome and unity, it is a hit or miss affair of pairing any of these headsets. I have a Dell XPS 15 and had zero problems prior to installing 16.04. I used the procedure in post #5, but that does not persist after reboots. I have to unpair the headset completely and then repair in order to get sound. Even then it's hit or miss, sometimes it doesn't work. I'd be happy to give more details to help resolve this. -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
Problem occurs with dell latitude e7450 4.6 kernel rc4 and latest bios a12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in One Hundred Papercuts: Confirmed Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573833] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of update-initramfs that you likely have installed is unable to work on a persistent usb stick. You can resolve this issue by upgrading the version of casper on your system. This can be done via the commands: sudo apt-get update; sudo apt-get install casper Then performing the software update or installation that you were originally trying. If this does not resolve your bug please set its status back to New. Thanks in advance! ** Tags added: needs-new-casper ** Changed in: bcmwl (Ubuntu) Status: Confirmed => Invalid -- 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/1573833 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in bcmwl package in Ubuntu: Invalid Bug description: While installing Ubuntu Gnome 16.04 from scratch, so it didn't install, got this error and the installation was interrupted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 22:21:44 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1573833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
I have similar experiences since I upgraded from Ubuntu 15.10 to 16.04. I can no longer suspend or hibernate, the screen goes black but the PC stays on, heating up and triggering the fan after a while. When I run Ubuntu 16.04 with kernel 4.2.0-35-generic (which was still installed) instead of kernel 4.4.0-21-generic, the problem does not occur, so I've uninstalled 4.4.0-21-generic for now until there's a better solution. I have no kernel versions in between available in my package manager. Ubuntu 16.04 xenial (x86-64) Cinnamon 2.8.6 Kernel 4.4.0-21-generic Processor AMD A8-5550M APU with Radeon(tm) HD Graphics x 2 7.0 GiB memory 315 GB hard disks Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8550G] (prog-if 00 [VGA controller]) graphics card No proprietary drivers in use For completeness: unlike suspend, hibernate has never worked perfectly (screen would stay black after resume, workaround to wake up screen was suspend and resume from suspend) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Incomplete Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d
Sorry, I don't think there's any possible way to do it. The machine won't boot. I could try to reproduce the issue again on a different VM, but I still wouldn't be able to collect logs. ** 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/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: Confirmed Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x0001efff] [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x0001efff] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009dfff] [0.00] node 0: [mem 0x0010-0xef
[Kernel-packages] [Bug 1573848] Re: KASLR should be enabled by default (x86)
** 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/1573848 Title: KASLR should be enabled by default (x86) Status in linux package in Ubuntu: Confirmed Bug description: Kernel Address Space Layout Randomization (KASLR) can make it harder to accomplish kernel security vulnerability exploits, especially during remote attacks or attacks from containers. On x86, KASLR has a run-time conflict with Hibernation, and currently the kernel selects Hibernation instead of KASLR unless the "kaslr" kernel command line option is given at boot time. Since the Unity desktop disabled access to Hibernation by default and cloud images don't use Hibernation, it would make sense to make KASLR enabled by default on Ubuntu. Those wishing to use Hibernation could just provide the "nokaslr" kernel command line option to flip the preference back. A patch to implement this already exists: https://lkml.org/lkml/2016/4/6/637 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573848] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1573848 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573848 Title: KASLR should be enabled by default (x86) Status in linux package in Ubuntu: Incomplete Bug description: Kernel Address Space Layout Randomization (KASLR) can make it harder to accomplish kernel security vulnerability exploits, especially during remote attacks or attacks from containers. On x86, KASLR has a run-time conflict with Hibernation, and currently the kernel selects Hibernation instead of KASLR unless the "kaslr" kernel command line option is given at boot time. Since the Unity desktop disabled access to Hibernation by default and cloud images don't use Hibernation, it would make sense to make KASLR enabled by default on Ubuntu. Those wishing to use Hibernation could just provide the "nokaslr" kernel command line option to flip the preference back. A patch to implement this already exists: https://lkml.org/lkml/2016/4/6/637 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568523] Re: CVE-2016-3672
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** 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/1568523 Title: CVE-2016-3672 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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-lts-wily source package in Trusty: New Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Sta
[Kernel-packages] [Bug 1566581] Re: CVE-2016-3689
** Changed in: linux-raspi2 (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/1566581 Title: CVE-2016-3689 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenial:
[Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported
** Description changed: - This card remains unsupported out-of-the-box by the ath10k_pci kernel - module. At this point, it looks like kvalo's ath10k-firmware repo just - needs to be pulled in. + The firmware for this card isn't included with Ubuntu. The firmware + provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when + used with this card. This included firmware is likely for the QCA6174 + instead of this card, the QCA6164. + + Yes, you read that right: the files for the QCA6164 need to be a folder + called QCA6174 in order for the card to work. Running "modprobe + ath10k_pci" shows that the ath10k_pci module looks for firmware in a + folder called QCA6174, but not in any folder called QCA6164. + + It seems that before this issue can be resolved, the ath10k_pci module + must be changed so that it recognizes firmware for both the QCA6164 and + QCA6174, in separate folders. --- HOW TO GET THIS CARD TO WORK: - As of February 26, 2016, this has become rather simple. + 1) Use a kernel that supports this card - According to the Linux Wireless wiki, support was added in kernel 4.2 - Your kernel is probably fine, but if it's older than 4.2, see + According to WikiDevi, support for this card was added in kernel 4.3. + If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip + to the next step. If you're running Ubuntu 15.10 or below, see https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a - newer one. + newer kernel. Alternatively, you can use backports. This is a lot more + work, but if you really need to keep using an older kernel for some + reason, there are some guides to installing backports in the comments + below. - 1) Get the latest firmware from https://github.com/kvalo/ath10k- - firmware/archive/master.zip + 2) Get rid of the firmware folder for this card that's included with + Ubuntu: - 2) Unzip this file, and copy the contents of ath10k-firmware-master to - /lib/firmware/ath10k. + sudo rm -r /lib/firmware/ath10k/QCA6174/ - 3) Rename two of the firmware files like so: - cd /lib/firmware/QCA6174/hw2.1 + 3) Download the latest firmware: + + wget https://github.com/kvalo/ath10k-firmware/archive/master.zip + + 4) Unzip the downloaded file. Inside the ath10k-firmware-master folder + is a folder named QCA6174. Copy the QCA6174 folder to + /lib/firmware/ath10k: + + unzip master.zip + sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/ + + 5) Rename two of the firmware files like so: + + cd /lib/firmware/ath10k/QCA6174/hw2.1/ sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin - cd /lib/firmware/QCA6174/hw3.0 + cd /lib/firmware/ath10k/QCA6174/hw3.0/ sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin - 4) Reboot your computer. Run "lshw -C network" to see if your card is - recognized. + 6) Reboot your computer. Run "lshw -C network" to see if your card is + recognized. You can delete the files you downloaded earlier: - If you created a "/lib/modprobe.d/ath10k.conf" file earlier to disable - otp, you can remove it. I did, and the card still works fine. + cd ~ + rm master.zip + rm -r ath10k-firmware-master/ - Last updated Match 26, 2016 + Verified to work on Ubuntu 16.04 LTS (with kernel 4.4.0-21-generic) + + Last updated April 22, 2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The firmware for this card isn't included with Ubuntu. The firmware provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when used with this card. This included firmware is likely for the QCA6174 instead of this card, the QCA6164. Yes, you read that right: the files for the QCA6164 need to be a folder called QCA6174 in order for the card to work. Running "modprobe ath10k_pci" shows that the ath10k_pci module looks for firmware in a folder called QCA6174, but not in any folder called QCA6164. It seems that before this issue can be resolved, the ath10k_pci module must be changed so that it recognizes firmware for both the QCA6164 and QCA6174, in separate folders. --- HOW TO GET THIS CARD TO WORK: 1) Use a kernel that supports this card According to WikiDevi, support for this card was added in kernel 4.3. If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip to the next step
[Kernel-packages] [Bug 1573848] [NEW] KASLR should be enabled by default (x86)
Public bug reported: Kernel Address Space Layout Randomization (KASLR) can make it harder to accomplish kernel security vulnerability exploits, especially during remote attacks or attacks from containers. On x86, KASLR has a run-time conflict with Hibernation, and currently the kernel selects Hibernation instead of KASLR unless the "kaslr" kernel command line option is given at boot time. Since the Unity desktop disabled access to Hibernation by default and cloud images don't use Hibernation, it would make sense to make KASLR enabled by default on Ubuntu. Those wishing to use Hibernation could just provide the "nokaslr" kernel command line option to flip the preference back. A patch to implement this already exists: https://lkml.org/lkml/2016/4/6/637 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1573848 Title: KASLR should be enabled by default (x86) Status in linux package in Ubuntu: New Bug description: Kernel Address Space Layout Randomization (KASLR) can make it harder to accomplish kernel security vulnerability exploits, especially during remote attacks or attacks from containers. On x86, KASLR has a run-time conflict with Hibernation, and currently the kernel selects Hibernation instead of KASLR unless the "kaslr" kernel command line option is given at boot time. Since the Unity desktop disabled access to Hibernation by default and cloud images don't use Hibernation, it would make sense to make KASLR enabled by default on Ubuntu. Those wishing to use Hibernation could just provide the "nokaslr" kernel command line option to flip the preference back. A patch to implement this already exists: https://lkml.org/lkml/2016/4/6/637 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** 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/1572666 Title: CVE-2016-3955 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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-lts-wily source package in Trusty: New Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Sta
[Kernel-packages] [Bug 1561388] Re: CVE-2016-3157
** Changed in: linux-raspi2 (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/1561388 Title: CVE-2016-3157 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1558847] Re: CVE-2016-3156
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-raspi2 (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/1558847 Title: CVE-2016-3156 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xe
[Kernel-packages] [Bug 1573833] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1573833 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: While installing Ubuntu Gnome 16.04 from scratch, so it didn't install, got this error and the installation was interrupted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 22:21:44 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1573833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551395] Re: CVE-2016-2782
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1551395 Title: CVE-2016-2782 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1556878] Re: CVE-2016-3137
** Changed in: linux-raspi2 (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/1556878 Title: CVE-2016-3137 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenial:
[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1554260 Title: CVE-2016-2847 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status
[Kernel-packages] [Bug 1556888] Re: CVE-2016-3140
** Changed in: linux-raspi2 (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/1556888 Title: CVE-2016-3140 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenial:
[Kernel-packages] [Bug 1556880] Re: CVE-2016-3138
** Changed in: linux-raspi2 (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/1556880 Title: CVE-2016-3138 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1556877] Re: CVE-2016-3136
** Changed in: linux-raspi2 (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/1556877 Title: CVE-2016-3136 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenial:
[Kernel-packages] [Bug 1573833] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
** Tags removed: need-duplicate-check -- 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/1573833 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: While installing Ubuntu Gnome 16.04 from scratch, so it didn't install, got this error and the installation was interrupted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 22:21:44 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1573833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549189] Re: CVE-2016-2546
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549189 Title: CVE-2016-2546 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1549190] Re: CVE-2016-2547
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549190 Title: CVE-2016-2547 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1549195] Re: CVE-2016-2548
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549195 Title: CVE-2016-2548 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1549182] Re: CVE-2016-2544
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549182 Title: CVE-2016-2544 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1549184] Re: CVE-2016-2545
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549184 Title: CVE-2016-2545 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1573833] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Public bug reported: While installing Ubuntu Gnome 16.04 from scratch, so it didn't install, got this error and the installation was interrupted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 22:21:44 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1573833 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: While installing Ubuntu Gnome 16.04 from scratch, so it didn't install, got this error and the installation was interrupted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 22:21:44 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1573833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
@Flames_in_paradise I do not have access to any optimus hardware to test. @Alberto, Thanks, gdm does not run as root anymore, X is for now launched as root via Xwrap for NVIDIA, but once the nvidia KMS drivers land even that should not be required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573702] Re: Ubuntu 16.04 freeze when HDMI cable plugged.
*** This bug is a duplicate of bug 1562076 *** https://bugs.launchpad.net/bugs/1562076 ** This bug has been marked a duplicate of bug 1562076 Ubuntu freezes a few seconds after plugin a screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573702 Title: Ubuntu 16.04 freeze when HDMI cable plugged. Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm suspect that this problem is similar to Bug #1562076 reported. lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.0 The Problem: When I plug a HDMI cable to use a second screen the Ubuntu freeze, halt and I need do a "hard power off". This problem occurs at any kernel of Ubuntu 16.04 that I tested. Now I use a 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18. The same hardware with Ubuntu 14 and kerne l3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC it's OK. If I could help us with any more information, please contact me. Thanks for help me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fpi2115 F pulseaudio /dev/snd/controlC0: fpi2115 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 13:26:33 2016 InstallationDate: Installed on 2016-02-12 (70 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5448 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=f7a65cdb-3d82-4056-ac2e-ed862cec2d7c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-08 (44 days ago) dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5448:pvrA06:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5448 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549181] Re: CVE-2016-2543
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1549181 Title: CVE-2016-2543 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-
[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185
** Changed in: linux-raspi2 (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/1561410 Title: CVE-2016-2185 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188
** Changed in: linux-raspi2 (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/1561414 Title: CVE-2016-2188 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1562076] Re: Ubuntu freezes a few seconds after plugin a screen
This problem IS specific to the new upgrade. I myself just upgraded from 14.04 LTS to 16.04 LTS. It worked fine prior to the upgrade. I'm using an ASUS X555UB Laptop. 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: Incomplete Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186
** Changed in: linux-raspi2 (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/1561411 Title: CVE-2016-2186 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567064] Re: tipc: missing linearization of sk_buff
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567064
Title:
tipc: missing linearization of sk_buff
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
The TIPC binding table sometimes fails to update correctly between
nodes because we don't linearize nonlinear buffers at two places where
it is needed in the code.
In the upstream kernel at kernel.org, the following commit was applied
on Nov 19th 2015:
commit c7cad0d6f70cd4ce8644ffe528a4df1cdc2e77f5 ("tipc: move
linearization of buffers to generic code") that fixes this issue.
This crucial fix made it into kernel 4.5, but unfortunately not into
4.4 that is used in Xenial, and makes TIPC in Xenial almost unusable
as it is now.
Now I am uncertain about how to proceed with this, since I am new with
dealing with the Ubuntu kernel.
- Do you apply such fixes from kernel.org if I post a new one to
kernel.org/stable? (The one referred to above won't apply cleanly to 4.4).
- Or should I issue a new one directly to Ubuntu's kernel team ?
- Or do you fix it yourself (it it pretty trivial and safe if you take a look
at the original commit I refer to) ?
BR
Jon Maloy
Ericsson Canada Inc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567064/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573817] Re: linux: 4.4.0-22.38 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-22.38 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-phase:Packaging + kernel-phase-changed:Friday, 22. April 2016 22:01 UTC ** Description changed: This bug is for tracking the 4.4.0-22.38 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Friday, 22. April 2016 22:01 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573817 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-22.38 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Friday, 22. April 2016 22:01 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1573817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1538429] Re: CVE-2016-2069
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1538429 Title: CVE-2016-2069 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New 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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Ne
[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184
** Changed in: linux-raspi2 (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/1561409 Title: CVE-2016-2184 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial 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-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in
[Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.
Is the patch working for anyone? If yes then please give me the instructions(or .deb file) . I tried the one suggested by Ralf but it dosent work somehow. output of ` uname -a ` ```$bash Linux sarthak-ThinkPad-E550 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1433906 Title: Acer, Inc ID 5986:055a is useless after 14.04.2 installed. Status in HWE Next: Won't Fix Status in linux-lts-utopic package in Ubuntu: Triaged Status in linux-lts-vivid package in Ubuntu: Triaged Status in linux-lts-wily package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Unknown Bug description: CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic) CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450 or E555. 2. Log in system and open a terminal. 3. $ gst-launch-0.10 v4l2src ! xvimagesink Expected result: Camara is activated Actual result: $ gst-launch-0.10 v4l2src ! xvimagesink Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 02:21:31 2015 InstallationDate: Installed on 2015-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561389] Re: CVE-2016-0821
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-raspi2 (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/1561389 Title: CVE-2016-0821 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: In
[Kernel-packages] [Bug 1573817] [NEW] linux: 4.4.0-22.38 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-22.38 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573817 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing
[Kernel-packages] [Bug 1567064] Re: tipc: missing linearization of sk_buff
I just submitted an SRU request for inclusion in Xenial. The bug status
will changed to "Fix Commited" when the fix lands in the -proposed
repository. It will then changed to "Fix Released" when it is in the
official kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567064
Title:
tipc: missing linearization of sk_buff
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The TIPC binding table sometimes fails to update correctly between
nodes because we don't linearize nonlinear buffers at two places where
it is needed in the code.
In the upstream kernel at kernel.org, the following commit was applied
on Nov 19th 2015:
commit c7cad0d6f70cd4ce8644ffe528a4df1cdc2e77f5 ("tipc: move
linearization of buffers to generic code") that fixes this issue.
This crucial fix made it into kernel 4.5, but unfortunately not into
4.4 that is used in Xenial, and makes TIPC in Xenial almost unusable
as it is now.
Now I am uncertain about how to proceed with this, since I am new with
dealing with the Ubuntu kernel.
- Do you apply such fixes from kernel.org if I post a new one to
kernel.org/stable? (The one referred to above won't apply cleanly to 4.4).
- Or should I issue a new one directly to Ubuntu's kernel team ?
- Or do you fix it yourself (it it pretty trivial and safe if you take a look
at the original commit I refer to) ?
BR
Jon Maloy
Ericsson Canada Inc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567064/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509355] Re: xorg crashes because of intel gpu driver
Just installed Kubuntu 16.04, fully updated as of 4/22/16 Noticed these two errors in KSystemLog: 4/22/16 12:08 PMjerry-Aspire-7739 kernel [13263.413901] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun 4/22/16 12:08 PMjerry-Aspire-7739 kernel [13263.415521] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun lspci jerry@jerry-Aspire-7739:~$ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) 03:00.0 Ethernet controller: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1) 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02) Partial lshw report: jerry@jerry-Aspire-7739:~$ lshw WARNING: you should run this program as super-user. jerry-aspire-7739 description: Computer width: 64 bits capabilities: vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 7654MiB *-cpu product: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 1333MHz capacity: 2399MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat cpufreq -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509355 Title: xorg crashes because of intel gpu driver Status in linux package in Ubuntu: Expired Bug description: Suddenly and without any warning the screen became blank and lightdm rebooted. I have found these interesting lines in dmesg: [14137.598202] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [14137.598222] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [14137.608538] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [14137.608552] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [14245.095875] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=601133 end=601134) [14697.328451] hrtimer: interrupt took 381228 ns [14744.724686] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=36973 end=36974) [17123.949459] usb 1-2: USB disconnect, device number 9 [17794.824728] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [17794.830525] [drm:intel_dp_complete_link_train [i915
[Kernel-packages] [Bug 1533044] Re: CVE-2016-0723
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1533044 Title: CVE-2016-0723 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source pack
[Kernel-packages] [Bug 1563916] Re: CVE-2016-0774
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1563916 Title: CVE-2016-0774 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial:
[Kernel-packages] [Bug 1545029] Re: CVE-2015-8812
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1545029 Title: CVE-2015-8812 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: New 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: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta
[Kernel-packages] [Bug 1573774] 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/1573774 Title: No screen after GRUB Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure, if this is the appropriate section for this bug report. I did an update (15.10 -> 16.04). After GRUB selects Ubuntu in standard configuration (Linux 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux), the screen turns immediately black and within seconds the screen signals "No cable attached". If I select the recovery mode in GRUB, the system boots fine in text- mode. From there I'm able to start X in 1280x1014 configuration (default: 1920x1080). I use the internal GPU of my Intel CPU with HDMI (no additional GPU available in my PC). CPUINFO: processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1467.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 2 apicid: 4 initial apicid: 4 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 1 initial apicid: 1 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 2 apicid: 5 initial apicid: 5 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_ts
[Kernel-packages] [Bug 1573774] Re: No screen after GRUB
Just for clarification: VGA-OUT works fine, it's an HDMI issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573774 Title: No screen after GRUB Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure, if this is the appropriate section for this bug report. I did an update (15.10 -> 16.04). After GRUB selects Ubuntu in standard configuration (Linux 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux), the screen turns immediately black and within seconds the screen signals "No cable attached". If I select the recovery mode in GRUB, the system boots fine in text- mode. From there I'm able to start X in 1280x1014 configuration (default: 1920x1080). I use the internal GPU of my Intel CPU with HDMI (no additional GPU available in my PC). CPUINFO: processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1467.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 2 apicid: 4 initial apicid: 4 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 1 initial apicid: 1 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs : bogomips : 5862.61 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family: 6 model : 37 model name: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping : 2 microcode : 0x9 cpu MHz : 1200.000 cache size: 4096 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 2 apicid: 5 initial apicid: 5 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monit
[Kernel-packages] [Bug 1533042] Re: CVE-2015-8767
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1533042 Title: CVE-2015-8767 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New 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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in
[Kernel-packages] [Bug 1573774] [NEW] No screen after GRUB
Public bug reported: I'm not sure, if this is the appropriate section for this bug report. I did an update (15.10 -> 16.04). After GRUB selects Ubuntu in standard configuration (Linux 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux), the screen turns immediately black and within seconds the screen signals "No cable attached". If I select the recovery mode in GRUB, the system boots fine in text- mode. From there I'm able to start X in 1280x1014 configuration (default: 1920x1080). I use the internal GPU of my Intel CPU with HDMI (no additional GPU available in my PC). CPUINFO: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping: 2 microcode : 0x9 cpu MHz : 1467.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs: bogomips: 5862.61 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping: 2 microcode : 0x9 cpu MHz : 1200.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 2 apicid : 4 initial apicid : 4 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs: bogomips: 5862.61 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping: 2 microcode : 0x9 cpu MHz : 1200.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs: bogomips: 5862.61 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz stepping: 2 microcode : 0x9 cpu MHz : 1200.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 2 apicid : 5 initial apicid : 5 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat bugs: bogomips: 5862.61 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0
[Kernel-packages] [Bug 1432869] Re: No wireless access for BCM 43162
Confirmed on Lenovo IdeaPad Yoga 500-15IBD 80N600EQCK. Ubuntu GNOME 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1432869 Title: No wireless access for BCM 43162 Status in linux package in Ubuntu: Expired Bug description: No connectivity on 14.04.2 for Lenovo Edge E555 using a BCM43162 wireless adapter. Here is what I got with lspci -nnk | grep -iA2 net Network Controller [0280]: Broadcom Corporation Device [14e4:43ae] (rev 02) Subsystem: Lenovo Device [17aa:0622] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534440] Re: CVE-2015-7566
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1534440 Title: CVE-2015-7566 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in
[Kernel-packages] [Bug 1508331] Re: CVE-2015-7833
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1508331 Title: CVE-2015-7833 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial 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-raspi2 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source packag
[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised
installed kubuntu 16.04 yesterday on my selfbuild-pc with gigabyte ga970a-ds3p and amd fx8350. same problem here. my external hdd seems to have power, its rotating and blinking, but its only recogniced on usb 2 port. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1242321 Title: USB 3.0 Harddrive not recognised Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu is not recognising any device plugged into any USB 3.0 ports. Sometimes Ubuntu will freeze for a few seconds when you plug something into a USB 3.0 port; when Ubuntu comes out of the freeze, the device is still NOT recognised. No problems with USB 2.0 ports and devices. The USB 3.0 on this computer only works in Windows 7 (I'm dual booting Ubuntu 13.10 and Windows 7, both are 64-bit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
We have tested the kernel and it looks good, this is okay to go forward. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460768] Re: Unable to build kernel 3.19.0-18
Still happens in 4.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460768 Title: Unable to build kernel 3.19.0-18 Status in One Hundred Papercuts: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: There is a bug during compiling kernel version 3.19.0-18. First I executed patch file from archive linux_3.19.0-18.18.diff.gz and source https://launchpad.net/ubuntu/+source/linux/3.19.0-18.18 Then I executed make-kpkg --initrd buildpackage with attached config file. But I got a compiling error: CC [M] ubuntu/vbox/vboxguest/VBoxGuest-linux.o In file included from :0:0: ././include/linux/kconfig.h:46:1: fatal error: ./ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory #endif /* __LINUX_KCONFIG_H */ ^ compilation terminated. make[6]: *** [ubuntu/vbox/vboxguest/VBoxGuest-linux.o] Error 1 make[5]: *** [ubuntu/vbox/vboxguest] Error 2 make[4]: *** [ubuntu/vbox] Error 2 make[3]: *** [ubuntu] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1460768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555865] Re: CVE-2015-7515
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-raspi2 (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/1555865 Title: CVE-2015-7515 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 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-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-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 Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 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: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Committed Status in linux-ti-omap4 source package in Wily: In
[Kernel-packages] [Bug 1572723] Re: Dell XPS 9350 Reboots upon resume with the latest 4.4.0-21 kernel update
I just booted windows and re-applied the new BIOS (1.3.3) and the new Thunderbolt Firmware so I am all caught up on the BIOS and firmware settings on the board. I also nuked all the HD and re-installed Ubuntu from scratch. I just retested it and the crash still happens when you close the lid or issue a suspend commend using the UI. This is a critical regression that should be addressed and soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572723 Title: Dell XPS 9350 Reboots upon resume with the latest 4.4.0-21 kernel update Status in linux package in Ubuntu: Confirmed Bug description: Make sure your machine is up to date (has the 4.4.0-21) kernel and close the lid on the laptop. When you open the lid, the machine reboots. This didn't happen with the 4.4.0-18 kernel) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anmar 1473 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 20 16:44:56 2016 HibernationDevice: RESUME=UUID=5dccb0a4-b2c7-4b32-bff8-bd0657b5158b InstallationDate: Installed on 2016-03-29 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=18eebbfe-ef00-4ba8-afd6-172ae82427c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571156] Re: vbox: resync with 5.0.18-dfsg-2build1
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571156 Title: vbox: resync with 5.0.18-dfsg-2build1 Status in linux package in Ubuntu: Fix Committed Bug description: We are behind main vbox packages: virtualbox (5.0.16-dfsg-3) experimental; urgency=low * Build without xorg legacy with the backport of 5.0.17 code (revision 106564) * Bump std-version to 3.9.8, no changes required. * Add vbox-img (LP: #1558521). - thanks sworddragon for the bug report! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
the log in comment #10 looks good to me. @Tim: yes, it could be a problem with permissions. I don't use Gnome, so I didn't notice. I can certainly have a look at GDM. @virgosun: that sounds like a different problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565601] Re: Kubuntu 16.04 does not auto logon
As reported elsewhere, using system settings to disable auto login and the re-enable it fixed the problem on Kubuntu. -- 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/1565601 Title: Kubuntu 16.04 does not auto logon Status in linux-armadaxp package in Ubuntu: Confirmed Bug description: I installed the beta and asked for auto logon, however on restart I get the login screen instead. It did work however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-armadaxp/+bug/1565601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554077] Re: brcmf_add_if: ERROR: netdev:wlp2s0 already exists
I'm experiencing this bug too. In my case, WiFi works in 50% of cases. Sometimes I'm booting up and it works, sometimes It is shown as wired o_O connection instead of WiFi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554077 Title: brcmf_add_if: ERROR: netdev:wlp2s0 already exists Status in linux package in Ubuntu: Incomplete Bug description: At boot time, on Wifi interface set up, at boot time, an error is raised. The graphical boot switches to textual boot to display this error. Despite this error the Wifi connection mostly works. [ 47.250309] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 47.289947] brcmf_add_if: ERROR: netdev:wlp2s0 already exists [ 47.289950] brcmf_add_if: ignore IF event [ 48.485330] brcmf_add_if: ERROR: netdev:wlp2s0 already exists [ 48.485333] brcmf_add_if: ignore IF event Ubuntu Wily 15.10, Kernel 4.2.0-30-generic, Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gquintana 1413 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=2e069a2b-037f-4058-89b1-6e221da4046d InstallationDate: Installed on 2016-01-31 (35 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=3ecb2c05-ad6c-4d9d-9356-48c6991f0226 ro quiet splash nouveau.modeset=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0X2P13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565601] Re: Kubuntu 16.04 does not auto logon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-armadaxp (Ubuntu) Status: New => Confirmed -- 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/1565601 Title: Kubuntu 16.04 does not auto logon Status in linux-armadaxp package in Ubuntu: Confirmed Bug description: I installed the beta and asked for auto logon, however on restart I get the login screen instead. It did work however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-armadaxp/+bug/1565601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565601] Re: Kubuntu 16.04 does not auto logon
I upgraded to 16.04 from 15.10 today and requested auto login, but it always requests password. I also used the system settings to set auto login, but it still requests password. -- 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/1565601 Title: Kubuntu 16.04 does not auto logon Status in linux-armadaxp package in Ubuntu: Confirmed Bug description: I installed the beta and asked for auto logon, however on restart I get the login screen instead. It did work however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-armadaxp/+bug/1565601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1537886] Re: CVE-2013-4312
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1537886 Title: CVE-2013-4312 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed 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: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 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: New 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-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source pack
[Kernel-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "hcidump of a pairing attempt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4643207/+files/hcidump-hr.log -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573271] Re: linux-ti-omap4: 3.2.0-1480.106 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1573271 Title: linux-ti-omap4: 3.2.0-1480.106 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1480.106 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-phase:Uploaded kernel-stable-phase-changed:Thursday, 21. April 2016 23:01 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1573271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573702] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573702 Title: Ubuntu 16.04 freeze when HDMI cable plugged. Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm suspect that this problem is similar to Bug #1562076 reported. lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.0 The Problem: When I plug a HDMI cable to use a second screen the Ubuntu freeze, halt and I need do a "hard power off". This problem occurs at any kernel of Ubuntu 16.04 that I tested. Now I use a 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18. The same hardware with Ubuntu 14 and kerne l3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC it's OK. If I could help us with any more information, please contact me. Thanks for help me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fpi2115 F pulseaudio /dev/snd/controlC0: fpi2115 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 13:26:33 2016 InstallationDate: Installed on 2016-02-12 (70 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5448 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=f7a65cdb-3d82-4056-ac2e-ed862cec2d7c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-08 (44 days ago) dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5448:pvrA06:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5448 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573700] 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/1573700 Title: Kernel instability Status in linux package in Ubuntu: Confirmed Bug description: Bad power management in kernel 4.4 results in overheating and memory corruption. Possibly reported here: http://mjg59.dreamwidth.org/41713.html Apr 22 14:10:30 oryx kernel: [ 6901.023405] [ cut here ] Apr 22 14:10:30 oryx kernel: [ 6901.023413] WARNING: CPU: 5 PID: 5658 at /build/linux-Ay7j_C/linux-4.4.0/arch/x86/kernel/check.c:141 check_for_bios_corruption.part.1+0xaf/0x100() Apr 22 14:10:30 oryx kernel: [ 6901.023415] Memory corruption detected in low memory Apr 22 14:10:30 oryx kernel: [ 6901.023416] Modules linked in: msr rfcomm vmw_vsock_vmci_transport vsock vmw_vmci drbg ansi_cprng ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netf ilter bridge stp llc overlay ec_sys bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi arc4 nvidia_uvm(POE) nvidia_modeset(POE) snd_hda_codec_realtek mxm_wmi snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp i915_bpo coretemp intel_ips kvm_intel drm_kms_helper kvm i2c_algo_bit fb_sys_fops syscopyar ea sysfillrect sysimgblt irqbypass snd_hda_intel crct10dif_pclmul crc32_pclmul iwlmvm snd_hda_codec snd_hda_core aesni_intel snd_hwdep mac80211 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_pcm iwlwifi input_leds serio_raw joydev snd_seq_midi snd_seq_midi_event cfg80211 uvcvideo snd_rawmidi nvidia(POE) vi deobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_core v4l2_common rtsx_pci_ms snd_seq_device videodev memstick snd_timer btusb media btrtl hci_uart snd drm btbcm btqca soundcore btintel mei_me bluetooth mei shpchp intel_lpss_acpi intel_lpss wmi acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrf s xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid rtsx_pci_sdmmc psmouse ahci r8169 nvme rtsx_pci libahci mii i2c_hid pinctrl_sunrisepoint video hid pinctrl_intel fjes Apr 22 14:10:30 oryx kernel: [ 6901.023506] CPU: 5 PID: 5658 Comm: kworker/5:0 Tainted: P OE 4.4.0-21-generic #37-Ubuntu Apr 22 14:10:30 oryx kernel: [ 6901.023508] Hardware name: System76, Inc. Oryx Pro/Oryx Pro, BIOS 1.05.09RSA1 11/16/2015 Apr 22 14:10:30 oryx kernel: [ 6901.023512] Workqueue: events check_corruption Apr 22 14:10:30 oryx kernel: [ 6901.023514] 0286 e16be0ec 8807c02bfd20 813e93c3 Apr 22 14:10:30 oryx kernel: [ 6901.023517] 8807c02bfd68 81ca6cc0 8807c02bfd58 81080f62 Apr 22 14:10:30 oryx kernel: [ 6901.023520] 8801 820fa730 0001 Apr 22 14:10:30 oryx kernel: [ 6901.023523] Call Trace: Apr 22 14:10:30 oryx kernel: [ 6901.023529] [] dump_stack+0x63/0x90 Apr 22 14:10:30 oryx kernel: [ 6901.023533] [] warn_slowpath_common+0x82/0xc0 Apr 22 14:10:30 oryx kernel: [ 6901.023536] [] warn_slowpath_fmt+0x5c/0x80 Apr 22 14:10:30 oryx kernel: [ 6901.023540] [] check_for_bios_corruption.part.1+0xaf/0x100 Apr 22 14:10:30 oryx kernel: [ 6901.023543] [] check_corruption+0x18/0x50 Apr 22 14:10:30 oryx kernel: [ 6901.023547] [] process_one_work+0x162/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023550] [] worker_thread+0x4b/0x4c0 Apr 22 14:10:30 oryx kernel: [ 6901.023553] [] ? process_one_work+0x480/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023556] [] ? process_one_work+0x480/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023559] [] kthread+0xd8/0xf0 Apr 22 14:10:30 oryx kernel: [ 6901.023562] [] ? kthread_create_on_node+0x1e0/0x1e0 Apr 22 14:10:30 oryx kernel: [ 6901.023566] [] ret_from_fork+0x3f/0x70 Apr 22 14:10:30 oryx kernel: [ 6901.023569] [] ? kthread_create_on_node+0x1e0/0x1e0 Apr 22 14:10:30 oryx kernel: [ 6901.023571] ---[ end trace bd39c0464c4ce14b ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: katox 2267 F pulseaudio /dev/snd/controlC0: katox 2267 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 22 18:34:21 2016 HibernationDevice: RESUME=UUID=318a1a5e-a37d-4d2a-be53-d08e720e5359 MachineType: System76, Inc. Oryx Pro ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=dff50ce8-af6c-4fbb-951f-27
[Kernel-packages] [Bug 1573702] [NEW] Ubuntu 16.04 freeze when HDMI cable plugged.
Public bug reported: Hello, I'm suspect that this problem is similar to Bug #1562076 reported. lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.0 The Problem: When I plug a HDMI cable to use a second screen the Ubuntu freeze, halt and I need do a "hard power off". This problem occurs at any kernel of Ubuntu 16.04 that I tested. Now I use a 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18. The same hardware with Ubuntu 14 and kerne l3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC it's OK. If I could help us with any more information, please contact me. Thanks for help me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fpi2115 F pulseaudio /dev/snd/controlC0: fpi2115 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 13:26:33 2016 InstallationDate: Installed on 2016-02-12 (70 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5448 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=f7a65cdb-3d82-4056-ac2e-ed862cec2d7c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-08 (44 days ago) dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5448:pvrA06:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5448 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze-hdmi hdmi third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573702 Title: Ubuntu 16.04 freeze when HDMI cable plugged. Status in linux package in Ubuntu: New Bug description: Hello, I'm suspect that this problem is similar to Bug #1562076 reported. lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.0 The Problem: When I plug a HDMI cable to use a second screen the Ubuntu freeze, halt and I need do a "hard power off". This problem occurs at any kernel of Ubuntu 16.04 that I tested. Now I use a 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18. The same hardware with Ubuntu 14 and kerne l3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC it's OK. If I could help us with any more information, please contact me. Thanks for help me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fpi2115 F pulseaudio /dev/snd/controlC0: fpi2115 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 13:26:33 2016 InstallationDate: Installed on 2016-02-12 (70 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5448 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=f7a65cdb-3d82-4056-ac2e-ed862cec2d7c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-08 (44 days ago) dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5448:pvrA06:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5448 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListH
[Kernel-packages] [Bug 1573700] [NEW] Kernel instability
Public bug reported: Bad power management in kernel 4.4 results in overheating and memory corruption. Possibly reported here: http://mjg59.dreamwidth.org/41713.html Apr 22 14:10:30 oryx kernel: [ 6901.023405] [ cut here ] Apr 22 14:10:30 oryx kernel: [ 6901.023413] WARNING: CPU: 5 PID: 5658 at /build/linux-Ay7j_C/linux-4.4.0/arch/x86/kernel/check.c:141 check_for_bios_corruption.part.1+0xaf/0x100() Apr 22 14:10:30 oryx kernel: [ 6901.023415] Memory corruption detected in low memory Apr 22 14:10:30 oryx kernel: [ 6901.023416] Modules linked in: msr rfcomm vmw_vsock_vmci_transport vsock vmw_vmci drbg ansi_cprng ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netf ilter bridge stp llc overlay ec_sys bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi arc4 nvidia_uvm(POE) nvidia_modeset(POE) snd_hda_codec_realtek mxm_wmi snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp i915_bpo coretemp intel_ips kvm_intel drm_kms_helper kvm i2c_algo_bit fb_sys_fops syscopyar ea sysfillrect sysimgblt irqbypass snd_hda_intel crct10dif_pclmul crc32_pclmul iwlmvm snd_hda_codec snd_hda_core aesni_intel snd_hwdep mac80211 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_pcm iwlwifi input_leds serio_raw joydev snd_seq_midi snd_seq_midi_event cfg80211 uvcvideo snd_rawmidi nvidia(POE) vi deobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_core v4l2_common rtsx_pci_ms snd_seq_device videodev memstick snd_timer btusb media btrtl hci_uart snd drm btbcm btqca soundcore btintel mei_me bluetooth mei shpchp intel_lpss_acpi intel_lpss wmi acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrf s xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid rtsx_pci_sdmmc psmouse ahci r8169 nvme rtsx_pci libahci mii i2c_hid pinctrl_sunrisepoint video hid pinctrl_intel fjes Apr 22 14:10:30 oryx kernel: [ 6901.023506] CPU: 5 PID: 5658 Comm: kworker/5:0 Tainted: P OE 4.4.0-21-generic #37-Ubuntu Apr 22 14:10:30 oryx kernel: [ 6901.023508] Hardware name: System76, Inc. Oryx Pro/Oryx Pro, BIOS 1.05.09RSA1 11/16/2015 Apr 22 14:10:30 oryx kernel: [ 6901.023512] Workqueue: events check_corruption Apr 22 14:10:30 oryx kernel: [ 6901.023514] 0286 e16be0ec 8807c02bfd20 813e93c3 Apr 22 14:10:30 oryx kernel: [ 6901.023517] 8807c02bfd68 81ca6cc0 8807c02bfd58 81080f62 Apr 22 14:10:30 oryx kernel: [ 6901.023520] 8801 820fa730 0001 Apr 22 14:10:30 oryx kernel: [ 6901.023523] Call Trace: Apr 22 14:10:30 oryx kernel: [ 6901.023529] [] dump_stack+0x63/0x90 Apr 22 14:10:30 oryx kernel: [ 6901.023533] [] warn_slowpath_common+0x82/0xc0 Apr 22 14:10:30 oryx kernel: [ 6901.023536] [] warn_slowpath_fmt+0x5c/0x80 Apr 22 14:10:30 oryx kernel: [ 6901.023540] [] check_for_bios_corruption.part.1+0xaf/0x100 Apr 22 14:10:30 oryx kernel: [ 6901.023543] [] check_corruption+0x18/0x50 Apr 22 14:10:30 oryx kernel: [ 6901.023547] [] process_one_work+0x162/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023550] [] worker_thread+0x4b/0x4c0 Apr 22 14:10:30 oryx kernel: [ 6901.023553] [] ? process_one_work+0x480/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023556] [] ? process_one_work+0x480/0x480 Apr 22 14:10:30 oryx kernel: [ 6901.023559] [] kthread+0xd8/0xf0 Apr 22 14:10:30 oryx kernel: [ 6901.023562] [] ? kthread_create_on_node+0x1e0/0x1e0 Apr 22 14:10:30 oryx kernel: [ 6901.023566] [] ret_from_fork+0x3f/0x70 Apr 22 14:10:30 oryx kernel: [ 6901.023569] [] ? kthread_create_on_node+0x1e0/0x1e0 Apr 22 14:10:30 oryx kernel: [ 6901.023571] ---[ end trace bd39c0464c4ce14b ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: katox 2267 F pulseaudio /dev/snd/controlC0: katox 2267 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 22 18:34:21 2016 HibernationDevice: RESUME=UUID=318a1a5e-a37d-4d2a-be53-d08e720e5359 MachineType: System76, Inc. Oryx Pro ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=dff50ce8-af6c-4fbb-951f-275913943881 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.bo
[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown
I can also confirm this problem. The system is starting when i use the 4.4.0-21-generic (recovery mode) It doesnt start when i choose 4.4.0-21-generic I only see a blue screen when i would start with 4.4.0-21-generic 4.2.0-34-generic is working fine -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359689 Title: cryptsetup password prompt not shown Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Triaged Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573271] Re: linux-ti-omap4: 3.2.0-1480.106 -proposed tracker
linux-ti-omap4 | 3.2.0-1480.106 | precise-proposed | source linux-meta-ti-omap4 | 3.2.0.1480.75 | precise-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1573271 Title: linux-ti-omap4: 3.2.0-1480.106 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1480.106 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-phase:Uploaded kernel-stable-phase-changed:Thursday, 21. April 2016 23:01 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1573271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Same to me. I have to rollback to Ubuntu Gnome 15.10. Please fix 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571156] Re: vbox: resync with 5.0.18-dfsg-2build1
We need to re-re-re-do this to get the latest: 5.0.18-dfsg-2build1 ** Summary changed: - vbox: resync with 5.0.16-dfsg-3 + vbox: resync with 5.0.18-dfsg-2build1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571156 Title: vbox: resync with 5.0.18-dfsg-2build1 Status in linux package in Ubuntu: In Progress Bug description: We are behind main vbox packages: virtualbox (5.0.16-dfsg-3) experimental; urgency=low * Build without xorg legacy with the backport of 5.0.17 code (revision 106564) * Bump std-version to 3.9.8, no changes required. * Add vbox-img (LP: #1558521). - thanks sworddragon for the bug report! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
** Changed in: canonical-devices-system-image Assignee: Bill Filler (bfiller) => John McAleely (john.mcaleely) -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
confirm same. reproducible on hardware Lenovo Yoga 500-15IBD Primus HD 5500/ Nvidia Geforce GT940M. Before 16.04, run fine on base system 15.10 Nvidia proprietary 351 After $sudo do-release-upgrade Lighntdm ---> login loop dpkg-reconfigure Gdm ---> blank screen Nvidia proprietary 362 Bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573648] 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/1573648 Title: 16.04 -> AMD APU via VGA gives blank screen Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 16.04, the system will only show a blank screen when a monitor is connected to the VGA output. The system itself is able to completely start-up (checked via a ssh login). Starting up using an older kernel (in this case 4.2.0) gives a functional graphical system. Possibly related dmesg lines (when booting 4.4.0): kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed It might be related to the following kernel post (but i am not entirely sure): https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 2014 F pulseaudio /dev/snd/controlC0: rene 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 16:29:44 2016 HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e InstallationDate: Installed on 2015-12-29 (114 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: FM2A68M-HD+ 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.90:bd12/04/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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/1573648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573231] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1573231 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: Incomplete Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x0001efff] [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
Might be a better idea, to use an old kernel instead of blacklisting. At least for me, blacklisting the radeon driver leads to high temperatures and battery drain, beause the ATI card runs in high performance mode. I'm currently doing a bisect to nail down the commit which introduced this bug - this will take pretty long however. 4.2. works perfectly fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersi
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
... continuing my post: blacklisting the Radeon made no difference -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
Exact issue on my laptop too (Lenovo Y40-80). Updated from 14.04 to 16.04 yesterday, and when I used to close the lid before, the laptop used to go to suspend mode, and wake up whenever I opened the lid again. However, after upgrading to 16.04, if I close the lid, the screen just turns back (while the system is still running), and when I open the lid again, the screen remains black, and I need to hard reset (long pressing the power button). Even on selecting "Suspend" from top right corner of the menu, it shows the same behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd
[Kernel-packages] [Bug 1573648] [NEW] 16.04 -> AMD APU via VGA gives blank screen
Public bug reported: After upgrade to 16.04, the system will only show a blank screen when a monitor is connected to the VGA output. The system itself is able to completely start-up (checked via a ssh login). Starting up using an older kernel (in this case 4.2.0) gives a functional graphical system. Possibly related dmesg lines (when booting 4.4.0): kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed It might be related to the following kernel post (but i am not entirely sure): https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 2014 F pulseaudio /dev/snd/controlC0: rene 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 16:29:44 2016 HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e InstallationDate: Installed on 2015-12-29 (114 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: FM2A68M-HD+ 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.90:bd12/04/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573648 Title: 16.04 -> AMD APU via VGA gives blank screen Status in linux package in Ubuntu: New Bug description: After upgrade to 16.04, the system will only show a blank screen when a monitor is connected to the VGA output. The system itself is able to completely start-up (checked via a ssh login). Starting up using an older kernel (in this case 4.2.0) gives a functional graphical system. Possibly related dmesg lines (when booting 4.4.0): kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed It might be related to the following kernel post (but i am not entirely sure): https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 2014 F pulseaudio /dev/snd/controlC0: rene 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 16:29:44 2016 HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e InstallationDate: Installed on 2015-12-29 (114 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.
[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: New Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x0001efff] [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x0001efff] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009dfff] [0.00] node 0: [mem 0x0010-0xefff] [0.00] node 0: [mem 0x0001-0x0001efff] [0.00] Initmem setup node 0 [mem 0x1000-0x0001efff] [0.00] ACPI: PM-Timer IO Port: 0xb008 [
