[Kernel-packages] [Bug 613022] Re: ssh daemon hangs after publickey packet sent
Closing this out as crufty. If this is seen again, please reopen. ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/613022 Title: ssh daemon hangs after publickey packet sent Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: A launched ec2 instance in ap-southeast-1 region is unreachable via ssh. $ ssh -vvv ec2-175-41-171-225.ap-southeast-1.compute.amazonaws.com shows progress up to : debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: smoser@brickies debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply Then nothing for minutes before session is killed (manually). In a 'good' connection, the following would be next: debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey I'll attach full 'ssh -vvv' logs good and bad connection. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssh-server 1:5.5p1-4ubuntu3 ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35 Uname: Linux 2.6.35-14-virtual x86_64 Architecture: amd64 Date: Tue Aug 3 14:45:25 2010 Ec2AMI: ami-9fc4bbcd Ec2AMIManifest: ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.1.manifest.xml Ec2AvailabilityZone: ap-southeast-1a Ec2InstanceType: m1.large Ec2Kernel: aki-11d5aa43 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/613022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495983] [NEW] [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32
You have been subscribed to a public bug: Attempting to install the latest build of Ubuntu Server 15.10 (Wily Werewolf) x32 on Hyper-V, after beginning installation a kernel panic occurs. The console log from the serial output is attached. http://cdimage.ubuntu.com/ubuntu-server/daily/current/ I tried with the builds from 14th and 15th of September with the same result. This bug does not affect x64 builds. Tried to start the installation with different resources with no effect, kernel panic always occurs no matter the VM settings. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment build daily hyper-v install kernel panic werewolf wily -- [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32 https://bugs.launchpad.net/bugs/1495983 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 1494006] Re: linux-ti-omap4: 3.2.0-1471.92 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1494006 Title: linux-ti-omap4: 3.2.0-1471.92 -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: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 09. September 2015 21:13 UTC kernel-stable-master-bug:1493780 kernel-stable-Certification-testing-end:Monday, 14. September 2015 13:00 UTC kernel-stable-Prepare-package-end:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-start:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:23 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 15. September 2015 22:01 UTC kernel-stable-Security-signoff-start:Tuesday, 15. September 2015 22:01 UTC kernel-stable-Regression-testing-start:Tuesday, 15. September 2015 22:01 UTC proposed-announcement-sent:True kernel-stable-Verification-testing-start:Tuesday, 15. September 2015 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1494006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495983] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1495983 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/1495983 Title: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32 Status in linux package in Ubuntu: Incomplete Bug description: Attempting to install the latest build of Ubuntu Server 15.10 (Wily Werewolf) x32 on Hyper-V, after beginning installation a kernel panic occurs. The console log from the serial output is attached. http://cdimage.ubuntu.com/ubuntu-server/daily/current/ I tried with the builds from 14th and 15th of September with the same result. This bug does not affect x64 builds. Tried to start the installation with different resources with no effect, kernel panic always occurs no matter the VM settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491761] Re: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04
filip, as per http://support.hp.com/us-en/drivers/selfservice/Compaq- Presario-CQ71-Notebook-PC-series/4004498/model/4039991 an update to your computer's buggy and outdated BIOS is available (F.23). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491761 Title: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04 Status in linux package in Ubuntu: Incomplete Bug description: (eth0): carrier is OFF Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 2 20:00:32 cq71 NetworkManager[579]: [1441216832.927980] [platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 2: mtu 0 (1) driver 'r8169' udi '/sys/devices/pci:00/:00:1c.1/:03:00.0/net/eth0': Invalid address for specified address family Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): preparing device r8169 :03:00.0 eth0: RTL8102e at 0xc90004778000, 00:00:00:00:00:00, XID 04c0 IRQ 27 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Subsystem: Hewlett-Packard Company Device 306c Kernel driver in use: r8169 *-network DISABLED description: Ethernet interface product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 02 size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full latency=0 link=no multicast=yes port=MII speed=100Mbit/s resources: irq:27 ioport:2000(size=256) memory:d401-d4010fff memory:d400-d400 memory:d500-d500 i compiled the r8101 module from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false after i put in a "cloned mac adress" the card is functional. there is also an old bug report of this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256331 --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 1084 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6f27858b-0ba5-46f9-b656-36f652d32cb0 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=c8c26d44-1f21-4878-8430-8e0fe79ffcc4 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev' Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 306C dmi.board.vendor: Quanta dmi.board.version: 21.12 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1494903] Re: Kernel 4.2 drm/i915 erractic error
** Tags added: latest-bios-a05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1494903 Title: Kernel 4.2 drm/i915 erractic error Status in linux package in Ubuntu: Incomplete Status in linux source package in Wily: Incomplete Bug description: I am encountering this following erratic error with Wily kernel 4.2. With Kernel, 4.1 I did not encounter such issues with drm i915. [ 5437.034758] [ cut here ] [ 5437.034784] WARNING: CPU: 2 PID: 0 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11098 intel_check_page_flip+0xfc/0x110 [i915]() [ 5437.034785] Kicking stuck page flip: queued at 322707, now 322711 [ 5437.034786] Modules linked in: hid_generic snd_usb_audio usbhid snd_usbmidi_lib drbg ansi_cprng ctr ccm rfcomm binfmt_misc bnep nls_iso8859_1 joydev dcdbas dell_wmi arc4 hid_multitouch sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_rt286 snd_soc_rl6347a iwlmvm snd_soc_core crct10dif_pclmul mac80211 snd_compress ac97_bus crc32_pclmul snd_pcm_dmaengine snd_seq_midi ghash_clmulni_intel uvcvideo snd_seq_midi_event aesni_intel snd_rawmidi videobuf2_vmalloc aes_x86_64 videobuf2_memops lrw gf128mul glue_helper btusb iwlwifi ablk_helper cryptd input_leds videobuf2_core serio_raw v4l2_common dell_led btrtl videodev snd_seq snd_hda_codec_hdmi btbcm btintel snd_hda_codec_realtek media bluetooth snd_hda_codec_generic cfg80211 rtsx_pci_ms snd_hda_intel memstick snd_hda_codec [ 5437.034821] snd_hda_core snd_hwdep snd_pcm lpc_ich snd_seq_device shpchp snd_timer snd soundcore soc_button_array int3403_thermal acpi_als kfifo_buf industrialio dw_dmac int3400_thermal spi_pxa2xx_platform processor_thermal_device dw_dmac_core acpi_thermal_rel snd_soc_sst_acpi intel_soc_dts_iosf 8250_dw i2c_designware_platform int3402_thermal tpm_crb iosf_mbi i2c_designware_core int340x_thermal_zone mac_hid acpi_pad parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc i915 i2c_algo_bit ahci drm_kms_helper libahci rtsx_pci drm wmi sdhci_acpi video sdhci i2c_hid hid [ 5437.034846] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.2.0-7-generic #7-Ubuntu [ 5437.034847] Hardware name: Dell Inc. XPS 13 9343/0TM99H, BIOS A05 07/14/2015 [ 5437.034849] c02101e8 88021f503d68 817b0465 [ 5437.034851] 88021f503db8 88021f503da8 81076536 88021f503db8 [ 5437.034853] 880211a46800 880211be3000 880211a469a8 [ 5437.034855] Call Trace: [ 5437.034857][] dump_stack+0x45/0x57 [ 5437.034864] [] warn_slowpath_common+0x86/0xc0 [ 5437.034866] [] warn_slowpath_fmt+0x46/0x50 [ 5437.034882] [] intel_check_page_flip+0xfc/0x110 [i915] [ 5437.034894] [] gen8_irq_handler+0x369/0x560 [i915] [ 5437.034897] [] handle_irq_event_percpu+0x74/0x180 [ 5437.034899] [] handle_irq_event+0x49/0x70 [ 5437.034902] [] handle_edge_irq+0x81/0x150 [ 5437.034904] [] handle_irq+0x25/0x40 [ 5437.034906] [] do_IRQ+0x4f/0xe0 [ 5437.034909] [] common_interrupt+0x6b/0x6b [ 5437.034910][] ? enqueue_hrtimer+0x44/0x80 [ 5437.034915] [] ? cpuidle_enter_state+0x130/0x270 [ 5437.034917] [] ? cpuidle_enter_state+0x10b/0x270 [ 5437.034919] [] cpuidle_enter+0x17/0x20 [ 5437.034920] [] call_cpuidle+0x32/0x60 [ 5437.034922] [] ? cpuidle_select+0x13/0x20 [ 5437.034923] [] cpu_startup_entry+0x259/0x320 [ 5437.034927] [] start_secondary+0x174/0x1a0 [ 5437.034928] ---[ end trace 3d8fa70b3cf1a1ff ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: loic 1504 F pulseaudio /dev/snd/controlC1: loic 1504 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 11 21:10:42 2015 HibernationDevice: RESUME=UUID=8c8fb0c1-2656-491a-9e7c-df539df7f606 InstallationDate: Installed on 2015-08-08 (34 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150808) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic.efi.signed root=/dev/mapper/vgroot-lvroot ro priority=low i915.enable_ips=0 pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 ipv6.disable=1 cgroup_disable=memory nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Kernel-packages] [Bug 1496109] phact (amd64) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-10.11/phact__4.2.0-10.11__2015-09-15_23-43-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463445] Re: CVE-2015-4003
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463445 Title: CVE-2015-4003 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51
[Kernel-packages] [Bug 1496163] 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/1496163 Title: Wily: firmware load for i915/skl_dmc_ver1.bin failed with error -2 Status in linux package in Ubuntu: Confirmed Bug description: On Skylake, the skl_dmc firmware is failing to load. From dmesg: [0.728803] i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) This means the GPU can't enter its lowest available power states, plus many display hotplugging scenarios (that only the skl_dmc firmware can handle) are broken. On a whim I tried some other firmware versions: 1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin (instead of skl_dmc_ver1_19.bin) 2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the skl_dmc_ver1.bin symlink to it But neither corrected the situation. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1251 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 15 16:21:24 2015 HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f IwConfig: enp4s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 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: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: Default string dmi.board.name: Z170-P D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481129] Re: System freeze when using Libre Office
Witold Szczeponik, I've already advised in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481129/comments/10 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481129 Title: System freeze when using Libre Office Status in linux package in Ubuntu: Incomplete Bug description: When using Libre office Draw, the system entirely froze. I was just able to move the mouse, not even able to do a tty session. I am using Nouveau Driver, with a kernel 3.19.0-25-generic. I'm quite new reporting bugs, so please let me know if you need any additional information, I'll add them =) Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 3 22:21:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7220] InstallationDate: Installed on 2015-07-18 (16 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: Micro-Star International GX627 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=9e366518-5490-46f2-a96a-b0a230e475dd ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1651IMS.10P dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-1651 dmi.board.vendor: MSI dmi.board.version: Ver 1.000 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.:bvrA1651IMS.10P:bd12/26/2008:svnMicro-StarInternational:pnGX627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GX627 dmi.product.version: Ver 1.000 dmi.sys.vendor: Micro-Star International version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Aug 3 22:11:32 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462173] Re: CVE-2015-4167
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462173 Title: CVE-2015-4167 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1495110] Re: External VGA port on laptop does not work anymore
Howard Cheng, as per http://us.acer.com/ac/en/US/content/drivers an update to your computer's buggy and outdated BIOS is available (2.11). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-2.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495110 Title: External VGA port on laptop does not work anymore Status in linux package in Ubuntu: Incomplete Bug description: I have been using the laptop for almost 2 years now, and I have not had problem connecting to a projector via the external VGA port until recently. Sometime between April and now, there must have been a kernel upgrade that messed it up. I saw a few other bug reports that eventually suggests I go to kernel 3.16.0. When I was on 3.13.0-63, my VGA output would work with the boot up screen and the log in screen. But once I log on the VGA port seems to be inactive and I can't get the output back. HDMI still seems to work, though the projectors I have access to don't have HDMI inputs. After I upgraded to 3.16.0, the VGA output would still work during the boot up and log in. Again, once I log on the VGA stopped working. However, when I switched to a text terminal (e.g. Ctrl-Alt-F1) I can see the VGA output again. As soon as I switch back to GUI the VGA output stopped working. The "Display" setting in System Settings cannot find an external monitor, nor could xrandr. My current work around is to use the HDMI port with an HDMI -> VGA converter. That seems to do the trick for now. Both Display setting and xrandr can see the HDMI connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.63.71 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: howard 2074 F pulseaudio /dev/snd/controlC1: howard 2074 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 12 09:48:27 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=931fa86c-ffc4-4421-95e5-3f0ed72ef187 InstallationDate: Installed on 2014-01-10 (610 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Acer Aspire E1-472 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=17eb8564-5cc9-439a-aa44-2160ead649f4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-49-generic N/A linux-backports-modules-3.16.0-49-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-14 (393 days ago) dmi.bios.date: 08/16/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.04. dmi.board.name: EA40_HW dmi.board.vendor: Acer dmi.board.version: V2.04. dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04.:bd08/16/2013:svnAcer:pnAspireE1-472:pvrV2.04.:rvnAcer:rnEA40_HW:rvrV2.04.:cvnAcer:ct9:cvrV2.04.: dmi.product.name: Aspire E1-472 dmi.product.version: V2.04. dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457807] Re: CVE-2015-4036
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1457807 Title: CVE-2015-4036 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source
Re: [Kernel-packages] [Bug 1495102] Re: [Panasonic Corporation CF53-4] hibernate/resume failure
Hello Chris, Model number on sticker is; CF-532ALHYCM I'm sorry, I have not had time to try an upstream kernel yet On 09/15/2015 09:43 PM, Christopher M. Penalver wrote: > Sean Smith, could you please provide the full computer model via the > sticker of the computer itself as per http://business.panasonic.com > /support-computerstablets-downloads-searchdownloads (not from the Bug > Description)? > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495102 Title: [Panasonic Corporation CF53-4] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: Entered " sudo pm-hibernate " Laptop hibernated but wouldn't resume, had to power off. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 [modified: boot/vmlinuz-4.2.0-7-generic] ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sean 1444 F pulseaudio /dev/snd/controlC0: sean 1444 F pulseaudio Date: Sat Sep 12 10:17:40 2015 DuplicateSignature: hibernate/resume:Panasonic Corporation CF53-4:V4.00L16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=9980098f-e9dc-4a15-ba4e-2bb9167e2838 InstallationDate: Installed on 2015-09-12 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) InterpreterPath: /usr/bin/python3.4 MachineType: Panasonic Corporation CF53-4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=9fa82ba6-4fb3-4394-9d8d-fb6faee16f6e ro quiet splash 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-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux Title: [Panasonic Corporation CF53-4] hibernate/resume failure UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L16 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF53-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L16:bd08/28/2014:svnPanasonicCorporation:pnCF53-4:pvr004:rvnPanasonicCorporation:rnCF53-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.name: CF53-4 dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496109] cavac (i386) - tests ran: 2, failed: 2
tests ran: 2, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-10.12/cavac__4.2.0-10.12__2015-09-16_03-28-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473664] Re: package linux-image-extra-3.13.0-57-generic 3.13.0-57.95 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[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/1473664 Title: package linux-image-extra-3.13.0-57-generic 3.13.0-57.95 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: Just doing a normal update and got errors (hopefully automatically included). The only thing that comes to mind to mention is that last update there was a new /etc/default/grub which differed slightly (only a comment line), otherwise this system normally receives updates without issue. Thanks. root@thinker:/etc/default# ls -l grub* -rw-r--r-- 1 root root 1233 Jul 1 13:12 grub -rw-r--r-- 1 root root 1245 Sep 13 2014 grub~ -rw-r--r-- 1 root root 1245 Sep 13 2014 grub.20141014_0902 -rw-r--r-- 1 root root 1276 Oct 14 2014 grub.20150701_1349 root@thinker:/etc/default# diff -u grub.20150701_1349 grub --- grub.20150701_1349 2014-10-14 09:03:17.967881855 -0500 +++ grub2015-07-01 13:12:26.548876556 -0500 @@ -8,7 +8,6 @@ GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` -#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="forcepae" ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-57-generic 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fahnoe 1515 F lxpanel fahnoe 1518 F audacious /dev/snd/pcmC0D0p: fahnoe 1518 F...m audacious /dev/snd/timer: fahnoe 1518 f audacious CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jul 11 10:53:56 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2c06c2c9-eec8-4525-b736-1b052b8786ad InstallationDate: Installed on 2014-09-13 (300 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IwConfig: irda0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 2373xx3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-55-generic root=/dev/mapper/lubuntu--vg-root ro forcepae RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.2 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-extra-3.13.0-57-generic 3.13.0-57.95 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373xx3 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373xx3:pvrThinkPadT40p:rvnIBM:rn2373xx3:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373xx3 dmi.product.version: ThinkPad T40p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496232] Re: CVE-2015-6937
CVE-2015-6937 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6174) is not supported
Here's some information for my card. I definitely haven't experienced any issues with low speeds. $ uname -a Linux flex-3-1470 3.19.0-28-generic #30-Ubuntu SMP Mon Aug 31 15:52:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lspci 02:00.0 Network controller: Qualcomm Atheros Device 0041 (rev 20) $ ifconfig wlan2 Link encap:Ethernet HWaddr ac:e0:10:0d:69:db inet addr:192.168.1.16 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::aee0:10ff:fe0d:69db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14493 errors:0 dropped:0 overruns:0 frame:0 TX packets:14013 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14548693 (14.5 MB) TX bytes:2558985 (2.5 MB) $ sudo lshw *-pci:1 description: PCI bridge product: Wildcat Point-LP PCI Express Root Port #3 vendor: Intel Corporation physical id: 1c.2 bus info: pci@:00:1c.2 version: e3 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:18 memory:c100-c11f *-network description: Wireless interface product: Qualcomm Atheros vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 logical name: wlan2 version: 20 serial: ac:e0:10:0d:69:db width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=3.19.0-28-generic firmware=atheros-12.0.0.102-fw ip=192.168.1.16 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:49 memory:c100-c11f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6174) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1496109] cavac (amd64) - tests ran: 83, failed: 1
tests ran: 83, failed: 1; http://kernel.ubuntu.com/testing/4.2.0-7.7/cavac__4.2.0-7.7__2015-09-15_21-49-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490494] Re: [LENOVO 80H8] hibernate/resume failure
I have tested a few more kernels to see if we can narrow down the problem. It works on the newest 3.13.0 generic kernel, built in August, as well as the 3.19 kernel built in April. The problem has probably been introduced somewhere on the 3.19 line between late .April and late July. I'll try to pin it down later. Platform hibernation works on the following: Linux nb-infomm-09 3.13.0-51-generic #84-Ubuntu SMP Wed Apr 15 12:08:34 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Linux nb-infomm-09 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Linux nb-infomm-09 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux It does not work on: Linux nb-infomm-09 3.19.0-28-generic #30-Ubuntu SMP Mon Aug 31 15:52:51 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 in Ubuntu. https://bugs.launchpad.net/bugs/1490494 Title: [LENOVO 80H8] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: I can't resume from hibernation, as the system seems to stall after PM: Image loading is done, and non-boot CPUs are disabled. The problem appeared after I upgraded from 14.04 to 15.04. I see from the apport-summary that there is a problem with PulseAudio - could it be the cause? I've attached a picture of what my screen shows before I have to do a hard reboot. Sorry about the quality of the picture. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asbjorn1381 F pulseaudio /dev/snd/controlC1: asbjorn1381 F pulseaudio Date: Mon Aug 31 10:28:29 2015 DuplicateSignature: hibernate/resume:LENOVO 80H8:8BCN44WW(V3.07) ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1439395517 Failure: hibernate/resume HibernationDevice: RESUME=UUID=a9cf9119-9b91-4cbd-bd7a-483787652dbd InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 80H8 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: LANGUAGE=en_GB: PATH=(custom, no user) LANG=en_GB.UTF8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=21144522-d804-4a5b-b792-ca3b3753ef47 ro no_console_suspend=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux Title: [LENOVO 80H8] hibernate/resume failure UpgradeStatus: Upgraded to vivid on 2015-07-25 (36 days ago) UserGroups: dmi.bios.date: 07/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN44WW(V3.07) dmi.board.asset.tag: 31900056WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900056WIN dmi.chassis.asset.tag: 31900056WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo M30-70 dmi.modalias: dmi:bvnLENOVO:bvr8BCN44WW(V3.07):bd07/21/2014:svnLENOVO:pn80H8:pvrLenovoM30-70:rvnLENOVO:rnINVALID:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoM30-70: dmi.product.name: 80H8 dmi.product.version: Lenovo M30-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495983] Re: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32
** 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/1495983 Title: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32 Status in linux package in Ubuntu: New Bug description: Attempting to install the latest build of Ubuntu Server 15.10 (Wily Werewolf) x32 on Hyper-V, after beginning installation a kernel panic occurs. The console log from the serial output is attached. http://cdimage.ubuntu.com/ubuntu-server/daily/current/ I tried with the builds from 14th and 15th of September with the same result. This bug does not affect x64 builds. Tried to start the installation with different resources with no effect, kernel panic always occurs no matter the VM settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA
Peter Matulis, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-207 ** Tags added: latest-bios-207 ** Changed in: linux (Ubuntu Wily) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492632 Title: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA Status in linux package in Ubuntu: Incomplete Status in linux source package in Wily: Incomplete Bug description: My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted display. Everything repeatedly shifts horizontally. I found the following in the kernel log. The corruption does not have a 1:1 relation with the occurrence of the error however. === [ 99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 92519) [ 99.275810] [ cut here ] [ 99.275822] WARNING: CPU: 1 PID: 909 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() [ 99.275823] pipe state doesn't match! [ 99.275824] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp mac80211 snd_soc_rt5640 kvm_intel snd_soc_rl6231 snd_soc_core kvm uv cvideo snd_compress ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine snd_hda_codec_conexant videobuf2_vmalloc snd_hda_codec_generic snd_seq_midi iwlwifi videobuf2_memops btusb snd_seq_midi_event serio_raw videobuf2_ core snd_rawmidi btrtl btbcm snd_hda_intel v4l2_common btintel videodev snd_hda_codec cfg80211 lpc_ich bluetooth snd_hda_core input_leds joydev mei_me hid_multitouch media snd_hwdep mei shpchp snd_pcm processor_t hermal_device intel_soc_dts_iosf iosf_mbi snd_seq snd_seq_device snd_timer snd soundcore snd_soc_sst_acpi acpi_pad dw_dmac acpi_als int3402_thermal i2c_designware_platform dw_dmac_core [ 99.275856] kfifo_buf i2c_designware_core 8250_dw spi_pxa2xx_platform industrialio int3400_thermal int340x_thermal_zone mac_hid acpi_thermal_rel sunrpc parport_pc ppdev lp parport autofs4 jitterentropy_rng dr bg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_k ms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid [ 99.275877] CPU: 1 PID: 909 Comm: Xorg Not tainted 4.2.0-7-generic #7-Ubuntu [ 99.275878] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.203 12/11/2014 [ 99.275879] c02ce1e8 8800d3a977e8 817b0465 [ 99.275881] 8800d3a97838 8800d3a97828 81076536 8800d3a97858 [ 99.275883] 8800d3a978c0 8800d374f800 0001 8800d374fb50 [ 99.275885] Call Trace: [ 99.275890] [] dump_stack+0x45/0x57 [ 99.275893] [] warn_slowpath_common+0x86/0xc0 [ 99.275895] [] warn_slowpath_fmt+0x46/0x50 [ 99.275906] [] ? intel_pipe_config_compare+0xb08/0xc60 [i915] [ 99.275916] [] check_crtc_state+0x2c5/0x440 [i915] [ 99.275929] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [ 99.275940] [] intel_crtc_set_config+0x4c7/0x580 [i915] [ 99.275951] [] ? drm_mode_create+0x25/0x60 [drm] [ 99.275959] []
[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA
Eric Carvalho, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** Attachment removed: "dmesg-dell-latitude-e5440.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492632/+attachment/4465364/+files/dmesg-dell-latitude-e5440.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492632 Title: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA Status in linux package in Ubuntu: Incomplete Status in linux source package in Wily: Incomplete Bug description: My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted display. Everything repeatedly shifts horizontally. I found the following in the kernel log. The corruption does not have a 1:1 relation with the occurrence of the error however. === [ 99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 92519) [ 99.275810] [ cut here ] [ 99.275822] WARNING: CPU: 1 PID: 909 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() [ 99.275823] pipe state doesn't match! [ 99.275824] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp mac80211 snd_soc_rt5640 kvm_intel snd_soc_rl6231 snd_soc_core kvm uv cvideo snd_compress ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine snd_hda_codec_conexant videobuf2_vmalloc snd_hda_codec_generic snd_seq_midi iwlwifi videobuf2_memops btusb snd_seq_midi_event serio_raw videobuf2_ core snd_rawmidi btrtl btbcm snd_hda_intel v4l2_common btintel videodev snd_hda_codec cfg80211 lpc_ich bluetooth snd_hda_core input_leds joydev mei_me hid_multitouch media snd_hwdep mei shpchp snd_pcm processor_t hermal_device intel_soc_dts_iosf iosf_mbi snd_seq snd_seq_device snd_timer snd soundcore snd_soc_sst_acpi acpi_pad dw_dmac acpi_als int3402_thermal i2c_designware_platform dw_dmac_core [ 99.275856] kfifo_buf i2c_designware_core 8250_dw spi_pxa2xx_platform industrialio int3400_thermal int340x_thermal_zone mac_hid acpi_thermal_rel sunrpc parport_pc ppdev lp parport autofs4 jitterentropy_rng dr bg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_k ms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid [ 99.275877] CPU: 1 PID: 909 Comm: Xorg Not tainted 4.2.0-7-generic #7-Ubuntu [ 99.275878] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.203 12/11/2014 [ 99.275879] c02ce1e8 8800d3a977e8 817b0465 [ 99.275881] 8800d3a97838 8800d3a97828 81076536 8800d3a97858 [ 99.275883] 8800d3a978c0 8800d374f800 0001 8800d374fb50 [ 99.275885] Call Trace: [ 99.275890] [] dump_stack+0x45/0x57 [ 99.275893] [] warn_slowpath_common+0x86/0xc0 [ 99.275895] [] warn_slowpath_fmt+0x46/0x50 [ 99.275906] [] ? intel_pipe_config_compare+0xb08/0xc60 [i915] [ 99.275916] [] check_crtc_state+0x2c5/0x440 [i915] [ 99.275929] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [ 99.275940] [] intel_crtc_set_config+0x4c7/0x580 [i915] [ 99.275951] [] ? drm_mode_create+0x25/0x60 [drm] [ 99.275959] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 99.275967] [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] [ 99.275973] [] drm_ioctl+0x125/0x610 [drm] [ 99.275980] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 99.275983] [] do_vfs_ioctl+0x285/0x470 [ 99.275986] [] ? recalc_sigpending+0x1f/0x60 [ 99.275988] [] ? __set_task_blocked+0x32/0x70 [ 99.275990] [] SyS_ioctl+0x79/0x90 [ 99.275992] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 99.275994] ---[ end trace 6172e2f40143dd37 ]--- === ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1151 F pulseaudio /dev/snd/controlC1: peter 1151 F pulseaudio Date: Sat Sep 5 15:15:04 2015 InstallationDate: Installed on 2015-07-05 (62 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150704) MachineType: ASUSTeK COMPUTER INC. UX303LAB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic root=UUID=9b60dccb-1ce9-4ddf-82f6-cc03b3c01b5c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic
[Kernel-packages] [Bug 1484221] Re: Kernel panic on HID bluetooth device disconnect
It does seem to be fixed. 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/1484221 Title: Kernel panic on HID bluetooth device disconnect Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: With 4.1.0-3-generic on Ubuntu Wily/15.10 x86_64, I get a kernel panic every time my bluetooth mouse disconnects. This bug has been reported previously for Redhat and Arch: https://bugzilla.redhat.com/show_bug.cgi?id=1250279 https://bugs.archlinux.org/task/45787?string=%5Blinux%5D The details of the trace are attached to those reports. My trace is pretty much identical. A patch has been released that is going to appear in kernel 4.2: http://www.spinics.net/lists/linux-input/msg40330.html Would it be possible to add it as Ubuntu patch? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1494893] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
** Tags added: latest-bios-0603 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1494893 Title: BUG: unable to handle kernel NULL pointer dereference at 0038 Status in linux package in Ubuntu: Incomplete Bug description: while moving files from local hdd to NAS system, Ubuntu locked twice. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: egtaroot 1694 F pulseaudio /dev/snd/controlC1: egtaroot 1694 F pulseaudio Date: Fri Sep 11 21:48:17 2015 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at location RIP: 0010:location location cifs_ioctl_clone.constprop.4+0x127/0x310 [cifs] Failure: oops HibernationDevice: RESUME=UUID=1f126905-ef92-4f88-a1c9-de5d23389d16 InstallationDate: Installed on 2015-08-16 (26 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=40ffe8ef-a968-42ab-9e9a-d648e8a9fb4c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at 0038 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463442] Re: CVE-2015-4001
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463442 Title: CVE-2015-4001 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1463444] Re: CVE-2015-4002
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463444 Title: CVE-2015-4002 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: 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-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-natty 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
[Kernel-packages] [Bug 1494593] Re: Marvell's W8897 WLAN/BT combo card doesn't work from time to time
** Tags added: needs-apport-collect ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1494593 Title: Marvell's W8897 WLAN/BT combo card doesn't work from time to time Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: On cold boot, the W8897 sometimes won't work. And even if it works, the card would fail after reboot. Even more, sometimes it would vanished from PCI bus. There's a race between mwifiex_pcie and mwifiex_usb which causes this issue. Currently as a workaround we can blacklist mwifiex_usb. Marvell is still working on a solution. PCI ID: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Device [11ab:2b38] USB ID: Bus 001 Device 003: ID 1286:2045 Marvell Semiconductor, Inc. And the info in dmesg: [ 7.561183] mwifiex: rx work enabled, cpus 8 [ 8.726729] mwifiex: rx work enabled, cpus 8 [ 8.727110] usbcore: registered new interface driver mwifiex_usb [ 8.796120] usb 1-6: info: FW download over, size 0 bytes [ 8.796123] usb 1-6: info: mwifiex_fw_dpc: unregister device [ 9.361595] mwifiex_pcie :02:00.0: info: FW download over, size 759128 bytes [ 19.760514] mwifiex_pcie :02:00.0: PCI-E is not the winner <0x,1>, exit dnld [ 19.760519] mwifiex_pcie :02:00.0: FW failed to be active in time [ 19.760522] mwifiex_pcie :02:00.0: info: mwifiex_fw_dpc: unregister device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1494593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484799 Title: CVE-2015-5707 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix 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 Committed Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in
[Kernel-packages] [Bug 1489318] Re: CVE-2015-6526
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489318 Title: CVE-2015-6526 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: 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: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status
[Kernel-packages] [Bug 1472165] Re: CVE-2015-5366
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1472165 Title: CVE-2015-5366 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
Re: [Kernel-packages] [Bug 1478250] Re: hp x360 laptop keyboard freezes for 1 sec. every few minutes
Mr. Penalver: Updating the BIOS fixed the problem! This computer has a "born on" date of July 1, yet the current rev. of the Megatrends BIOS is F.25 and one they delivered this machine with was only F.04. So you can mark this one solved, or closed, or whatever the term is (or I will if you ell me what to do) and thanks very much. On Mon, Sep 14, 2015 at 8:57 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > thomas a. sargent, as per http://support.hp.com/us- > en/drivers/selfservice/HP-Spectre-13-4000-x360-Convertible- > PC/7527520/model/8082197 an update to your computer's buggy and outdated > BIOS is available (F.22). If you update to this following > https://help.ubuntu.com/community/BIOSUpdate does it change anything? > > If it doesn't, could you please both specify what happened, and provide > the output of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. As well, you don't > have to create a new bug report. > > Once the BIOS is updated, and the information above is provided, then > please mark this report Status Confirmed. > > Thank you for your understanding. > > ** Attachment removed: "WifiSyslog.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455010/+files/WifiSyslog.txt > > ** Attachment removed: "UdevLog.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455009/+files/UdevLog.txt > > ** Attachment removed: "UdevDb.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455008/+files/UdevDb.txt > > ** Attachment removed: "RfKill.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455007/+files/RfKill.txt > > ** Attachment removed: "PulseList.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455006/+files/PulseList.txt > > ** Attachment removed: "ProcModules.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455005/+files/ProcModules.txt > > ** Attachment removed: "ProcInterrupts.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455004/+files/ProcInterrupts.txt > > ** Attachment removed: "ProcEnviron.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455003/+files/ProcEnviron.txt > > ** Attachment removed: "ProcCpuinfo.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455002/+files/ProcCpuinfo.txt > > ** Attachment removed: "Lsusb.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455001/+files/Lsusb.txt > > ** Attachment removed: "Lspci.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4455000/+files/Lspci.txt > > ** Attachment removed: "IwConfig.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4454999/+files/IwConfig.txt > > ** Attachment removed: "CurrentDmesg.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4454998/+files/CurrentDmesg.txt > > ** Attachment removed: "BootDmesg.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4454997/+files/BootDmesg.txt > > ** Attachment removed: "AlsaInfo.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478250/+attachment/4454996/+files/AlsaInfo.txt > > ** Tags added: bios-outdated-f.22 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1478250 > > Title: > hp x360 laptop keyboard freezes for 1 sec. every few minutes > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > A couple weeks ago Installed ubuntu 14.04 on an hp spectre x360. It > works great except for a strange keyboard problem. Every 2 or 3 > minutes the keyboard freezes for about 1 second - it misses keystrokes > completely. Anything typed during that 1 second period is missed. > For that same period, the LED in the F5 key turns off. The F5 key is > normally illuminated. If you hit it, that turns the LED off and turns > on the keyboard backlight. Hit it again, and the backlight goes off > and F5 lights up again. Apparently while that light is out, the > keyboard is disabled. > > I wrote a program that printed a variable character pattern to a > terminal every 4 times/sec and just watched it. I wanted to know if > the whole computer (or just whole desktop?) was freezing, or just the > keyboard. When the keyboard light turned off, the program kept > running, so I think it's just the keyboard. > > The timing of the light blinking off is variable. If I am not typing, > the light
[Kernel-packages] [Bug 1496109] cavac (amd64) - tests ran: 2, failed: 2
tests ran: 2, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-10.11/cavac__4.2.0-10.11__2015-09-16_04-10-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496109] cavac (i386) - tests ran: 2, failed: 2
tests ran: 2, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-10.12/cavac__4.2.0-10.12__2015-09-16_04-51-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496107] Re: Bluetooth option missing when trying to share images
We don't support sharing something via bluetooth at the moment. It's a missing feature we will implement in the future. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Tags added: after-bluez5 bluetooth ** Changed in: canonical-devices-system-image Status: New => Confirmed -- 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/1496107 Title: Bluetooth option missing when trying to share images Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: In Gallery, I choose the "Images" view (default is "Events"). I tap one, it opens. I tap again, then the upper right corner sign for options. There is Share, choosing that will offer Facebook, Messages, Telegram, Dekko, Tagger, but no Bluetooth. Might be because the previous bug that I submitted? (Bluetooth disconnects in a few seconds). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds
Basically we don't support phone-to-phone connections at the moment. When initiating the connection the Ubuntu device to another phone that will even not be possible as we disable the "connect" button for a phone-type device. However if you make the connection the other way round that depends on which profile the remote wants to use and if the remote device is marked as trusted after it got paired. If it is not marked as trusted there is now way to allow the connection at the moment as we just don't allow it. As already stated on bug 1496107 this is a missing feature and will be added in the future. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Tags added: after-bluez5 bluetooth ** Changed in: canonical-devices-system-image Status: New => Incomplete ** Changed in: canonical-devices-system-image Status: Incomplete => Confirmed -- 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/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA
I tried an older upstream kernel (v4.0-vivid) and the errant log messages do not appear: $ uname -r 4.0.0-04-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492632 Title: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: Confirmed Bug description: My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted display. Everything repeatedly shifts horizontally. I found the following in the kernel log. The corruption does not have a 1:1 relation with the occurrence of the error however. === [ 99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 92519) [ 99.275810] [ cut here ] [ 99.275822] WARNING: CPU: 1 PID: 909 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() [ 99.275823] pipe state doesn't match! [ 99.275824] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp mac80211 snd_soc_rt5640 kvm_intel snd_soc_rl6231 snd_soc_core kvm uv cvideo snd_compress ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine snd_hda_codec_conexant videobuf2_vmalloc snd_hda_codec_generic snd_seq_midi iwlwifi videobuf2_memops btusb snd_seq_midi_event serio_raw videobuf2_ core snd_rawmidi btrtl btbcm snd_hda_intel v4l2_common btintel videodev snd_hda_codec cfg80211 lpc_ich bluetooth snd_hda_core input_leds joydev mei_me hid_multitouch media snd_hwdep mei shpchp snd_pcm processor_t hermal_device intel_soc_dts_iosf iosf_mbi snd_seq snd_seq_device snd_timer snd soundcore snd_soc_sst_acpi acpi_pad dw_dmac acpi_als int3402_thermal i2c_designware_platform dw_dmac_core [ 99.275856] kfifo_buf i2c_designware_core 8250_dw spi_pxa2xx_platform industrialio int3400_thermal int340x_thermal_zone mac_hid acpi_thermal_rel sunrpc parport_pc ppdev lp parport autofs4 jitterentropy_rng dr bg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_k ms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid [ 99.275877] CPU: 1 PID: 909 Comm: Xorg Not tainted 4.2.0-7-generic #7-Ubuntu [ 99.275878] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.203 12/11/2014 [ 99.275879] c02ce1e8 8800d3a977e8 817b0465 [ 99.275881] 8800d3a97838 8800d3a97828 81076536 8800d3a97858 [ 99.275883] 8800d3a978c0 8800d374f800 0001 8800d374fb50 [ 99.275885] Call Trace: [ 99.275890] [] dump_stack+0x45/0x57 [ 99.275893] [] warn_slowpath_common+0x86/0xc0 [ 99.275895] [] warn_slowpath_fmt+0x46/0x50 [ 99.275906] [] ? intel_pipe_config_compare+0xb08/0xc60 [i915] [ 99.275916] [] check_crtc_state+0x2c5/0x440 [i915] [ 99.275929] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [ 99.275940] [] intel_crtc_set_config+0x4c7/0x580 [i915] [ 99.275951] [] ? drm_mode_create+0x25/0x60 [drm] [ 99.275959] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 99.275967] [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] [ 99.275973] [] drm_ioctl+0x125/0x610 [drm] [ 99.275980] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 99.275983] [] do_vfs_ioctl+0x285/0x470 [ 99.275986] [] ? recalc_sigpending+0x1f/0x60 [ 99.275988] [] ? __set_task_blocked+0x32/0x70 [ 99.275990] [] SyS_ioctl+0x79/0x90 [ 99.275992] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 99.275994] ---[ end trace 6172e2f40143dd37 ]--- === ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1151 F pulseaudio /dev/snd/controlC1: peter 1151 F pulseaudio Date: Sat Sep 5 15:15:04 2015 InstallationDate: Installed on 2015-07-05 (62 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150704) MachineType: ASUSTeK COMPUTER INC. UX303LAB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic root=UUID=9b60dccb-1ce9-4ddf-82f6-cc03b3c01b5c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
[Kernel-packages] [Bug 1496232] [NEW] CVE-2015-6937
*** This bug is a security vulnerability *** Public security bug reported: Description needed Break-Fix: - 74e98eb085889b0d2d4908f59f6e00026063014f ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Low Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Low Status: New ** Affects: linux-manta (Ubuntu) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Low Status: New ** Affects: linux-armadaxp
[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised
I have the same problem on my Ubuntu Server Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-63-generic x86_64) Plug in a USB 3 powered drive and I get: Sep 16 14:38:16 fuller kernel: [ 258.785743] usb 3-4: new full-speed USB device number 2 using xhci_hcd Sep 16 14:38:16 fuller kernel: [ 258.785913] usb 3-4: Device not responding to set address. Sep 16 14:38:16 fuller kernel: [ 258.989962] usb 3-4: Device not responding to set address. Sep 16 14:38:16 fuller kernel: [ 259.193931] usb 3-4: device not accepting address 2, error -71 Sep 16 14:38:16 fuller kernel: [ 259.305981] usb 3-4: new full-speed USB device number 3 using xhci_hcd Sep 16 14:38:16 fuller kernel: [ 259.306146] usb 3-4: Device not responding to set address. Sep 16 14:38:17 fuller kernel: [ 259.510201] usb 3-4: Device not responding to set address. Sep 16 14:38:17 fuller kernel: [ 259.714169] usb 3-4: device not accepting address 3, error -71 Sep 16 14:38:17 fuller kernel: [ 259.826218] usb 3-4: new full-speed USB device number 4 using xhci_hcd Sep 16 14:38:17 fuller kernel: [ 259.826387] usb 3-4: Device not responding to set address. Sep 16 14:38:17 fuller kernel: [ 260.030471] usb 3-4: Device not responding to set address. Sep 16 14:38:17 fuller kernel: [ 260.234411] usb 3-4: device not accepting address 4, error -71 Sep 16 14:38:17 fuller kernel: [ 260.346462] usb 3-4: new full-speed USB device number 5 using xhci_hcd Sep 16 14:38:17 fuller kernel: [ 260.346624] usb 3-4: Device not responding to set address. Sep 16 14:38:18 fuller kernel: [ 260.550715] usb 3-4: Device not responding to set address. Sep 16 14:38:18 fuller kernel: [ 260.754648] usb 3-4: device not accepting address 5, error -71 Sep 16 14:38:18 fuller kernel: [ 260.754749] hub 3-0:1.0: unable to enumerate USB device on port 4 politas@fuller:~$ lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M Tried the autosuspend workaround mentioned above with no change. How do we undo that, by the way? -- You 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 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
Eric Carvalho, please do not mark this a duplicate of another report, or vice versa. ** This bug is no longer a duplicate of bug 1492632 [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492764 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Status in linux package in Ubuntu: Incomplete Bug description: System: Kubuntu 15.10 Since kernel version 4.2 I have a few of this errors: Sep 06 16:16:35 benediktZ50-70 kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Sep 06 16:16:35 benediktZ50-70 kernel: [ cut here ] Sep 06 16:16:35 benediktZ50-70 kernel: WARNING: CPU: 0 PID: 187 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() Sep 06 16:16:35 benediktZ50-70 kernel: pipe state doesn't match! Sep 06 16:16:35 benediktZ50-70 kernel: Modules linked in: rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci r8169 mii sdhci_acpi video sdhci i2c_hid hid Sep 06 16:16:35 benediktZ50-70 kernel: CPU: 0 PID: 187 Comm: plymouthd Tainted: GW 4.2.0-7-generic #7-Ubuntu Sep 06 16:16:35 benediktZ50-70 kernel: Hardware name: LENOVO 20354/Lancer 5A5, BIOS 9BCN91WW 07/21/2015 Sep 06 16:16:35 benediktZ50-70 kernel: c023f1e8 8802413277e8 817b0465 Sep 06 16:16:35 benediktZ50-70 kernel: 880241327838 880241327828 81076536 880241327858 Sep 06 16:16:35 benediktZ50-70 kernel: 8802413278c0 880241152000 0001 880241152350 Sep 06 16:16:35 benediktZ50-70 kernel: Call Trace: Sep 06 16:16:35 benediktZ50-70 kernel: [] dump_stack+0x45/0x57 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_common+0x86/0xc0 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_fmt+0x46/0x50 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] check_crtc_state+0x2c5/0x440 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_modeset_check_state+0x20e/0x6b0 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_crtc_set_config+0x4c7/0x580 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_create+0x25/0x60 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_set_config_internal+0x66/0x100 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_ioctl+0x125/0x610 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] do_vfs_ioctl+0x285/0x470 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? do_munmap+0x349/0x480 Sep 06 16:16:35 benediktZ50-70 kernel: [] SyS_ioctl+0x79/0x90 Sep 06 16:16:35 benediktZ50-70 kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Sep 06 16:16:35 benediktZ50-70 kernel: ---[ end trace 724377a3c01e4270 ]--- I will check next week if these errors have any impact on my system. This is a Nvidia Optimus System with the Intel graphic card activated by default. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benedikt 1550 F pulseaudio /dev/snd/controlC1: benedikt 1550 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 6 16:22:48 2015 HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf InstallationDate: Installed on 2014-12-21 (259 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141218) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias:
[Kernel-packages] [Bug 1388975] Re: CVE-2014-8559
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1388975 Title: CVE-2014-8559 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix 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: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source
[Kernel-packages] [Bug 1492850] Re: Dell pro venue 11 - No wireless connections after sleep
stef.baly, as per http://www.dell.com/support/home/us/en/19/product- support/product/dell-venue-11i-pro/drivers/advanced an update to your computer's buggy and outdated BIOS is available (A16). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Description changed: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes After suspend (no more wifi chipset !). @utopie:~$ sudo lshw -C network *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes - --- - ApportVersion: 2.17.2-0ubuntu1.4 - Architecture: amd64 - CurrentDesktop: Unity - DistroRelease: Ubuntu 15.04 - InstallationDate: Installed on 2015-04-23 (136 days ago) - InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) - Package: linux (not installed) - Tags: vivid - Uname: Linux 4.2.0-040200rc8-generic x86_64 - UnreportableReason: The running kernel is not an Ubuntu kernel - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - _MarkForUpload: True - --- - ApportVersion: 2.17.2-0ubuntu1.4 - Architecture: amd64 - CurrentDesktop: Unity - DistroRelease: Ubuntu 15.04 - InstallationDate: Installed on 2015-04-23 (144 days ago) - InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) - Package: linux (not installed) - Tags: vivid - Uname: Linux 4.2.0-040200-generic x86_64 - UnreportableReason: The running kernel is not an Ubuntu kernel - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - _MarkForUpload: True - --- + + --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: baly 1169 F pulseaudio - /dev/snd/controlC1: baly 1169 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: baly 1169 F pulseaudio + /dev/snd/controlC1: baly 1169 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=729324f1-42a5-45f8-9585-f6e0169f2d64 InstallationDate: Installed on 2015-04-23 (144 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Venue 11 Pro 7130 vPro Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed root=UUID=35cde4a5-bbc3-442b-b239-d3f917925a94 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1416503] Re: CVE-2015-1420
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1416503 Title: CVE-2015-1420 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Released Status in
[Kernel-packages] [Bug 1462170] Re: CVE-2015-1805
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462170 Title: CVE-2015-1805 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51
[Kernel-packages] [Bug 1462169] Re: CVE-2014-9731
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462169 Title: CVE-2014-9731 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1496163] [NEW] Wily: firmware load for i915/skl_dmc_ver1.bin failed with error -2
Public bug reported: On Skylake, the skl_dmc firmware is failing to load. From dmesg: [0.728803] i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) This means the GPU can't enter its lowest available power states, plus many display hotplugging scenarios (that only the skl_dmc firmware can handle) are broken. On a whim I tried some other firmware versions: 1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin (instead of skl_dmc_ver1_19.bin) 2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the skl_dmc_ver1.bin symlink to it But neither corrected the situation. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1251 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 15 16:21:24 2015 HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f IwConfig: enp4s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 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: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: Default string dmi.board.name: Z170-P D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1496163 Title: Wily: firmware load for i915/skl_dmc_ver1.bin failed with error -2 Status in linux package in Ubuntu: New Bug description: On Skylake, the skl_dmc firmware is failing to load. From dmesg: [0.728803] i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) This means the GPU can't enter its lowest available power states, plus many display hotplugging scenarios (that only the skl_dmc firmware can handle) are broken. On a whim I tried some other firmware versions: 1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin (instead of skl_dmc_ver1_19.bin) 2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the skl_dmc_ver1.bin symlink to it But neither corrected the situation. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1251 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 15 16:21:24 2015 HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f IwConfig: enp4s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002
[Kernel-packages] [Bug 1491761] Re: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04
** Tags added: bios-outdated-f.23 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491761 Title: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04 Status in linux package in Ubuntu: Incomplete Bug description: (eth0): carrier is OFF Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 2 20:00:32 cq71 NetworkManager[579]: [1441216832.927980] [platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 2: mtu 0 (1) driver 'r8169' udi '/sys/devices/pci:00/:00:1c.1/:03:00.0/net/eth0': Invalid address for specified address family Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): preparing device r8169 :03:00.0 eth0: RTL8102e at 0xc90004778000, 00:00:00:00:00:00, XID 04c0 IRQ 27 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Subsystem: Hewlett-Packard Company Device 306c Kernel driver in use: r8169 *-network DISABLED description: Ethernet interface product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 02 size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full latency=0 link=no multicast=yes port=MII speed=100Mbit/s resources: irq:27 ioport:2000(size=256) memory:d401-d4010fff memory:d400-d400 memory:d500-d500 i compiled the r8101 module from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false after i put in a "cloned mac adress" the card is functional. there is also an old bug report of this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256331 --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 1084 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6f27858b-0ba5-46f9-b656-36f652d32cb0 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=c8c26d44-1f21-4878-8430-8e0fe79ffcc4 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev' Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 306C dmi.board.vendor: Quanta dmi.board.version: 21.12 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.14:bd09/22/2009:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn306C:rvr21.12:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496109] fozzie (amd64) - tests ran: 194, failed: 0
tests ran: 194, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-10.11/fozzie__4.2.0-10.11__2015-09-15_21-35-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462164] Re: CVE-2014-9728
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462164 Title: CVE-2014-9728 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1448291] Re: CVE-2014-8171
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1448291 Title: CVE-2014-8171 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2
[Kernel-packages] [Bug 1430949] Re: CVE-2014-8172
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1430949 Title: CVE-2014-8172 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: 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: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1471096] Re: CVE-2015-3212
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1471096 Title: CVE-2015-3212 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1441108] Re: CVE-2015-2925
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1441108 Title: CVE-2015-2925 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily:
[Kernel-packages] [Bug 1463740] Re: CVE-2015-4004
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463740 Title: CVE-2015-4004 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
** Tags added: latest-bios-a09 regression-update ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Incomplete Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490494] Re: [LENOVO 80H8] hibernate/resume failure
Asbjørn Nilsen Riseth, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490494 Title: [LENOVO 80H8] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: I can't resume from hibernation, as the system seems to stall after PM: Image loading is done, and non-boot CPUs are disabled. The problem appeared after I upgraded from 14.04 to 15.04. I see from the apport-summary that there is a problem with PulseAudio - could it be the cause? I've attached a picture of what my screen shows before I have to do a hard reboot. Sorry about the quality of the picture. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asbjorn1381 F pulseaudio /dev/snd/controlC1: asbjorn1381 F pulseaudio Date: Mon Aug 31 10:28:29 2015 DuplicateSignature: hibernate/resume:LENOVO 80H8:8BCN44WW(V3.07) ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1439395517 Failure: hibernate/resume HibernationDevice: RESUME=UUID=a9cf9119-9b91-4cbd-bd7a-483787652dbd InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 80H8 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: LANGUAGE=en_GB: PATH=(custom, no user) LANG=en_GB.UTF8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=21144522-d804-4a5b-b792-ca3b3753ef47 ro no_console_suspend=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux Title: [LENOVO 80H8] hibernate/resume failure UpgradeStatus: Upgraded to vivid on 2015-07-25 (36 days ago) UserGroups: dmi.bios.date: 07/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN44WW(V3.07) dmi.board.asset.tag: 31900056WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900056WIN dmi.chassis.asset.tag: 31900056WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo M30-70 dmi.modalias: dmi:bvnLENOVO:bvr8BCN44WW(V3.07):bd07/21/2014:svnLENOVO:pn80H8:pvrLenovoM30-70:rvnLENOVO:rnINVALID:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoM30-70: dmi.product.name: 80H8 dmi.product.version: Lenovo M30-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438501] Re: CVE-2014-9710
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1438501 Title: CVE-2014-9710 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-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 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: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid
[Kernel-packages] [Bug 1462167] Re: CVE-2014-9730
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462167 Title: CVE-2014-9730 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1462165] Re: CVE-2014-9729
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462165 Title: CVE-2014-9729 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1477026] Re: CVE-2015-3290
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1477026 Title: CVE-2015-3290 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51
[Kernel-packages] [Bug 1462175] Re: CVE-2015-4170
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1462175 Title: CVE-2015-4170 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New
[Kernel-packages] [Bug 1478826] Re: CVE-2015-5157
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1478826 Title: CVE-2015-5157 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily:
[Kernel-packages] [Bug 1495102] Re: [Panasonic Corporation CF53-4] hibernate/resume failure
Sean Smith, could you please provide the full computer model via the sticker of the computer itself as per http://business.panasonic.com /support-computerstablets-downloads-searchdownloads (not from the Bug Description)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495102 Title: [Panasonic Corporation CF53-4] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: Entered " sudo pm-hibernate " Laptop hibernated but wouldn't resume, had to power off. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 [modified: boot/vmlinuz-4.2.0-7-generic] ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sean 1444 F pulseaudio /dev/snd/controlC0: sean 1444 F pulseaudio Date: Sat Sep 12 10:17:40 2015 DuplicateSignature: hibernate/resume:Panasonic Corporation CF53-4:V4.00L16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=9980098f-e9dc-4a15-ba4e-2bb9167e2838 InstallationDate: Installed on 2015-09-12 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) InterpreterPath: /usr/bin/python3.4 MachineType: Panasonic Corporation CF53-4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=9fa82ba6-4fb3-4394-9d8d-fb6faee16f6e ro quiet splash 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-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux Title: [Panasonic Corporation CF53-4] hibernate/resume failure UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L16 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF53-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L16:bd08/28/2014:svnPanasonicCorporation:pnCF53-4:pvr004:rvnPanasonicCorporation:rnCF53-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.name: CF53-4 dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469320] Re: CVE-2015-4700
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1469320 Title: CVE-2015-4700 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1469315] Re: CVE-2015-4692
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1469315 Title: CVE-2015-4692 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1489314] Re: CVE-2015-6252
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489314 Title: CVE-2015-6252 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: 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: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in
[Kernel-packages] [Bug 1484797] Re: CVE-2015-5706
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484797 Title: CVE-2015-5706 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source
[Kernel-packages] [Bug 1496109] cavac (amd64) - tests ran: 2, failed: 2
tests ran: 2, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-10.11/cavac__4.2.0-10.11__2015-09-16_02-46-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/1496109 Title: linux: 4.2.0-10.12 -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: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-10.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 15. September 2015 19:27 UTC kernel-phase-changed:Tuesday, 15. September 2015 19:27 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1496109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495782] Re: Suspend / Hibernate will toggle Wifi / BT status on Trusty
As per Ara, this should be a greylist bug. (Unless the wireless key can't make it work, thus it will be a bl -- 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/1495782 Title: Suspend / Hibernate will toggle Wifi / BT status on Trusty Status in HWE Next: New Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: CID: 201412-16319 Dell Latitude 3150 CID: 201407-15273 Dell Latitude 3450 Running hibernate or suspend will trigger a rfkill event on resume and toggle both of the Wireless network and Bluetooth, so they will be blocked when you suspend it for the first time, and be re-enabled when you suspend it again. After the first suspend, "rfkill list" shows: ubuntu@201412-16319:~$ cat rfkill 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes 1: dell-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no You may unblock then with the wireless hotkey, however, on 201412-16319, sometime the wireless can't be re-enable with the hotkey (fail rate: 3~4 out of 12), I will need to suspend this system again to make wireless back to work. (0 out of 12 on 201407-15273) I noticed that this issue seems to happen only on the system with an individual wireless key input event: $ sudo evtest /dev/input/event6:DELL Wireless hotkeys (A 14.04.2 certified Dell Vostro 5470 ,CID: 201307-14037, does not have this issue, and it does not have a wireless key input event in evtest, the wireless key event is called KEY_WLAN and is integrated in Dell WMI hotkeys event) If you use evtest to monitor this wireless hotkey event, I can see that it will send a rfkill event after resume from suspend: ubuntu@201407-15273:~$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Sleep Button /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:SynPS/2 Synaptics TouchPad /dev/input/event6:DELL Wireless hotkeys /dev/input/event7:Video Bus /dev/input/event8:HDA Intel PCH Headphone Mic /dev/input/event9:Dell WMI hotkeys /dev/input/event10: HDA Intel HDMI HDMI/DP,pcm=3 /dev/input/event11: HDA Intel HDMI HDMI/DP,pcm=7 /dev/input/event12: HDA Intel HDMI HDMI/DP,pcm=8 /dev/input/event13: Integrated_Webcam_HD Select the device event number [0-13]: 6 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "DELL Wireless hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 247 (KEY_RFKILL) Properties: Testing ... (interrupt to exit) Event: time 1442315336.476988, -- SYN_REPORT Event: time 1442315379.463923, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1442315379.463923, -- SYN_REPORT Event: time 1442315379.463927, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1442315379.463927, -- SYN_REPORT (The first SYN_REPORT here is for suspend, as when you press the wireless hotkey it will send out the "type 1 (EV_KEY)" information first) Steps to reproduce: 1. Install 14.04.2 + update 2. Suspend it from the system menu 3. Wake it up. 4. Suspend it again. 5. Wake it up Expected result: * Wireless and Bluetooth should be working all the time. Actual result: * They got disabled on the first, third, fifth... cycle. You can verify it here with "sudo pm-hibernate" too, and will get the same result. This issue can be reproduced on 3.16 and 3.19 kernel. And some pre- installed systems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 00:17:34 2015 InstallationDate: Installed on 2015-09-11 (4 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) --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1574 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice:
[Kernel-packages] [Bug 1495782] Re: Suspend / Hibernate will toggle Wifi / BT status on Trusty
As per Ara, this should be a greylist bug. (Unless the wireless key can't make it work, thus it will be a blocker for 201412-16319) ** Tags added: certification-grey -- 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/1495782 Title: Suspend / Hibernate will toggle Wifi / BT status on Trusty Status in HWE Next: New Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: CID: 201412-16319 Dell Latitude 3150 CID: 201407-15273 Dell Latitude 3450 Running hibernate or suspend will trigger a rfkill event on resume and toggle both of the Wireless network and Bluetooth, so they will be blocked when you suspend it for the first time, and be re-enabled when you suspend it again. After the first suspend, "rfkill list" shows: ubuntu@201412-16319:~$ cat rfkill 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes 1: dell-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no You may unblock then with the wireless hotkey, however, on 201412-16319, sometime the wireless can't be re-enable with the hotkey (fail rate: 3~4 out of 12), I will need to suspend this system again to make wireless back to work. (0 out of 12 on 201407-15273) I noticed that this issue seems to happen only on the system with an individual wireless key input event: $ sudo evtest /dev/input/event6:DELL Wireless hotkeys (A 14.04.2 certified Dell Vostro 5470 ,CID: 201307-14037, does not have this issue, and it does not have a wireless key input event in evtest, the wireless key event is called KEY_WLAN and is integrated in Dell WMI hotkeys event) If you use evtest to monitor this wireless hotkey event, I can see that it will send a rfkill event after resume from suspend: ubuntu@201407-15273:~$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Sleep Button /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:SynPS/2 Synaptics TouchPad /dev/input/event6:DELL Wireless hotkeys /dev/input/event7:Video Bus /dev/input/event8:HDA Intel PCH Headphone Mic /dev/input/event9:Dell WMI hotkeys /dev/input/event10: HDA Intel HDMI HDMI/DP,pcm=3 /dev/input/event11: HDA Intel HDMI HDMI/DP,pcm=7 /dev/input/event12: HDA Intel HDMI HDMI/DP,pcm=8 /dev/input/event13: Integrated_Webcam_HD Select the device event number [0-13]: 6 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "DELL Wireless hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 247 (KEY_RFKILL) Properties: Testing ... (interrupt to exit) Event: time 1442315336.476988, -- SYN_REPORT Event: time 1442315379.463923, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1442315379.463923, -- SYN_REPORT Event: time 1442315379.463927, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1442315379.463927, -- SYN_REPORT (The first SYN_REPORT here is for suspend, as when you press the wireless hotkey it will send out the "type 1 (EV_KEY)" information first) Steps to reproduce: 1. Install 14.04.2 + update 2. Suspend it from the system menu 3. Wake it up. 4. Suspend it again. 5. Wake it up Expected result: * Wireless and Bluetooth should be working all the time. Actual result: * They got disabled on the first, third, fifth... cycle. You can verify it here with "sudo pm-hibernate" too, and will get the same result. This issue can be reproduced on 3.16 and 3.19 kernel. And some pre- installed systems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 00:17:34 2015 InstallationDate: Installed on 2015-09-11 (4 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) --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1574 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu
[Kernel-packages] [Bug 1489314] Re: CVE-2015-6252
** 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/1489314 Title: CVE-2015-6252 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: 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: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty
[Kernel-packages] [Bug 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
Benedikt, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492764 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Status in linux package in Ubuntu: Incomplete Bug description: System: Kubuntu 15.10 Since kernel version 4.2 I have a few of this errors: Sep 06 16:16:35 benediktZ50-70 kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Sep 06 16:16:35 benediktZ50-70 kernel: [ cut here ] Sep 06 16:16:35 benediktZ50-70 kernel: WARNING: CPU: 0 PID: 187 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() Sep 06 16:16:35 benediktZ50-70 kernel: pipe state doesn't match! Sep 06 16:16:35 benediktZ50-70 kernel: Modules linked in: rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci r8169 mii sdhci_acpi video sdhci i2c_hid hid Sep 06 16:16:35 benediktZ50-70 kernel: CPU: 0 PID: 187 Comm: plymouthd Tainted: GW 4.2.0-7-generic #7-Ubuntu Sep 06 16:16:35 benediktZ50-70 kernel: Hardware name: LENOVO 20354/Lancer 5A5, BIOS 9BCN91WW 07/21/2015 Sep 06 16:16:35 benediktZ50-70 kernel: c023f1e8 8802413277e8 817b0465 Sep 06 16:16:35 benediktZ50-70 kernel: 880241327838 880241327828 81076536 880241327858 Sep 06 16:16:35 benediktZ50-70 kernel: 8802413278c0 880241152000 0001 880241152350 Sep 06 16:16:35 benediktZ50-70 kernel: Call Trace: Sep 06 16:16:35 benediktZ50-70 kernel: [] dump_stack+0x45/0x57 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_common+0x86/0xc0 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_fmt+0x46/0x50 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] check_crtc_state+0x2c5/0x440 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_modeset_check_state+0x20e/0x6b0 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_crtc_set_config+0x4c7/0x580 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_create+0x25/0x60 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_set_config_internal+0x66/0x100 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_ioctl+0x125/0x610 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] do_vfs_ioctl+0x285/0x470 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? do_munmap+0x349/0x480 Sep 06 16:16:35 benediktZ50-70 kernel: [] SyS_ioctl+0x79/0x90 Sep 06 16:16:35 benediktZ50-70 kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Sep 06 16:16:35 benediktZ50-70 kernel: ---[ end trace 724377a3c01e4270 ]--- I will check next week if these errors have any impact on my system. This is a Nvidia Optimus System with the Intel graphic card activated by default. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID
[Kernel-packages] [Bug 1453256] Re: CVE-2015-3636
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1453256 Title: CVE-2015-3636 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in
[Kernel-packages] [Bug 1494092] Re: After docking/undocking, tooltips cause the UI to become briefly unresponsive
** Tags added: bios-outdated-1.45 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1494092 Title: After docking/undocking, tooltips cause the UI to become briefly unresponsive Status in linux package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 which I use frequently both undocked and docked with dual monitors. It all works fine when it is first powered on in either configuration, as well as when it awakes from sleep. However, once I switch to the opposite configuration from the initial power-up, I experience brief moments of unresponsiveness. I switch between configurations by entering suspend (sleep), either docking or undocking the laptop, and then returning from suspend mode. The unresponsiveness is most often triggered by tooltips appearing in any program, and the system remains unresponsive until the tooltip disappears. The behavior may occur for other types of windows or UI components, but I can't say for certain. When I'm experiencing this issue, the mouse moves and most screen updates still happen (It will cause most video playback to pause, however). However, mouse clicks and typing are ignored or queued up. I'm using Ubuntu 15.04, with the nvidia-355 binary driver. I've used other versions of the nvidia driver, and they have all exhibited this behavior or had other issues. I don't recall having this issue with 14.10, but I can't confirm it. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: troy 3291 F pulseaudio /dev/snd/controlC0: troy 3291 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ae9c899d-aaf8-42e8-9165-ffc08269576c InstallationDate: Installed on 2015-03-26 (168 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 4239CTO NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=6113f906-aaea-4e54-abf5-3722066a6a6d ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489318] Re: CVE-2015-6526
** 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/1489318 Title: CVE-2015-6526 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: 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: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in linux-lts-quantal
[Kernel-packages] [Bug 1061508] Re: System Boots Every Other Time
tjboadwa, you would need to do use Ubuntu in order to follow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1061508/comments/10 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1061508 Title: System Boots Every Other Time Status in linux package in Ubuntu: Expired Bug description: After a fresh install of 12.04.1 the system boots every other time it's started or restarted. When it doesn't boot the screen goes to sleep as the system hangs/freezes. The system boots fine under 10.04.4. Steps to reproduce: 1) Install using 12.04.1 2) Boot the system 3) If the system boots properly restart or shutdown the system ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: name 2478 F pulseaudio /dev/snd/pcmC0D0p: name 2478 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a58,0011' Controls : 40 Simple ctrls : 21 Date: Thu Oct 4 06:05:55 2012 HibernationDevice: RESUME=UUID=9d64ac90-738f-49eb-a637-ad5473e780b4 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP-Pavilion GC384AV-ABA m8000e ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic-pae root=/dev/mapper/sda6_crypt ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-31-generic-pae N/A linux-backports-modules-3.2.0-31-generic-pae N/A linux-firmware1.79.1 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UdevDb: Error: [Errno 2] No such file or directory UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.09 dmi.board.name: NARRA dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd05/15/2007:svnHP-Pavilion:pnGC384AV-ABAm8000e:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GC384AV-ABA m8000e dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1061508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA
Tags added as requested. $ uname -r 4.2.0-040200-generic End of dmesg upon reboot into upstream kernel: -- 8< -- [ 15.530865] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 92519) [ 15.530868] [ cut here ] [ 15.530881] WARNING: CPU: 0 PID: 960 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x282/0x3f0 [i915]() [ 15.530882] pipe state doesn't match! [ 15.530883] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core intel_rapl x86_pkg_temp_thermal v4l2_common intel_powerclamp coretemp videodev kvm_intel snd_hda_codec_hdmi iwlmvm kvm input_leds media mac80211 snd_hda_codec_conexant snd_soc_rt5640 snd_hda_codec_generic joydev serio_raw snd_soc_rl6231 snd_hda_intel btusb btrtl btbcm hid_multitouch btintel iwlwifi bluetooth snd_hda_codec mei_me cfg80211 snd_soc_core mei snd_hda_core snd_hwdep snd_compress processor_thermal_device ac97_bus snd_pcm_dmaengine intel_soc_dts_iosf iosf_mbi snd_pcm lpc_ich shpchp snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore acpi_als int3400_thermal kfifo_buf industrialio acpi_thermal_rel dw_dmac int3402_thermal [ 15.530913] int340x_thermal_zone dw_dmac_core i2c_designware_platform snd_soc_sst_acpi 8250_dw spi_pxa2xx_platform i2c_designware_core acpi_pad mac_hid parport_pc ppdev lp parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid [ 15.530934] CPU: 0 PID: 960 Comm: Xorg Not tainted 4.2.0-040200-generic #201508301530 [ 15.530935] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.207 03/23/2015 [ 15.530936] c022cc48 880213f9f7f8 817a1b43 [ 15.530938] 880213f9f848 880213f9f838 8107719a 880213f9f868 [ 15.530940] 880214dd6b48 880213f9f8d0 880214dd6800 880214f9b000 [ 15.530942] Call Trace: [ 15.530946] [] dump_stack+0x45/0x57 [ 15.530949] [] warn_slowpath_common+0x8a/0xc0 [ 15.530951] [] warn_slowpath_fmt+0x46/0x50 [ 15.530963] [] ? intel_pipe_config_compare+0xa2d/0xcc0 [i915] [ 15.530974] [] check_crtc_state+0x282/0x3f0 [i915] [ 15.530987] [] intel_modeset_check_state+0x292/0x6b0 [i915] [ 15.530999] [] intel_crtc_set_config+0x3ea/0x5a0 [i915] [ 15.531009] [] drm_mode_set_config_internal+0x68/0x100 [drm] [ 15.531018] [] drm_mode_setcrtc+0xdd/0x4f0 [drm] [ 15.531024] [] drm_ioctl+0x363/0x680 [drm] [ 15.531031] [] ? drm_mode_setplane+0x1c0/0x1c0 [drm] [ 15.531034] [] do_vfs_ioctl+0x2cd/0x4b0 [ 15.531037] [] ? __set_task_blocked+0x32/0x70 [ 15.531039] [] ? __set_current_blocked+0x36/0x60 [ 15.531041] [] SyS_ioctl+0x79/0x90 [ 15.531043] [] ? SyS_rt_sigprocmask+0x86/0xb0 [ 15.531046] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 15.531047] ---[ end trace 6474de6e6264cf1a ]--- [ 18.672546] wlp2s0: authenticate with 00:22:b0:05:f8:36 [ 18.678236] wlp2s0: send auth to 00:22:b0:05:f8:36 (try 1/3) [ 18.703845] wlp2s0: authenticated [ 18.704751] wlp2s0: associate with 00:22:b0:05:f8:36 (try 1/3) [ 18.707578] wlp2s0: RX AssocResp from 00:22:b0:05:f8:36 (capab=0x431 status=0 aid=1) [ 18.708637] wlp2s0: associated [ 18.708660] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready [ 18.711406] cfg80211: Regulatory domain changed to country: US [ 18.711409] cfg80211: DFS Master region: FCC [ 18.711410] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 18.711412] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 3000 mBm), (N/A) [ 18.711414] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 1700 mBm), (N/A) [ 18.711415] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2300 mBm), (0 s) [ 18.711416] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 3000 mBm), (N/A) [ 18.711417] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) -- 8< -- ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.2 ** Changed in: linux (Ubuntu Wily) 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/1492632 Title: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: Confirmed
[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707
** 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/1484799 Title: CVE-2015-5707 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix 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 Committed Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source
[Kernel-packages] [Bug 1494006] Re: linux-ti-omap4: 3.2.0-1471.92 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 09. September 2015 21:13 UTC kernel-stable-master-bug:1493780 kernel-stable-Certification-testing-end:Monday, 14. September 2015 13:00 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-start:Monday, 14. September 2015 15:00 UTC - kernel-stable-phase-changed:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:23 UTC + kernel-stable-phase:Verification & Testing + kernel-stable-phase-changed:Tuesday, 15. September 2015 22:01 UTC + kernel-stable-Security-signoff-start:Tuesday, 15. September 2015 22:01 UTC + kernel-stable-Regression-testing-start:Tuesday, 15. September 2015 22:01 UTC + proposed-announcement-sent:True + kernel-stable-Verification-testing-start:Tuesday, 15. September 2015 22:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1494006 Title: linux-ti-omap4: 3.2.0-1471.92 -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: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 09. September 2015 21:13 UTC kernel-stable-master-bug:1493780 kernel-stable-Certification-testing-end:Monday, 14. September 2015 13:00 UTC kernel-stable-Prepare-package-end:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-start:Monday, 14. September 2015 15:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 15. September 2015 20:23 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 15. September 2015 22:01 UTC kernel-stable-Security-signoff-start:Tuesday, 15. September 2015 22:01 UTC kernel-stable-Regression-testing-start:Tuesday, 15. September 2015 22:01 UTC proposed-announcement-sent:True kernel-stable-Verification-testing-start:Tuesday, 15. September 2015 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1494006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495795] 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/1495795 Title: package linux-image-3.19.0-28-generic 3.19.0-28.30 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko' to '/lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko .dpkg-new': unexpected end of file or stream Status in linux package in Ubuntu: Confirmed Bug description: just trying to update ubuntu mate ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 1276 F pulseaudio /dev/snd/controlC0: james 1276 F pulseaudio Date: Mon Sep 14 12:39:00 2015 DuplicateSignature: package:linux-image-3.19.0-28-generic:3.19.0-28.30:cannot copy extracted data for './lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko' to '/lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko' to '/lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko.dpkg-new': unexpected end of file or stream HibernationDevice: RESUME=UUID=200230d6-1497-4945-9e5a-bce333fd0362 InstallationDate: Installed on 2015-09-14 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=aeb60d7d-97ea-48e8-9dca-5f024edccd81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-3.19.0-28-generic 3.19.0-28.30 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko' to '/lib/modules/3.19.0-28-generic/kernel/drivers/infiniband/core/ib_cm.ko.dpkg-new': unexpected end of file or stream UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M800CE-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/08/2006:svn:pn:pvr:rvn:rnP4M800CE-8237:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488170] [NEW] Bluetooth initiated after quitting airplane mode
You have been subscribed to a public bug: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- Bluetooth initiated after quitting airplane mode https://bugs.launchpad.net/bugs/1488170 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1495782] Re: [Dell Latitude 3150] Suspend / Hibernate will turn Wifi / BT off / on with 14.04.2
** Summary changed: - [Dell Latitude 3150] Hibernate will turn Wifi / BT off on 14.04.2 + [Dell Latitude 3150] Suspend / Hibernate will turn Wifi / BT off / on with 14.04.2 ** Tags removed: certification-grey ** Description changed: CID: 201412-16319 Dell Latitude 3150 - Running hibernate will turn the Wireless network and Bluetooth off, - however it can be re-enabled with the wireless hotkey. + Running hibernate or suspend will turn the Wireless network and + Bluetooth off on the first time, and turn it on on the second time, + however it can alway be re-enabled with the wireless hotkey. Steps: 1. Install 14.04.2 + update 2. Run hibernate with "sudo pm-hibernate" 3. Wake it up. + 4. Hibernate it again. + 5. Wake it up Expected result: - * Wireless and Bluetooth still working. + * Wireless and Bluetooth should be working all the time. Actual result: - * They got disabled. + * They got disabled on the first, third, fifth... cycle + + You can replace hiberate here in the steps with suspend, and will get + the same result. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 00:17:34 2015 InstallationDate: Installed on 2015-09-11 (4 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) - --- + --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1574 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1574 F pulseaudio CRDA: - country TW: - (2402 - 2472 @ 40), (3, 27) - (5270 - 5330 @ 40), (3, 17), DFS - (5735 - 5815 @ 40), (3, 30) + country TW: + (2402 - 2472 @ 40), (3, 27) + (5270 - 5330 @ 40), (3, 17), DFS + (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c9ac4cb4-606e-492c-a4a0-c511bad7444f InstallationDate: Installed on 2015-09-11 (4 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:6709 Microdia - Bus 001 Device 036: ID 8087:0a2a Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:6709 Microdia + Bus 001 Device 036: ID 8087:0a2a Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=f071bd28-7686-4baa-a134-8392289e49d2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: - linux-restricted-modules-3.16.0-49-generic N/A - linux-backports-modules-3.16.0-49-generic N/A - linux-firmware 1.127.15 + linux-restricted-modules-3.16.0-49-generic N/A + linux-backports-modules-3.16.0-49-generic N/A + linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 021010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/31/2015:svnDellInc.:pnLatitude3150:pvr:rvnDellInc.:rn021010:rvrD02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3150 dmi.sys.vendor: Dell Inc. ** Changed in: linux (Ubuntu) Importance: Low => Undecided ** Package changed: linux (Ubuntu) => linux-lts-utopic (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/1495782 Title: [Dell Latitude 3150] Suspend / Hibernate will turn Wifi / BT off / on with 14.04.2 Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: CID: 201412-16319 Dell Latitude 3150 Running hibernate or suspend will turn the Wireless network and Bluetooth off on the first time, and turn it on on the second time, however it can alway be re-enabled with the wireless hotkey. Steps: 1. Install 14.04.2 + update 2. Run hibernate with "sudo pm-hibernate" 3. Wake it up. 4. Hibernate it again. 5.
[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
** Project changed: ubuntu-system-image => bluez (Ubuntu) ** Also affects: urfkill (Ubuntu) Importance: Undecided Status: New ** Tags added: after-bluez5 bluetooth -- 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/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
*** This bug is a duplicate of bug 1492632 *** https://bugs.launchpad.net/bugs/1492632 ** This bug has been marked a duplicate of bug 1492632 [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492764 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Status in linux package in Ubuntu: Confirmed Bug description: System: Kubuntu 15.10 Since kernel version 4.2 I have a few of this errors: Sep 06 16:16:35 benediktZ50-70 kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Sep 06 16:16:35 benediktZ50-70 kernel: [ cut here ] Sep 06 16:16:35 benediktZ50-70 kernel: WARNING: CPU: 0 PID: 187 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() Sep 06 16:16:35 benediktZ50-70 kernel: pipe state doesn't match! Sep 06 16:16:35 benediktZ50-70 kernel: Modules linked in: rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci r8169 mii sdhci_acpi video sdhci i2c_hid hid Sep 06 16:16:35 benediktZ50-70 kernel: CPU: 0 PID: 187 Comm: plymouthd Tainted: GW 4.2.0-7-generic #7-Ubuntu Sep 06 16:16:35 benediktZ50-70 kernel: Hardware name: LENOVO 20354/Lancer 5A5, BIOS 9BCN91WW 07/21/2015 Sep 06 16:16:35 benediktZ50-70 kernel: c023f1e8 8802413277e8 817b0465 Sep 06 16:16:35 benediktZ50-70 kernel: 880241327838 880241327828 81076536 880241327858 Sep 06 16:16:35 benediktZ50-70 kernel: 8802413278c0 880241152000 0001 880241152350 Sep 06 16:16:35 benediktZ50-70 kernel: Call Trace: Sep 06 16:16:35 benediktZ50-70 kernel: [] dump_stack+0x45/0x57 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_common+0x86/0xc0 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_fmt+0x46/0x50 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] check_crtc_state+0x2c5/0x440 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_modeset_check_state+0x20e/0x6b0 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_crtc_set_config+0x4c7/0x580 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_create+0x25/0x60 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_set_config_internal+0x66/0x100 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_ioctl+0x125/0x610 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] do_vfs_ioctl+0x285/0x470 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? do_munmap+0x349/0x480 Sep 06 16:16:35 benediktZ50-70 kernel: [] SyS_ioctl+0x79/0x90 Sep 06 16:16:35 benediktZ50-70 kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Sep 06 16:16:35 benediktZ50-70 kernel: ---[ end trace 724377a3c01e4270 ]--- I will check next week if these errors have any impact on my system. This is a Nvidia Optimus System with the Intel graphic card activated by default. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benedikt 1550 F pulseaudio /dev/snd/controlC1: benedikt 1550 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 6 16:22:48 2015 HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf InstallationDate: Installed on 2014-12-21 (259 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141218) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias:
[Kernel-packages] [Bug 1491761] Re: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04
compaq presario cq71 CQ71-350SB VL002EA#UUG With the r8101 module the card works but i have the feeling that it doesn't work 100 % sometimes it is very slow. Other times it works normal but still slower than on my other laptop who is even older. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491761 Title: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) not working in 14.04 and 15.04 Status in linux package in Ubuntu: Incomplete Bug description: (eth0): carrier is OFF Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 2 20:00:32 cq71 NetworkManager[579]: [1441216832.927980] [platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 2: mtu 0 (1) driver 'r8169' udi '/sys/devices/pci:00/:00:1c.1/:03:00.0/net/eth0': Invalid address for specified address family Sep 2 20:00:32 cq71 NetworkManager[579]: (eth0): preparing device r8169 :03:00.0 eth0: RTL8102e at 0xc90004778000, 00:00:00:00:00:00, XID 04c0 IRQ 27 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Subsystem: Hewlett-Packard Company Device 306c Kernel driver in use: r8169 *-network DISABLED description: Ethernet interface product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 02 size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full latency=0 link=no multicast=yes port=MII speed=100Mbit/s resources: irq:27 ioport:2000(size=256) memory:d401-d4010fff memory:d400-d400 memory:d500-d500 i compiled the r8101 module from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false after i put in a "cloned mac adress" the card is functional. there is also an old bug report of this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256331 --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 1084 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6f27858b-0ba5-46f9-b656-36f652d32cb0 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=c8c26d44-1f21-4878-8430-8e0fe79ffcc4 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev' Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 306C dmi.board.vendor: Quanta dmi.board.version: 21.12 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.14:bd09/22/2009:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn306C:rvr21.12:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1061508] Re: System Boots Every Other Time
Trying from work today on via google chrome on a windows box, can't seem to log a ticket through launch pad, even though I have a valid login. I'm guessing I need log a ticket through my Ubuntu machine via terminal commands only? I've never logged a new bug before - new to this. - Tobi On Sun, Sep 13, 2015 at 9:51 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > tjboadwa, it will help immensely if you filed a new report via a terminal: > ubuntu-bug linux > > Please feel free to subscribe me to it. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1061508 > > Title: > System Boots Every Other Time > > Status in linux package in Ubuntu: > Expired > > Bug description: > After a fresh install of 12.04.1 the system boots every other time > it's started or restarted. When it doesn't boot the screen goes to > sleep as the system hangs/freezes. The system boots fine under > 10.04.4. > > Steps to reproduce: > 1) Install using 12.04.1 > 2) Boot the system > 3) If the system boots properly restart or shutdown the system > > ProblemType: Bug > DistroRelease: Ubuntu 12.04 > Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50 > ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 > Uname: Linux 3.2.0-31-generic-pae i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. > ApportVersion: 2.0.1-0ubuntu13 > Architecture: i386 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: name 2478 F pulseaudio >/dev/snd/pcmC0D0p: name 2478 F...m pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23' > Mixer name : 'Realtek ALC888' > Components : 'HDA:10ec0888,103c2a58,0011' > Controls : 40 > Simple ctrls : 21 > Date: Thu Oct 4 06:05:55 2012 > HibernationDevice: RESUME=UUID=9d64ac90-738f-49eb-a637-ad5473e780b4 > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 > (20120423.2) > IwConfig: Error: [Errno 2] No such file or directory > MachineType: HP-Pavilion GC384AV-ABA m8000e > ProcEnviron: >LANGUAGE=en_US:en >TERM=xterm >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: >0 nouveaufb >1 nouveaufb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic-pae > root=/dev/mapper/sda6_crypt ro quiet splash > RelatedPackageVersions: >linux-restricted-modules-3.2.0-31-generic-pae N/A >linux-backports-modules-3.2.0-31-generic-pae N/A >linux-firmware1.79.1 > RfKill: Error: [Errno 2] No such file or directory > SourcePackage: linux > UdevDb: Error: [Errno 2] No such file or directory > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/15/2007 > dmi.bios.vendor: Phoenix Technologies, LTD > dmi.bios.version: 5.09 > dmi.board.name: NARRA > dmi.board.vendor: ASUSTek Computer INC. > dmi.board.version: 1.01 > dmi.chassis.type: 3 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd05/15/2007:svnHP-Pavilion:pnGC384AV-ABAm8000e:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: > dmi.product.name: GC384AV-ABA m8000e > dmi.sys.vendor: HP-Pavilion > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1061508/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1061508 Title: System Boots Every Other Time Status in linux package in Ubuntu: Expired Bug description: After a fresh install of 12.04.1 the system boots every other time it's started or restarted. When it doesn't boot the screen goes to sleep as the system hangs/freezes. The system boots fine under 10.04.4. Steps to reproduce: 1) Install using 12.04.1 2) Boot the system 3) If the system boots properly restart or shutdown the system ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: name 2478 F pulseaudio /dev/snd/pcmC0D0p: name 2478 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a58,0011'
[Kernel-packages] [Bug 1496073] [NEW] Request cherry-pick of upstream kernel patch which caps SECCOMP_RET_ERRNO to MAX_ERRNO
Public bug reported: The seccomp regression tests are failing due to SRU kernels not having the relevant commit: Author: Kees CookDate: Tue Feb 17 13:48:00 2015 -0800 seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO when setting errno during a SECCOMP_RET_ERRNO filter action. This makes sure we have a reliable value being set, so that an invalid errno will not be ignored by userspace. Signed-off-by: Kees Cook Reported-by: Dmitry V. Levin Cc: Andy Lutomirski Cc: Will Drewry Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds SRU Justification Impact: Upstream regression tests are reporting errors. Test Case: Run the upstream regression tests and verify they are passing cleanly. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Brad Figg (brad-figg) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Brad Figg (brad-figg) ** Description changed: The seccomp regression tests are failing due to SRU kernels not having the relevant commit: Author: Kees Cook Date: Tue Feb 17 13:48:00 2015 -0800 - seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO - - The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO - when setting errno during a SECCOMP_RET_ERRNO filter action. This makes - sure we have a reliable value being set, so that an invalid errno will not - be ignored by userspace. - - Signed-off-by: Kees Cook - Reported-by: Dmitry V. Levin - Cc: Andy Lutomirski - Cc: Will Drewry - Signed-off-by: Andrew Morton - Signed-off-by: Linus Torvalds + seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO + + The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO + when setting errno during a SECCOMP_RET_ERRNO filter action. This makes + sure we have a reliable value being set, so that an invalid errno will not + be ignored by userspace. + + Signed-off-by: Kees Cook + Reported-by: Dmitry V. Levin + Cc: Andy Lutomirski + Cc: Will Drewry + Signed-off-by: Andrew Morton + Signed-off-by: Linus Torvalds + + SRU Justification + + Impact: + Upstream regression tests are reporting errors. + + Test Case: + Run the upstream regression tests and verify they are passing + cleanly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1496073 Title: Request cherry-pick of upstream kernel patch which caps SECCOMP_RET_ERRNO to MAX_ERRNO Status in linux package in Ubuntu: In Progress Bug description: The seccomp regression tests are failing due to SRU kernels not having the relevant commit: Author: Kees Cook Date: Tue Feb 17 13:48:00 2015 -0800 seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO when setting errno during a SECCOMP_RET_ERRNO filter action. This makes sure we have a reliable value being set, so that an invalid errno will not be ignored by userspace. Signed-off-by: Kees Cook Reported-by: Dmitry V. Levin Cc: Andy Lutomirski Cc: Will Drewry Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds SRU Justification Impact: Upstream regression tests are reporting errors. Test Case: Run the upstream regression tests and verify they are passing cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496091] [NEW] Wifi is very unstable
Public bug reported: My wifi keeps getting disconnected every now and then (every 30seconds to 1hour). When using the 3.13 kernel, when it tries to reconnect, my computer freezes and wont even let me switch to one of the TTY terminals. With 3.16, 4.0, & 4.2 my computer rarely freezes, but when it does, it only lasts for a minute. With the 3.19 kernel I can't even use my wifi. My OS is Linux Mint 17.2 Cinnamon 64-bit; I originally had been 17.1 installed before I upgraded. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1496091 Title: Wifi is very unstable Status in linux package in Ubuntu: Incomplete Bug description: My wifi keeps getting disconnected every now and then (every 30seconds to 1hour). When using the 3.13 kernel, when it tries to reconnect, my computer freezes and wont even let me switch to one of the TTY terminals. With 3.16, 4.0, & 4.2 my computer rarely freezes, but when it does, it only lasts for a minute. With the 3.19 kernel I can't even use my wifi. My OS is Linux Mint 17.2 Cinnamon 64-bit; I originally had been 17.1 installed before I upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492850] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1492850/+attachment/4465398/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492850 Title: Dell pro venue 11 - No wireless connections after sleep Status in linux package in Ubuntu: Incomplete Bug description: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes After suspend (no more wifi chipset !). @utopie:~$ sudo lshw -C network *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-23 (136 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.2.0-040200rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-23 (144 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.2.0-040200-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495759] Re: package linux-image-3.19.0-29-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495759 Title: package linux-image-3.19.0-29-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: The Bug might have been in a NY Dime Bank ad I was reading, but not sure, all I know is the server froze up three times and each time I had to do a force shut down, and restart the server. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-29-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joeinslw 1726 F pulseaudio Date: Mon Sep 14 16:01:03 2015 DuplicateSignature: package:linux-image-3.19.0-29-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=59d4d870-6596-4daa-bdec-d2d0c6e4d2f0 InstallationDate: Installed on 2015-08-14 (31 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO ThinkServer TS440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-27-generic root=UUID=1db83ae2-a976-41b2-969e-03c7db20824b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1 RfKill: SourcePackage: linux Title: package linux-image-3.19.0-29-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS440 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: ThinkServer TS440 dmi.product.version: 70AQ0009UX dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492850] Re: Dell pro venue 11 - No wireless connections after sleep
apport information ** Description changed: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes After suspend (no more wifi chipset !). @utopie:~$ sudo lshw -C network *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-23 (136 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.2.0-040200rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ApportVersion: 2.17.2-0ubuntu1.4 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.04 + InstallationDate: Installed on 2015-04-23 (144 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + Package: linux (not installed) + Tags: vivid + Uname: Linux 4.2.0-040200-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1492850/+attachment/4465397/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492850 Title: Dell pro venue 11 - No wireless connections after sleep Status in linux package in Ubuntu: Incomplete Bug description: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série:
[Kernel-packages] [Bug 1495208] cavac (amd64) - tests ran: 154, failed: 71
tests ran: 154, failed: 71; http://kernel.ubuntu.com/testing/4.2.0-10.11/cavac__4.2.0-10.11__2015-09-15_14-25-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/1495208 Title: linux: 4.2.0-10.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: This bug is for tracking the 4.2.0-10.11 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:Sunday, 13. September 2015 10:29 UTC kernel-phase-changed:Sunday, 13. September 2015 10:29 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Sunday, 13. September 2015 17:27 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1495208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496091] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1496091 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/1496091 Title: Wifi is very unstable Status in linux package in Ubuntu: Incomplete Bug description: My wifi keeps getting disconnected every now and then (every 30seconds to 1hour). When using the 3.13 kernel, when it tries to reconnect, my computer freezes and wont even let me switch to one of the TTY terminals. With 3.16, 4.0, & 4.2 my computer rarely freezes, but when it does, it only lasts for a minute. With the 3.19 kernel I can't even use my wifi. My OS is Linux Mint 17.2 Cinnamon 64-bit; I originally had been 17.1 installed before I upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 703180] Re: 197b:2391 [Dell XPS 15 (L501X)] SD card reader inaccessible without pci bus rescan
This is broken again on wily. ** Tags added: wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/703180 Title: 197b:2391 [Dell XPS 15 (L501X)] SD card reader inaccessible without pci bus rescan Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: This is a Dell XPS L501X laptop (the new ones with USB3 etc: http://www.dell.com/us/p/xps-15/pd.aspx) The card reader neither shows up in lspci nor in lsusb (only device connected via USB seems to be the internal webcam which works), so I can't even figure out which model it is… ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-24-generic-pae 2.6.35-24.42 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 1777 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf090 irq 49' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0665,1028046e,0013 HDA:80862804,80860101,0010' Controls : 29 Simple ctrls : 13 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xadefc000 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Sat Jan 15 05:06:50 2011 Frequency: Once a day. HibernationDevice: RESUME=UUID=e7d13dad-6e7f-4320-8b4f-98e29cfde6f0 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS L501X ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic-pae root=UUID=b8eb30a4-6bd4-4d52-b356-8cb3431ba849 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: linux-firmware 1.38.3 SourcePackage: linux dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 00CKNG dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd11/26/2010:svnDellInc.:pnXPSL501X:pvrA04:rvnDellInc.:rn00CKNG:rvrA04:cvnDellInc.:ct8:cvrA04: dmi.product.name: XPS L501X dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/703180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495864] [NEW] DKMS regression: Build failure on armhf and ppc64el
Public bug reported: Here's the build log taken from http://autopkgtest.ubuntu.com/packages/x /xtables-addons/trusty/ppc64el/ dpkg: warning: version '*-*' has bad syntax: version number does not start with digit It is likely that 3.19.0-26-generic belongs to a chroot's host Building initial module for 3.19.0-29-generic Error! Build of xt_ACCOUNT.ko failed for: 3.19.0-29-generic (ppc64le) Consult the make.log in the build directory /var/lib/dkms/xtables-addons/2.3/build/ for more information. Processing triggers for libc-bin (2.19-0ubuntu6.6) ... I: Testing binary package xtables-addons-common I: Package xtables-addons-common has no dkms.conf, skipping I: Installing binary package xtables-addons-dkms Reading package lists... Building dependency tree... Reading state information... xtables-addons-dkms is already the newest version. xtables-addons-dkms set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Testing binary package xtables-addons-dkms I: Testing if xtables-addons modules are correctly installed xtables-addons, 2.3: added E: not installed adt-run [20:10:04]: test command1: ---] command1 FAIL non-zero exit status 1 adt-run [20:10:04]: test command1: - - - - - - - - - - results - - - - - - - - - - adt-run [20:10:05]: summary command1 FAIL non-zero exit status 1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Incomplete ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495864 Title: DKMS regression: Build failure on armhf and ppc64el Status in linux package in Ubuntu: Incomplete Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-vivid package in Ubuntu: New Status in linux source package in Trusty: Incomplete Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Bug description: Here's the build log taken from http://autopkgtest.ubuntu.com/packages/x/xtables- addons/trusty/ppc64el/ dpkg: warning: version '*-*' has bad syntax: version number does not start with digit It is likely that 3.19.0-26-generic belongs to a chroot's host Building initial module for 3.19.0-29-generic Error! Build of xt_ACCOUNT.ko failed for: 3.19.0-29-generic (ppc64le) Consult the make.log in the build directory /var/lib/dkms/xtables-addons/2.3/build/ for more information. Processing triggers for libc-bin (2.19-0ubuntu6.6) ... I: Testing binary package xtables-addons-common I: Package xtables-addons-common has no dkms.conf, skipping I: Installing binary package xtables-addons-dkms Reading package lists... Building dependency tree... Reading state information... xtables-addons-dkms is already the newest version. xtables-addons-dkms set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Testing binary package xtables-addons-dkms I: Testing if xtables-addons modules are correctly installed xtables-addons, 2.3: added E: not installed adt-run [20:10:04]: test command1: ---] command1 FAIL non-zero exit status 1 adt-run [20:10:04]: test command1: - - - - - - - - - - results - - - - - - - - - - adt-run [20:10:05]: summary command1 FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495639] Re: Bug: unable to handle kernel NULL pointer dereference at
@Joseph for a long time i've also got such kernel issues: in fact booting was failing each time the first time (was affected many kernels accross a year or so) with various crash messages. And finally i've found that these issues was due to ram voltage set too low by the default bios setting. I then searched for the ram model stick specs and what voltage should be affected to it. So i've unhide the ram voltage (bios AMI) by setting the cpu on "manual" but nothing changed on the cpu settings side (no tweaks), then the ram voltage have been set on "manual" too with the required 1.85v for the ram sticks. Since i've never had issue to boot: no kernel panic, no pointer trouble, If the bios have to be blamed on my system when booting ubuntu/linux, the same system was not having trouble to boot windows. So there is a problem on the linux kernel, wanting too much power. nb: i suppose there is tons of 'kernel panic, or else') reports due to the problem i've found. So it might be important to dig around that 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/1495639 Title: Bug: unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: In Progress Bug description: When i boot Ubuntu 12.04.5 from CD for installation, Ubuntu was loading for few second and after them this bug was presenting. Bug: unable to handle kernel NULL pointer dereference at 00054 ...and any information on my PC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495782] Re: [Dell Latitude 3150] Suspend / Hibernate will toggle Wifi / BT off / on with 14.04.2
** Summary changed: - [Dell Latitude 3150] Suspend / Hibernate will turn Wifi / BT off / on with 14.04.2 + [Dell Latitude 3150] Suspend / Hibernate will toggle Wifi / BT off / on with 14.04.2 -- 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/1495782 Title: [Dell Latitude 3150] Suspend / Hibernate will toggle Wifi / BT off / on with 14.04.2 Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: CID: 201412-16319 Dell Latitude 3150 Running hibernate or suspend will turn the Wireless network and Bluetooth off on the first time, and turn it on on the second time, however it can alway be re-enabled with the wireless hotkey. Steps: 1. Install 14.04.2 + update 2. Run hibernate with "sudo pm-hibernate" 3. Wake it up. 4. Hibernate it again. 5. Wake it up Expected result: * Wireless and Bluetooth should be working all the time. Actual result: * They got disabled on the first, third, fifth... cycle You can replace hiberate here in the steps with suspend, and will get the same result. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 00:17:34 2015 InstallationDate: Installed on 2015-09-11 (4 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) --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1574 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c9ac4cb4-606e-492c-a4a0-c511bad7444f InstallationDate: Installed on 2015-09-11 (4 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6709 Microdia Bus 001 Device 036: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=f071bd28-7686-4baa-a134-8392289e49d2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: linux-restricted-modules-3.16.0-49-generic N/A linux-backports-modules-3.16.0-49-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 021010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/31/2015:svnDellInc.:pnLatitude3150:pvr:rvnDellInc.:rn021010:rvrD02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3150 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1495782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453812] Re: System freeze when using LibreOffice Writer
Bug #1481129, which I marked as a duplicate of this bug, contains some more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453812 Title: System freeze when using LibreOffice Writer Status in linux package in Ubuntu: Incomplete Bug description: LibreOffice Writer is freezing the system after a few minutes (Ubuntu 15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is moving the mouse pointer on the screen. Impossible to connect to a tty session to kill Xorg. A physical reboot is necessary. Note that I used LibreOffice Calc without problem. The problem has been encountered also under Fedora 21: http://forums.fedora-fr.org/viewtopic.php?id=63428 WORKAROUND: Use nvidia-304-updates or 340.76. --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:063a] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Z400 Workstation Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.07 dmi.board.asset.tag: CZC0195Y06 dmi.board.name: 0B4Ch dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: CZC0195Y06 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed May 20 08:19:58 2015 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481129] Re: System freeze when using Libre Office
*** This bug is a duplicate of bug 1453812 *** https://bugs.launchpad.net/bugs/1453812 ** This bug has been marked a duplicate of bug 1453812 System freeze when using LibreOffice Writer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481129 Title: System freeze when using Libre Office Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: When using Libre office Draw, the system entirely froze. I was just able to move the mouse, not even able to do a tty session. I am using Nouveau Driver, with a kernel 3.19.0-25-generic. I'm quite new reporting bugs, so please let me know if you need any additional information, I'll add them =) Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 3 22:21:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7220] InstallationDate: Installed on 2015-07-18 (16 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: Micro-Star International GX627 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=9e366518-5490-46f2-a96a-b0a230e475dd ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1651IMS.10P dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-1651 dmi.board.vendor: MSI dmi.board.version: Ver 1.000 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.:bvrA1651IMS.10P:bd12/26/2008:svnMicro-StarInternational:pnGX627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GX627 dmi.product.version: Ver 1.000 dmi.sys.vendor: Micro-Star International version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Aug 3 22:11:32 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495864] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1495864 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 ** Changed in: linux (Ubuntu Trusty) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1495864 Title: DKMS regression: Build failure on armhf and ppc64el Status in linux package in Ubuntu: Incomplete Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-vivid package in Ubuntu: New Status in linux source package in Trusty: Incomplete Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Bug description: Here's the build log taken from http://autopkgtest.ubuntu.com/packages/x/xtables- addons/trusty/ppc64el/ dpkg: warning: version '*-*' has bad syntax: version number does not start with digit It is likely that 3.19.0-26-generic belongs to a chroot's host Building initial module for 3.19.0-29-generic Error! Build of xt_ACCOUNT.ko failed for: 3.19.0-29-generic (ppc64le) Consult the make.log in the build directory /var/lib/dkms/xtables-addons/2.3/build/ for more information. Processing triggers for libc-bin (2.19-0ubuntu6.6) ... I: Testing binary package xtables-addons-common I: Package xtables-addons-common has no dkms.conf, skipping I: Installing binary package xtables-addons-dkms Reading package lists... Building dependency tree... Reading state information... xtables-addons-dkms is already the newest version. xtables-addons-dkms set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Testing binary package xtables-addons-dkms I: Testing if xtables-addons modules are correctly installed xtables-addons, 2.3: added E: not installed adt-run [20:10:04]: test command1: ---] command1 FAIL non-zero exit status 1 adt-run [20:10:04]: test command1: - - - - - - - - - - results - - - - - - - - - - adt-run [20:10:05]: summary command1 FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp