[Kernel-packages] [Bug 1401425] Re: Uninstalling unused kernel requires a reboot
Addition: I suspect this may be related to Nvidia driver packages and DKMS. When I removed the packages, the offer to reboot appeared again. I can understand why that happened - even though I don't have a Nvidia card on this machine, the module is built for all kernels, including the active one, and removing it requires reconfiguring the active kernel. However, this should not happen when unused kernel is removed. I attached apt logs of the Nvidia packages removal. ** Attachment added: /var/log/apt/history.log and term.log of Nvidia drivers removal https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401425/+attachment/4283313/+files/apt.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401425 Title: Uninstalling unused kernel requires a reboot Status in linux package in Ubuntu: Confirmed Bug description: When Linux kernel is updated, a package with the new kernel version is installed, and the system offers to reboot the machine (an icon appears in the system tray). After reboot the new kernel is loaded, but the old one is still installed. When I remove the old kernel packages (e.g. linux-image-3.16.0-25-generic, linux-image- extra-3.16.0-25-generic, linux-headers-3.16.0-25, linux- headers-3.16.0-25-generic) the system offers to reboot again, even though that kernel is not used. In essence this means that kernel upgrade requires two reboots. Removing unused kernel packages should not require a reboot, and some time ago it actually worked that way. I can't remember exactly which kernel release broke that (probably, 3.16.0-24 or so). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic (not installed) ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2670 F pulseaudio /dev/snd/controlC2: lastique 2670 F pulseaudio /dev/snd/controlC0: lastique 2670 F pulseaudio /dev/snd/controlC1: lastique 2670 F pulseaudio CurrentDesktop: KDE Date: Thu Dec 11 10:58:29 2014 HibernationDevice: RESUME=UUID=91d1b3ae-bbf2-489a-93b8-87323a08a6e8 InstallationDate: Installed on 2013-11-01 (404 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=d61403bb-991b-45fe-8052-ffc7a7e0db80 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-26-generic N/A linux-backports-modules-3.16.0-26-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-01 (39 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
yes, the solution was to issue some sort of apt-add-repository ppa:costamagnagianfranco/locutusofborg-ppa. Anyway, I hope somebody will sponsor the patch into ubuntu archives soon. thanks for testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in Virtualbox: New Status in linux package in Ubuntu: Triaged Status in virtualbox package in Ubuntu: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
Upload is sitting in the queue now: https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text= ** Changed in: virtualbox (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in Virtualbox: New Status in linux package in Ubuntu: Triaged Status in virtualbox package in Ubuntu: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251065]
(In reply to Peter Rimshnick from comment #33) Comment on attachment 93360 [details] tarball of dmesg output and Xorg.0.log Did you set drm.debug=6 in the kernel command line? The dmesg output is missing debugging 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/1251065 Title: HP Mini 1000 fails to resume from suspend Status in The Linux Kernel: Confirmed Status in linux package in Ubuntu: In Progress Bug description: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1251065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
@Christopher I updated the bios to version 1101: the bug is still there. You can remove the tag. Now I will try the upstream kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403653] Re: Kworker takes 100% CPU when booting with efi
The newest upstream kernel has the same bug. The symptoms in that upstream bug are identical (I also got this after an update to Yosemite) so this is almost certainly the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403653 Title: Kworker takes 100% CPU when booting with efi Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: When running on a Macbook Pro Retina that has been booted with EFI, a kworker process constantly takes 100% CPU. If you boot in legacy mode this does not happen. When grepping for large values in /sys/firmware/acpi/interrupts, this one stands out: /sys/firmware/acpi/interrupts/gpe66: 2510732 enabled Trying to disable it with echo disable /sys/firmware/acpi/interrupts/gpe66 makes the CPU load go away. This will also prevent installation of Ubuntu, because if you try to install when kworker is running causes ubiquity to hang while trying to format the disk. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpakkane 2346 F pulseaudio /dev/snd/controlC0: jpakkane 2346 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 17 23:36:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-17 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=7196f220-ff77-4982-bfc1-03506a8013f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B11.1408291433 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B11.1408291433:bd08/29/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1401817] Re: memory leak with unknown reason after upgrade to utopic
the bug also occurs with the upstream kernel ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401817 Title: memory leak with unknown reason after upgrade to utopic Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure if this is the right component/package. We are not able to identify a package/program which could be responsible for this bug, so we assume it is the kernel or at least a kernel configuration. Since the upgrade from trusty to utopic at October 27., our three servers for package building are massively swapping. This leads to by a factor of four slower build times. There were no configuration changes at all. Munin graphs of one of the affected servers are attached. The system has 48GB memory, and we have configured several ramdisks: root@cx1000-02:~# mount | grep -E tmpfs|ramfs none on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755,size=1024) udev on /dev type devtmpfs (rw,mode=0755) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,nodev,noexec,nosuid,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,nodev,noexec,nosuid,size=104857600,mode=0755) tmpfs on /var/tmp/obs type tmpfs (rw,size=36G) tmpfs on /run/obs type tmpfs (rw,relatime,size=1G) ramfs on /var/obscache type ramfs (rw) tmpfs on /run/obs type tmpfs (rw,relatime,size=1048576k) The build service uses several chroot environments to build packages for several distributions (http://openbuildservice.org/). You don't see any process which allocates so much memory with 'top'. Even after stopping the build service and unmounting /var/tmp/obs you are not able to deactivate the swap via swapoff -a: root@cx1000-02:~# swapoff -a swapoff: /dev/sda5: swapoff failed: Cannot allocate memory We also tested the latest kernel (3.16.0-28) and an old trusty kernel (3.13.0-40) without success. Also patching perl to exclude the perl bug https://rt.perl.org/Public/Bug/Display.html?id=123198 as root cause doesn't help. We don't have any idea what's the cause for this problem... We can deploy debug packages or anything else on the system, so please hesitate to ask for any information or help. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-26-generic 3.16.0-26.35 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Fri Dec 12 09:54:36 2014 HibernationDevice: RESUME=UUID=531cb8f2-e194-45a7-a13c-3167aacf89bf InstallationDate: Installed on 2011-09-20 (1178 days ago) InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: FUJITSU PRIMERGY CX122 S1 PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=6e5b9bee-ccdf-4e6f-b09d-759312aeb3e0 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-26-generic N/A linux-backports-modules-3.16.0-26-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-27 (45 days ago) dmi.bios.date: 05/24/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 Rev. 1.10.2899.A1 dmi.board.asset.tag: - dmi.board.name: D2899 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2899-A11 WGS02 GS01 dmi.chassis.asset.tag: YLAM001377 dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: CX122S1R dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00Rev.1.10.2899.A1:bd05/24/2011:svnFUJITSU:pnPRIMERGYCX122S1:pvrGS01:rvnFUJITSU:rnD2899:rvrS26361-D2899-A11WGS02GS01:cvnFUJITSU:ct23:cvrCX122S1R: dmi.product.name: PRIMERGY CX122 S1 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403653] Re: Kworker takes 100% CPU after installing OSX Yosemite upgrade
** Summary changed: - Kworker takes 100% CPU when booting with efi + Kworker takes 100% CPU after installing OSX Yosemite upgrade ** Description changed: - When running on a Macbook Pro Retina that has been booted with EFI, a - kworker process constantly takes 100% CPU. If you boot in legacy mode - this does not happen. + When running on a Macbook Pro Retina that has had its OSX install + upgraded to Yosemite, a kworker process constantly takes 100% CPU. When grepping for large values in /sys/firmware/acpi/interrupts, this one stands out: /sys/firmware/acpi/interrupts/gpe66: 2510732 enabled Trying to disable it with echo disable /sys/firmware/acpi/interrupts/gpe66 makes the CPU load go away. This will also prevent installation of Ubuntu, because if you try to install when kworker is running causes ubiquity to hang while trying to format the disk. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jpakkane 2346 F pulseaudio - /dev/snd/controlC0: jpakkane 2346 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jpakkane 2346 F pulseaudio + /dev/snd/controlC0: jpakkane 2346 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 17 23:36:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-17 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=7196f220-ff77-4982-bfc1-03506a8013f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.16.0-28-generic N/A - linux-backports-modules-3.16.0-28-generic N/A - linux-firmware 1.138 + linux-restricted-modules-3.16.0-28-generic N/A + linux-backports-modules-3.16.0-28-generic N/A + linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B11.1408291433 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B11.1408291433:bd08/29/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403653 Title: Kworker takes 100% CPU after installing OSX Yosemite upgrade Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: When running on a Macbook Pro Retina that has had its OSX install upgraded to Yosemite, a kworker process constantly takes 100% CPU. When grepping for large values in /sys/firmware/acpi/interrupts, this one stands out: /sys/firmware/acpi/interrupts/gpe66: 2510732 enabled Trying to disable it with echo disable /sys/firmware/acpi/interrupts/gpe66 makes the CPU load go away. This will also prevent installation of Ubuntu, because if you try to install when kworker is running causes ubiquity to hang while trying to format the disk. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpakkane 2346 F pulseaudio /dev/snd/controlC0: jpakkane 2346 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 17 23:36:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-17 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=7196f220-ff77-4982-bfc1-03506a8013f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
** Changed in: linux (Ubuntu) Status: Triaged = Invalid ** Project changed: virtualbox = null-and-void ** Changed in: null-and-void Status: New = 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/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in NULL Project: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1401624] Re: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip
Did this issue occur in a previous version of Ubuntu, or is this a new issue? I did not use this WiFi controller with a previous Ubuntu version. Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. The kernel warnings do not happen with this kernel version: ii linux-image-3.18.0-031800-generic 3.18.0-031800.201412071935 amd64Linux kernel image for version 3.18.0 on 64 bit x86 SMP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401624 Title: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip Status in linux package in Ubuntu: Fix Released Bug description: I have a laptop with this WiFi controller: 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at e2d0 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlwifi I switched WiFi off with the RF kill switch and got those errors: [19011.796623] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio. [19011.797807] [ cut here ] [19011.797848] WARNING: CPU: 1 PID: 6870 at /build/buildd/linux-3.16.0/net/wireless/core.c:949 cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]() [19011.797853] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core [19011.797964] ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core wmi video [19011.797980] CPU: 1 PID: 6870 Comm: kworker/1:1 Not tainted 3.16.0-28-generic #37-Ubuntu [19011.797983] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 11/14/2013 [19011.797999] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [19011.798003] 0009 8801b3c47c28 81781e6a [19011.798008] 8801b3c47c60 8106fedd 88022136a8d0 880035adc260 [19011.798013] 0002 88022136a000 880035adc000 8801b3c47c70 [19011.798018] Call Trace: [19011.798030] [81781e6a] dump_stack+0x45/0x56 [19011.798038] [8106fedd] warn_slowpath_common+0x7d/0xa0 [19011.798044] [8106ffba] warn_slowpath_null+0x1a/0x20 [19011.798060] [c052f629] cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211] [19011.798068] [8167acab] ? __dev_remove_pack+0x8b/0xb0 [19011.798075] [81761cbc] ? __unregister_prot_hook+0xcc/0xd0 [19011.798082] [8109972d] notifier_call_chain+0x4d/0x70 [19011.798087] [81099856] raw_notifier_call_chain+0x16/0x20 [19011.798093] [8167b4d5] call_netdevice_notifiers_info+0x35/0x60 [19011.798099] [8167b878] dev_close_many+0xc8/0x120 [19011.798105] [8167da46] dev_close.part.71+0x36/0x50 [19011.798110] [8167da81] dev_close+0x21/0x30 [19011.798125] [c052e8e5] cfg80211_shutdown_all_interfaces+0x45/0xc0 [cfg80211] [19011.798140] [c052e98b] cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211] [19011.798146] [8108da32] process_one_work+0x182/0x4e0 [19011.798151] [8108ddfb] worker_thread+0x6b/0x6a0 [19011.798156] [8108dd90] ? process_one_work+0x4e0/0x4e0 [19011.798162] [81094c6b] kthread+0xdb/0x100 [19011.798168] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [19011.798175] [81789dfc] ret_from_fork+0x7c/0xb0 [19011.798181] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [19011.798184] ---[ end trace 9074ade8075c79de ]--- [19011.798187] [ cut here ] [19011.798210] WARNING: CPU: 1 PID: 6870 at /build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]() [19011.798213] wlan1: Failed check-sdata-in-driver check, flags: 0x0 [19011.798214] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal
[Kernel-packages] [Bug 1401624] Re: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip
With this kernel: ii linux-image-extra-3.16.0-29-generic 3.16.0-29.39 amd64Linux kernel extra modules for version 3.16.0 on 64 bit x86 SMP and this updated firmware: ii linux-firmware 1.138.1 all Firmware for Linux kernel drivers the kernel warnings do not happen either. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401624 Title: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip Status in linux package in Ubuntu: Fix Released Bug description: I have a laptop with this WiFi controller: 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at e2d0 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlwifi I switched WiFi off with the RF kill switch and got those errors: [19011.796623] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio. [19011.797807] [ cut here ] [19011.797848] WARNING: CPU: 1 PID: 6870 at /build/buildd/linux-3.16.0/net/wireless/core.c:949 cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]() [19011.797853] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core [19011.797964] ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core wmi video [19011.797980] CPU: 1 PID: 6870 Comm: kworker/1:1 Not tainted 3.16.0-28-generic #37-Ubuntu [19011.797983] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 11/14/2013 [19011.797999] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [19011.798003] 0009 8801b3c47c28 81781e6a [19011.798008] 8801b3c47c60 8106fedd 88022136a8d0 880035adc260 [19011.798013] 0002 88022136a000 880035adc000 8801b3c47c70 [19011.798018] Call Trace: [19011.798030] [81781e6a] dump_stack+0x45/0x56 [19011.798038] [8106fedd] warn_slowpath_common+0x7d/0xa0 [19011.798044] [8106ffba] warn_slowpath_null+0x1a/0x20 [19011.798060] [c052f629] cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211] [19011.798068] [8167acab] ? __dev_remove_pack+0x8b/0xb0 [19011.798075] [81761cbc] ? __unregister_prot_hook+0xcc/0xd0 [19011.798082] [8109972d] notifier_call_chain+0x4d/0x70 [19011.798087] [81099856] raw_notifier_call_chain+0x16/0x20 [19011.798093] [8167b4d5] call_netdevice_notifiers_info+0x35/0x60 [19011.798099] [8167b878] dev_close_many+0xc8/0x120 [19011.798105] [8167da46] dev_close.part.71+0x36/0x50 [19011.798110] [8167da81] dev_close+0x21/0x30 [19011.798125] [c052e8e5] cfg80211_shutdown_all_interfaces+0x45/0xc0 [cfg80211] [19011.798140] [c052e98b] cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211] [19011.798146] [8108da32] process_one_work+0x182/0x4e0 [19011.798151] [8108ddfb] worker_thread+0x6b/0x6a0 [19011.798156] [8108dd90] ? process_one_work+0x4e0/0x4e0 [19011.798162] [81094c6b] kthread+0xdb/0x100 [19011.798168] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [19011.798175] [81789dfc] ret_from_fork+0x7c/0xb0 [19011.798181] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [19011.798184] ---[ end trace 9074ade8075c79de ]--- [19011.798187] [ cut here ] [19011.798210] WARNING: CPU: 1 PID: 6870 at /build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]() [19011.798213] wlan1: Failed check-sdata-in-driver check, flags: 0x0 [19011.798214] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags removed: bios-outdated-1101 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
@Joseph I checked the bug against the latest upstream kernel (3.18.1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Fabio, could you please provide the results of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date As well, did this problem not occur in a release prior to Trusty? ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: bios-outdated-1101 kernel-bug-exists-upstream-3.18.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working
I have read the section mentioned above and it is question of commit bisecting the mainline kernel. Sorry but i have not found a chapter describing this process. Are mainline kernels and upstream kernels the same. If this is the case i can apply the descriptions in chapter Commit bisecting upstream kernel versions Thanks in advance for your answer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322068 Title: Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: On clevo W253EU laptop : After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are: Ubuntu 12.04.LTS it works Ubuntu 12.04.1 LTS it works Ubuntu 12.04.2 LTS it works Ubuntu 12.04.3 LTS it does not working Ubuntu 12.04.4 LTS it does not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibold 1910 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 09:31:55 2014 HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab InstallationDate: Installed on 2014-05-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working
Antoine Sibold, mainline means the same thing as upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322068 Title: Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: On clevo W253EU laptop : After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are: Ubuntu 12.04.LTS it works Ubuntu 12.04.1 LTS it works Ubuntu 12.04.2 LTS it works Ubuntu 12.04.3 LTS it does not working Ubuntu 12.04.4 LTS it does not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibold 1910 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 09:31:55 2014 HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab InstallationDate: Installed on 2014-05-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
@Christopher Here is the requested output: $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date [sudo] password for fabio: 1101 09/04/2012 As to the other question, I can't answer: I bought the dongle a few weeks ago. Sorry. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
** Summary changed: - linux-ti-omap4: version to be filled -proposed tracker + linux-ti-omap4: 3.2.0-1458.78 -proposed tracker ** Description changed: - This bug is for tracking the version to be filled upload package. This - bug will contain status and testing results related to that upload. + This bug is for tracking the 3.2.0-1458.78 upload package. This bug will + contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 -- 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/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392006] Re: CVE-2014-7825
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392006 Title: CVE-2014-7825 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic 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-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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-mvl-dove source package in
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Fabio, for regression testing purposes, could you please test a live environment of 12.04.0 (not 12.04.3 or some other variant) via http ://old-releases.ubuntu.com/releases/12.04.0/ and advise to the results? ** Tags removed: bios-outdated-1101 ** Tags added: latest-bios-1101 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392820] Re: CVE-2014-7841
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Utopic) 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/1392820 Title: CVE-2014-7841 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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:
[Kernel-packages] [Bug 1400314] Re: CVE-2014-8134
** Changed in: linux (Ubuntu Vivid) Status: Fix Released = New ** Description changed: paravirt_enabled has the following effects: - Disables the F00F bug workaround warning. There is no F00F bug workaround any more because Linux's standard IDT handling already works around the F00F bug, but the warning still exists. This is only cosmetic, and, in any event, there is no such thing as KVM on a CPU with the F00F bug. - Disables 32-bit APM BIOS detection. On a KVM paravirt system, there should be no APM BIOS anyway. - Disables tboot. I think that the tboot code should check the CPUID hypervisor bit directly if it matters. - paravirt_enabled disables espfix32. espfix32 should *not* be disabled under KVM paravirt. The last point is the purpose of this patch. It fixes a leak of the high 16 bits of the kernel stack address on 32-bit KVM paravirt guests. While I'm at it, this removes pv_info setup from kvmclock. That code seems to serve no purpose. + + Break-Fix: - local-2014-8134 -- 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/1400314 Title: CVE-2014-8134 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic 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-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in
[Kernel-packages] [Bug 1388975] Re: CVE-2014-8559
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Invalid ** Description changed: The d_walk function in fs/dcache.c in the Linux kernel through 3.17.2 does not properly maintain the semantics of rename_lock, which allows local users to cause a denial of service (deadlock and system hang) via a crafted application. + + Break-Fix: - ca5358ef75fc69fee5322a38a340f5739d997c10 + Break-Fix: - 946e51f2bf37f1656916eb75bd0742ba33983c28 -- 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: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: 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-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-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: New Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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
[Kernel-packages] [Bug 1395187] Re: CVE-2014-8884
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Utopic) 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/1395187 Title: CVE-2014-8884 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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:
[Kernel-packages] [Bug 1392823] Re: CVE-2014-7842
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Utopic) 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/1392823 Title: CVE-2014-7842 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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
[Kernel-packages] [Bug 1392826] Re: CVE-2014-7843
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux (Ubuntu Utopic) 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/1392826 Title: CVE-2014-7843 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: 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: Fix Committed Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic 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 Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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-mvl-dove
[Kernel-packages] [Bug 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 + kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403851] [NEW] CVE-2014-4323
*** This bug is a security vulnerability *** Public security bug reported: The mdp_lut_hw_update function in drivers/video/msm/mdp.c in the MDP display driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain start and length values within an ioctl call, which allows attackers to gain privileges via a crafted application. Break-Fix: - 014fa8def84c62893fa016e873c12de1da498603 ** Affects: linux (Ubuntu) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: High Status: Invalid ** 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: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: High Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: High Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: High 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: High Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: High Status: New ** Affects: linux (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: High 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: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: High Status: New ** Affects:
[Kernel-packages] [Bug 1403851] Re: CVE-2014-4323
CVE-2014-4323 ** 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 Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) 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 ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed
[Kernel-packages] [Bug 1403852] [NEW] CVE-2014-8133
*** This bug is a security vulnerability *** Public security bug reported: [espfix bypass using set_thread_area] Break-Fix: - 41bdc78544b8a93a9c6814b8bbbfef966272abbe ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** 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: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium 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: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium 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: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium
[Kernel-packages] [Bug 1403852] Re: CVE-2014-8133
CVE-2014-8133 ** 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 Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) 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 ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New =
[Kernel-packages] [Bug 1403855] Re: CVE-2014-9322
CVE-2014-9322 ** 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 Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) 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 ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New =
[Kernel-packages] [Bug 1403855] [NEW] CVE-2014-9322
*** This bug is a security vulnerability *** Public security bug reported: [x86: local privesc due to bad_iret and paranoid entry incompatibility] Break-Fix: - 6f442be2fb22be02cafa606f1769fa1e6f894441 Break-Fix: - b645af2d5905c4e32399005b867987919cbfc3ae ** Affects: linux (Ubuntu) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: High Status: Invalid ** 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: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: High Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: High Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: High Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: High Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: High 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: High Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: High Status: New ** Affects: linux (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: High 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: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: High
[Kernel-packages] [Bug 1403868] [NEW] Lockup during boot with latest 14.10 and 14.04 LTS
Public bug reported: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 utopic ** Attachment added: Stack trace.jpg https://bugs.launchpad.net/bugs/1403868/+attachment/4283464/+files/Stack%20trace.jpg ** Description changed: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install - last Friday which worked fine, until the system pulled in the current - updates and again refused to boot. + last Friday which worked fine, until the system pulled in the then + current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: masterbrain 1936 F lxpanel + USERPID ACCESS COMMAND + /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: - lono wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth0 no wireless extensions. Lsusb: - Bus 001 Device 002: ID 4146:ba63 USBest Technology - 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 + Bus 001 Device 002: ID 4146:ba63 USBest Technology + 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
[Kernel-packages] [Bug 1403154] Re: linux: 3.2.0-75.110 -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) = John Johansen (jjohansen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403154 Title: linux: 3.2.0-75.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-75.110 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 17:50 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 23:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 18:20 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 20:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402872] Re: linux: 3.13.0-44.73 -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) = John Johansen (jjohansen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402872 Title: linux: 3.13.0-44.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-44.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 23:54 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 16. December 2014 22:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Verification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Regression-testing-start:Tuesday, 16. December 2014 23:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402822] Re: linux: 3.16.0-29.39 -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) = John Johansen (jjohansen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402822 Title: linux: 3.16.0-29.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-29.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 20:29 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:03 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 20:06 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 22:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Christopher, I will but I need some time. Maybe later today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403868] 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/1403868 Title: Lockup during boot with latest 14.10 and 14.04 LTS Status in linux package in Ubuntu: New Bug description: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/1403868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
** Tags removed: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403868] Re: Lockup during boot with latest 14.10 and 14.04 LTS
** Changed in: linux (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403868 Title: Lockup during boot with latest 14.10 and 14.04 LTS Status in linux package in Ubuntu: New Bug description: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/1403868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402822] Re: linux: 3.16.0-29.39 -proposed tracker
Looks good ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402822 Title: linux: 3.16.0-29.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-29.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 20:29 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:03 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 20:06 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 22:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Fabio, I noticed you removed the kernel-bug-exists-upstream tag. Is this no longer reproducible in the latest mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402872] Re: linux: 3.13.0-44.73 -proposed tracker
Looks good ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402872 Title: linux: 3.13.0-44.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-44.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 23:54 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 16. December 2014 22:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Verification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Regression-testing-start:Tuesday, 16. December 2014 23:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403868] 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/1403868 Title: Lockup during boot with latest 14.10 and 14.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/1403868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403154] Re: linux: 3.2.0-75.110 -proposed tracker
Looks good ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403154 Title: linux: 3.2.0-75.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-75.110 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 17:50 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 23:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 18:20 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 20:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402872] Re: linux: 3.13.0-44.73 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-44.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 23:54 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 16. December 2014 22:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Verification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Regression-testing-start:Tuesday, 16. December 2014 23:01 UTC + kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402872 Title: linux: 3.13.0-44.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-44.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 23:54 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 16. December 2014 22:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Verification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Regression-testing-start:Tuesday, 16. December 2014 23:01 UTC kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- 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/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402822] Re: linux: 3.16.0-29.39 -proposed tracker
** Description changed: This bug is for tracking the 3.16.0-29.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 20:29 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:03 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 20:06 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 22:00 UTC + kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402822 Title: linux: 3.16.0-29.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-29.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 15. December 2014 20:29 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 07:03 UTC ppa-package-testing-start:Tuesday, 16. December 2014 07:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 20:06 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 22:00 UTC kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1402822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403154] Re: linux: 3.2.0-75.110 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-75.110 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 17:50 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 23:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 18:20 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 20:02 UTC + kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403154 Title: linux: 3.2.0-75.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-75.110 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 17:50 UTC kernel-stable-Prepare-package-end:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 16. December 2014 23:08 UTC ppa-package-testing-start:Tuesday, 16. December 2014 23:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 17. December 2014 18:20 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Verification-testing-start:Wednesday, 17. December 2014 20:01 UTC kernel-stable-Certification-testing-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Security-signoff-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Regression-testing-start:Wednesday, 17. December 2014 20:02 UTC kernel-stable-Security-signoff-end:Thursday, 18. December 2014 14:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338185] Re: networking fails in 32-bit 14.04 using HyperV on Win2012R2
I can confirm that this bug is fixed in Ubuntu 14.04 with the follwing kernel package: kernel linux-image-3.13.0-43-generic 3.13.0-43.72 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/1338185 Title: networking fails in 32-bit 14.04 using HyperV on Win2012R2 Status in linux package in Ubuntu: Triaged Bug description: I was running Ubuntu 13.10 32-bit as a VM on a Windows Server 2012 R2 machine with Hyper-V. In 32-bit 13.10, networking worked properly at all times, from the first installation to normal usage. I ran the upgrade to 32-bit Ubuntu 14.04 and discovered that networking is no longer working. To eliminate the possibility that there was a botched upgrade, I tried a fresh install in another VM. I performed a fresh install of 32-bit Ubuntu 14.04 in Hyper-V from ubuntu-14.04-desktop-i386.iso, and I noticed that the network was not connecting during the first part of the installation before any files are copied to the disk. After the installation completed, there was no eth0 device present. By comparison, I performed a fresh install of 64-bit Ubuntu 14.04 in Hyper-V from the ubuntu-14.04-desktop-amd64.iso, and networking worked properly at all times from the start of installation. To summarize, networking is failing in 32-bit Ubuntu 14.04 under Hyper-V in Windows Server 2012 R2. Networking is working properly in 32-bit Ubuntu 13.10 on the same machine. Networking is working properly in 64-bit Ubuntu 14.04 on the same machine. Any suggestions on getting 32-bit Ubuntu 14.04 to work in my Hyper-V VM ? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400314] Re: CVE-2014-8134
** Changed in: linux (Ubuntu Vivid) 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/1400314 Title: CVE-2014-8134 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-fsl-imx51 package in Ubuntu: Invalid 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-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic 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-fsl-imx51 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-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: 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-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: 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-fsl-imx51 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-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4
[Kernel-packages] [Bug 1403918] [NEW] Lucid update to 2.6.32.65 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 2.6.32.65 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches are in the 2.6.32.65 stable release: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lucid) 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/1403918 Title: Lucid update to 2.6.32.65 stable release Status in linux package in Ubuntu: New Status in linux source package in Lucid: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 2.6.32.65 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches are in the 2.6.32.65 stable release: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403868] Re: Lockup during boot with latest 14.10 and 14.04 LTS
Will the system boot if you select the prior kernel version, which would be the one used during the install? ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403868 Title: Lockup during boot with latest 14.10 and 14.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/1403868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Christopher, 1) I removed that tag beacuse you inserted a more detailed one, namely kernel-bug-exists-upstream-3.18.1, so my tag looked to me redundant (maybe I shouldn't have removed it: I am unfamiliar with launchpad) 2) As you asked me, I tested a live cd with ubuntu 12.04.0 (amd64) and even there I can not use the dongle: you can insert the more appropriate tag. 3) I don't know if it can be of any use, but I will say it anyway: I have another bluetooth usb dongle. With the other device I can connect without problem to the telephone. Both with 12.04.4 and with my usual 14.04. If it can be of any help, I can insert the output of lsusb -v for both devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403507] Re: Issue on resume
Hello Joseph I tried to install the upstream kernel but I have the error message Selecting previously unselected package linux-headers-3.18.0-999. (Reading database ... 489847 files and directories currently installed.) Preparing to unpack linux-headers-3.18.0-999_3.18.0-999.201412170840_all.deb ... Unpacking linux-headers-3.18.0-999 (3.18.0-999.201412170840) ... Selecting previously unselected package linux-headers-3.18.0-999-generic. Preparing to unpack linux-headers-3.18.0-999-generic_3.18.0-999.201412170840_amd64.deb ... Unpacking linux-headers-3.18.0-999-generic (3.18.0-999.201412170840) ... Selecting previously unselected package linux-image-3.18.0-999-generic. Preparing to unpack linux-image-3.18.0-999-generic_3.18.0-999.201412170840_amd64.deb ... Done. Unpacking linux-image-3.18.0-999-generic (3.18.0-999.201412170840) ... Setting up linux-headers-3.18.0-999 (3.18.0-999.201412170840) ... Setting up linux-headers-3.18.0-999-generic (3.18.0-999.201412170840) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic Error! Bad return status for module build on kernel: 3.18.0-999-generic (x86_64) Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information. Setting up linux-image-3.18.0-999-generic (3.18.0-999.201412170840) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic Error! Bad return status for module build on kernel: 3.18.0-999-generic (x86_64) Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic update-initramfs: Generating /boot/initrd.img-3.18.0-999-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-999-generic /boot/vmlinuz-3.18.0-999-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.18.0-999-generic Found initrd image: /boot/initrd.img-3.18.0-999-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found linux image: /boot/vmlinuz-3.11.0-19-generic Found initrd image: /boot/initrd.img-3.11.0-19-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Find the make.log DKMS make.log for i915-3.15-3.13-0.01 for kernel 3.18.0-999-generic (x86_64) Thu Dec 18 16:49:48 CET 2014 GNU Make 4.0 Built for x86_64-pc-linux-gnu Copyright (C) 1988-2013 Free Software Foundation, Inc. Licence GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Reading makefiles... Reading makefile 'Makefile'... make: Entering directory '/usr/src/linux-headers-3.18.0-999-generic' Reading makefile 'scripts/Kbuild.include' (search path) (no ~ expansion)... Reading makefile 'include/config/auto.conf' (search path) (don't care) (no ~ expansion)... Reading makefile 'arch/x86/Makefile' (search path) (no ~ expansion)... Reading makefile 'scripts/Makefile.extrawarn' (search path) (no ~ expansion)... Updating makefiles Considering target file 'scripts/Makefile.extrawarn'. Looking for an implicit rule for 'scripts/Makefile.extrawarn'. No implicit rule found for 'scripts/Makefile.extrawarn'. Finished prerequisites of target file 'scripts/Makefile.extrawarn'. No need to remake target 'scripts/Makefile.extrawarn'. Considering target file 'arch/x86/Makefile'. Looking for an implicit rule for 'arch/x86/Makefile'. No implicit rule found for 'arch/x86/Makefile'. Finished prerequisites of target file 'arch/x86/Makefile'. No need to remake target 'arch/x86/Makefile'. Considering target file 'include/config/auto.conf'. File 'include/config/auto.conf' does not exist. Finished prerequisites of target file 'include/config/auto.conf'. Must remake target 'include/config/auto.conf'. test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo 2; \ echo 2 ERROR: Kernel configuration is invalid.; \ echo 2 include/generated/autoconf.h or include/config/auto.conf are missing.;\ echo 2 Run 'make oldconfig make prepare' on kernel src to fix it.; \ echo 2 ; \ /bin/false) Putting child 0x1523e90 (include/config/auto.conf) PID
[Kernel-packages] [Bug 1353129] [NEW] [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
You have been subscribed to a public bug: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug bios-outdated-2.21 trusty vivid -- [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working https://bugs.launchpad.net/bugs/1353129 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 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) = Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/package-testing Status: In Progress = Confirmed ** Description changed: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC + kernel-stable-phase:PPA Testing + kernel-stable-phase-changed:Thursday, 18. December 2014 16:02 UTC + kernel-stable-Prepare-package-end:Thursday, 18. December 2014 16:02 UTC + kernel-stable-Promote-to-proposed-start:Thursday, 18. December 2014 16:02 UTC + ppa-package-testing-start:Thursday, 18. December 2014 16:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 18. December 2014 16:02 UTC kernel-stable-Prepare-package-end:Thursday, 18. December 2014 16:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 18. December 2014 16:02 UTC ppa-package-testing-start:Thursday, 18. December 2014 16:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403918] Re: Lucid update to 2.6.32.65 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from Linus' tree or in a minimally + backported form of that patch. The 2.6.32.65 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from Linus' tree or in a minimally -backported form of that patch. The 2.6.32.65 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD + The following patches are in the 2.6.32.65 stable release: -The following patches are in the 2.6.32.65 stable release: + x86, 64-bit: Move K8 B step iret fixup to fault entry asm + x86-64: Adjust frame type at paranoid_exit: + x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels + x86-32, espfix: Remove filter for espfix32 due to race + x86-64, espfix: Don't leak bits 31:16 of %esp returning to 16-bit stack + x86, espfix: Move espfix definitions into a separate header file + x86, espfix: Fix broken header guard + x86, espfix: Make espfix64 a Kconfig option, fix UML + x86, espfix: Make it possible to disable 16-bit support + x86_64/entry/xen: Do not invoke espfix64 on Xen + x86/espfix/xen: Fix allocation of pages for paravirt page tables + x86_64, traps: Stop using IST for #SS + x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C + x86_64, traps: Rework bad_iret + + The following patches from the stable release have been dropped (some + were actually already applied to Lucid): + + net: sendmsg: fix failed backport of fix NULL pointer dereference + net/l2tp: don't fall back on UDP [get|set]sockopt + ALSA: control: Don't access controls outside of protected regions + ALSA: control: Fix replacing user controls + USB: whiteheat: Added bounds checking for bulk command response + net: sctp: fix panic on duplicate ASCONF chunks + net: sctp: fix remote memory pressure from excessive queueing + udf: Avoid infinite loop when processing indirect ICBs + net: sctp: fix NULL pointer dereference in af-from_addr_param on malformed packet + mac80211: fix fragmentation code, particularly for encryption + ttusb-dec: buffer overflow in ioctl + vlan: Don't propagate flag changes on down interfaces. + sctp: Fix double-free introduced by bad backport in 2.6.32.62 + md/raid6: Fix misapplied backport in 2.6.32.64 + block: add missing blk_queue_dead() checks + block: Fix blk_execute_rq_nowait() dead queue handling + cciss: Fix misapplied cciss: fix info leak in cciss_ioctl32_passthru() + proc connector: Delete spurious memset in proc_exit_connector() + Linux 2.6.32.65 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403918 Title: Lucid update to 2.6.32.65 stable release Status in linux package in Ubuntu: New Status in linux source package in Lucid: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 2.6.32.65 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches are in the 2.6.32.65 stable release: x86, 64-bit: Move K8 B step iret fixup to fault entry asm x86-64: Adjust frame type at paranoid_exit: x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels x86-32, espfix: Remove filter for espfix32 due to race x86-64, espfix: Don't leak bits 31:16 of %esp returning to 16-bit stack x86, espfix: Move espfix definitions into a separate header file x86, espfix: Fix broken header guard x86, espfix: Make espfix64 a Kconfig option, fix UML x86, espfix: Make it possible to disable 16-bit support x86_64/entry/xen: Do not invoke espfix64 on Xen x86/espfix/xen: Fix allocation of pages for paravirt page tables x86_64, traps: Stop using IST for #SS x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C x86_64, traps: Rework bad_iret The following patches from the stable release have been
[Kernel-packages] [Bug 1353129] Re: Over and out
Christopher M. Penalver: As well, having the outdated BIOS upgraded would be a great step, as well as having the mainline kernel tested to this issue. In my own experience BIOS are usually very buggy and trigger many issues. I know of 3 bugs in my own computer BIOS. Rolf Leggewie: He and I would like to find the cause of this without your constant interference. Taking decisions slowly by consensus is what usually works the best. But sometimes those are so trivial or so uncertain that taking one without entering in too much discussion is a better choice, as the opposite would mean spending most of the time in topics that really doesn't matter at all. When that happens, because Ubuntu is a meritocratic community, the Canonical staff has always the last word. And everyone should accept that. Christopher M. Penalver: If you find something I've done alienating, I deeply and sincerely apologize for this. I will reflect on the intent of this e-mail, and how to better my triaging approach. My intentions are only to get to the technical root cause of a particular report, and follow the guidelines already set out by the respective teams whose packages I triage. Christopher, you have been too kind. Managing an irrational situation in a rational way is like asking someone to change religion: it won't work. As rule of thumbs, if someone treats you steadily disrespectful there's no single reason for continuing the business. Because there's no single excuse for mistreating other people. In those cases the most appropriate answer I have found is the following, which for me feels like letting go a big weight: Rolf Leggewie (http://tinyurl.com/p2eflk5): Yadda, yadda. Dude, you must be by FAR the single most-hated guy on LP. You must hear to get lost and leave people alone at least a good dozen times a day, don't you? Why don't you do that? You are NOT helping the project, even though you might think you do. http://tinyurl.com/7yaoc62 ** Package changed: unity (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = High ** 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/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot
** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) = khuanglim (khuang0411) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/996369 Title: bond slave interface sometimes does not come up on boot Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: Confirmed Status in linux source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in linux source package in Saucy: Won't Fix Status in linux source package in Trusty: Confirmed Bug description: bug report: Hi guys, I'm running ubuntu12.04 server on a HP DL380G7. server01 ~ # lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 I've got 2 ethernet cards with 4x 10G interfaces. I've got a bond on 4x10G where only eth4 and eth6 are patched. server01 ~ # ethtool -i eth4 driver: be2net version: 4.0.100u firmware-version: 4.0.360.15 bus-info: :0e:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no server01 ~ # ethtool -i eth6 driver: be2net version: 4.0.100u firmware-version: 4.0.360.15 bus-info: :15:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE interfaces. However, sometimes I only see 1 interface coming up in the bond after a reboot and when I manually bring the other interface up (ifconfig eth6 up) it works: # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable Active Aggregator Info: Aggregator ID: 2 Number of ports: 1 Actor Key: 33 Partner Key: 32773 Partner Mac Address: 00:23:04:ee:be:01 Slave Interface: eth6 MII Status: down SHOULD BE UP Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 00:9c:02:3c:c9:70 Aggregator ID: 1 Slave queue ID: 0 Slave Interface: eth4 MII Status: up ONLY INTERFACE THAT IS UP Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:9c:02:3c:99:98 Aggregator ID: 2 Slave queue ID: 0 Slave Interface: eth7 MII Status: down Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: 00:9c:02:3c:c9:74 Aggregator ID: 3 Slave queue ID: 0 Slave Interface: eth5 MII Status: down Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: 00:9c:02:3c:99:9c Aggregator ID: 4 Slave queue ID: 0 server01 ~ # ifconfig bond0 Link encap:Ethernet HWaddr 00:9c:02:3c:c9:70 inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:169071 errors:0 dropped:54 overruns:0 frame:0 TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18435358 (18.4 MB) TX bytes:174727 (174.7 KB) eth4 Link encap:Ethernet HWaddr 00:9c:02:3c:c9:70 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:169071 errors:0 dropped:45 overruns:0 frame:0 TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18435358 (18.4 MB) TX bytes:174637 (174.6 KB) eth5 Link encap:Ethernet HWaddr 00:9c:02:3c:c9:70 UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth7 Link encap:Ethernet HWaddr 00:9c:02:3c:c9:70 UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1333 errors:0 dropped:0 overruns:0 frame:0 TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:102784 (102.7 KB) TX bytes:102784 (102.7 KB) vlan888
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
When you have upgraded your BIOS, if this bug reproduces again, please set this bug status back to confirmed. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403918] Re: Lucid update to 2.6.32.65 stable release
** Changed in: linux (Ubuntu Lucid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403918 Title: Lucid update to 2.6.32.65 stable release Status in linux package in Ubuntu: New Status in linux source package in Lucid: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 2.6.32.65 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches are in the 2.6.32.65 stable release: x86, 64-bit: Move K8 B step iret fixup to fault entry asm x86-64: Adjust frame type at paranoid_exit: x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels x86-32, espfix: Remove filter for espfix32 due to race x86-64, espfix: Don't leak bits 31:16 of %esp returning to 16-bit stack x86, espfix: Move espfix definitions into a separate header file x86, espfix: Fix broken header guard x86, espfix: Make espfix64 a Kconfig option, fix UML x86, espfix: Make it possible to disable 16-bit support x86_64/entry/xen: Do not invoke espfix64 on Xen x86/espfix/xen: Fix allocation of pages for paravirt page tables x86_64, traps: Stop using IST for #SS x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C x86_64, traps: Rework bad_iret The following patches from the stable release have been dropped (some were actually already applied to Lucid): net: sendmsg: fix failed backport of fix NULL pointer dereference net/l2tp: don't fall back on UDP [get|set]sockopt ALSA: control: Don't access controls outside of protected regions ALSA: control: Fix replacing user controls USB: whiteheat: Added bounds checking for bulk command response net: sctp: fix panic on duplicate ASCONF chunks net: sctp: fix remote memory pressure from excessive queueing udf: Avoid infinite loop when processing indirect ICBs net: sctp: fix NULL pointer dereference in af-from_addr_param on malformed packet mac80211: fix fragmentation code, particularly for encryption ttusb-dec: buffer overflow in ioctl vlan: Don't propagate flag changes on down interfaces. sctp: Fix double-free introduced by bad backport in 2.6.32.62 md/raid6: Fix misapplied backport in 2.6.32.64 block: add missing blk_queue_dead() checks block: Fix blk_execute_rq_nowait() dead queue handling cciss: Fix misapplied cciss: fix info leak in cciss_ioctl32_passthru() proc connector: Delete spurious memset in proc_exit_connector() Linux 2.6.32.65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403943] [NEW] linux: 2.6.32-71.138 -proposed tracker
Public bug reported: This bug is for tracking the 2.6.32-71.138 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 18. December 2014 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Thursday, 18. December 2014 16:18 UTC ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-ports-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug lucid ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Tags added: lucid ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-ports-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned)
[Kernel-packages] [Bug 1403955] [NEW] DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
Public bug reported:
Using MAAS as DHCP server, the client receives the following IPv4 lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface br0;
fixed-address 10.230.20.26;
filename pxelinux.0;
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name ctsstack.qa.1ss;
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: cts
** Package changed: linux (Ubuntu) = 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/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
Status in Ubuntu:
New
Bug description:
Using MAAS as DHCP server, the client receives the following IPv4
lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface br0;
fixed-address 10.230.20.26;
filename pxelinux.0;
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name ctsstack.qa.1ss;
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1403955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
There were mentions of it happening after a resume from hibernate. Teo, could you please confirm whether or not you've used hibernate again and if it has triggered the bug? You mention later that it happens randomly, but I just want to make it very certain that it can't be reliably triggered by hibernation... rather than assuming anything. To pinpoint this to an update that could have caused this issue, it would be useful to have /var/log/apt/history.log for 2014-08-05 and a few days earlier, if you still have that; along with if you remember when the computer had last been rebooted before you did last reboot you mention in this bug report. I realize this is a long time ago, but if you remember, or if you usually shut down your computer every few days, etc. then it can help figuring out from the apt history log whether a specific package was updated around the same time and could be the cause of the issue, or be a trigger for a BIOS bug. Meaningful packages could still be acpi-support, linux, etc... 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/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402834] Re: fuse filesystems get disconnected on container exit
Serge asked me about potentially using an AppArmor umount rule to prevent forced umounts in the container. After I looked at the AppArmor parser code, I realized that it doesn't properly support umount rules (note that mount rules are properly supported). I've created bug #1403968 to track this AppArmor 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/1402834 Title: fuse filesystems get disconnected on container exit Status in linux package in Ubuntu: Confirmed Bug description: When bind-mounting a directory from a fuse filesytems into a container, then when the container is shut down, the userspace process serving the fuse fs is terminated. The original fuse mountpoint remains busy until it is manually unmounted. I've tested this with sshfs, git://github.com/stgraber/cgmanagerfs, the bbfs example fs from http://www.cs.nmsu.edu/~pfeiffer/fuse-tutorial/, or git://github.com/lxc/lxcfs. To reproduce: Mount a fusefs - say sshfs - with -o allow_other, let's say onto /tmp/d. sshfs -f -d -o allow_other somehost:$HOME /tmp/d Bind that into a container by adding lxc.mount.entry = /tmp/d freezer none bind,create=dir 0 0 to the container's config. start the container, stop it. the fuse program stops (exits 0 in fact) the mount is not cleaned up - ls /tmp/d on the host henceforth complains: ls: cannot access /tmp/d Transport endpoint is not connected (sudo umount /tmp/d cleans it up) I don't know for sure whether this is a kernel or libfuse bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1398171] Re: Update firmware for Intel 3160 / 7260 / 7265 wireless
Verified version 1.127.10 on trusty and 1.138.1 on utopic. The iwlwifi firmware files are updated and work with the relevant hardware/kernels. ** Tags added: verification-done-trusty verification-done-utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1398171 Title: Update firmware for Intel 3160 / 7260 / 7265 wireless Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Committed Status in linux-firmware source package in Utopic: Fix Committed Status in linux-firmware source package in Vivid: Fix Released Bug description: Intel has released bug fix updates to the firmware for these devices. Update linux-firmware for affected releases to receive the bug fixes. Version number: 25.228.9.0 Revision number: 85188 Build number: WFFW08523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1398171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1314245] Re: Missing r8169 firmware warning when installing Trusty kernel
Just did an upgrade and got this at the end: update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 status:Confirmed → Fix Released kinda suggests this shouldn't have happened, or am I missing something? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1314245 Title: Missing r8169 firmware warning when installing Trusty kernel Status in linux-firmware package in Ubuntu: Fix Released Status in linux-meta-lts-trusty package in Ubuntu: Fix Released Bug description: I'm running the linux-generic-lts-saucy stack with no problem, but when I upgrade to linux-generic-lts-trusty on my 12.04 machine, I get this warning and had to revert back to the saucy stack: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 I'm not sure if this has been fixed in a newer version of the kernel, but I wanted to put that out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1314245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403943] Re: linux: 2.6.32-71.138 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/prepare-package-ports-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-ports-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403943 Title: linux: 2.6.32-71.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-71.138 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 18. December 2014 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Thursday, 18. December 2014 16:18 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
** Also affects: virtualbox (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: virtualbox (Ubuntu Precise) Status: New = Triaged ** Changed in: virtualbox (Ubuntu Precise) Importance: Undecided = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in NULL Project: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Committed Status in linux source package in Precise: New Status in virtualbox source package in Precise: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
Hello Jason, or anyone else affected, Accepted virtualbox into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/4.1.12-dfsg-2ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: virtualbox (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in NULL Project: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Committed Status in linux source package in Precise: New Status in virtualbox source package in Precise: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
Due to your careful question, it turned out, that I have made very serious error! When installing your Utopic test kernel with commit b47f210 reverted I did not install the linux-image-extra... I tried to check whether I did same kind of error earlier. In case of 3.13.0-36-generic, 3.13.0-36-generic and 3.16.0-28-generic, and in general, if the installation source was an Ubuntu release, then the extra was there always. In case of kernel-PPA, following the https://wiki.ubuntu.com/Kernel/MainlineBuilds tips ( comment here: #30), I installed the headers as well, while I did NOT installed the kernel extra, since there is no such separated stuff. I tested quite a lot of kernels. But, do I see correctly, that a size of greater than 50MB of kernel binary package means, that that package contains the extras as well? I see, when there is a separate extra package, then the normal and extra package together is slighly larger than the single over 50MB kernel binary package, this is why I think that this kind of single package contains the extras as well. Then I got 4 different kernels upto diverse commits, but since they are gone from the URL you gave me, I can not RETEST them, ... while I am suspicious that I did not install the extras, but may happen that I installed on the base of why not if it is there, simply I do not remember. Now in case of the latest kernel, which is already an Utopic test kernel with commit b47f210 reverted, I am sure, that I did NOT install extras. However this kernel without the extras, --- due to it's revision number collision with the similar kernel of the normal Ubuntu release, --- is sensitive to whether the packages of the normal Ubuntu kernels are there or not. In my #42 comment: the extras of the normal release kerlen of the same version number was there, while the extras you provided were NOT installed, and in this case I get the usual error. But, if I remove any trace of the normal release kernel, and then I install your kernel with extras, then IT WORKS, ... actually I write this comment using your latest kerenel provided me! I try to prevent this kernel from updating by the automatic updating system of Ubuntu. Is installing linux-image-### and linux-image-extra-### enough to get rid of the other kernel with same version number, or what I have to do to make a clean install of the kernels you gave me? In short: 3.13.0-36-generic works, 3.13.0-37-generic has the issue, official 3.16.0-28-generic also has the issue, but YOUR 3.16.0-28-generic WORKS. I really excuse myself for my big error and WASTING YOUR TIME, and naturally I am ready to repeat former tests, if you could provide those packages again. This week I prepared to formulate my thanks that regardless of we know each other you give your time and knowledge, ... and jut in this week I had to discover my error vasting resources. I advocate the free softwares approximately since two and half decades, as a university staff, so in theory I understand the importance and the meaning of this global movement, ... but it is very touching to have such an abstract and at the same time personal experinece, that someone from the mankind whom I even don't know on which continent is resident, helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in linux package in Ubuntu: Confirmed Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user
[Kernel-packages] [Bug 1403473] Re: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403473 Title: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy bluez bluez: Installato: 4.101-0ubuntu13 Candidato: 4.101-0ubuntu13 Tabella versione: *** 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installato: 1.23-git201403102151-1ubuntu1 Candidato: 1.23-git201403102151-1ubuntu1 Tabella versione: *** 1.23-git201403102151-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status My smartphone is paired but is not connected, so I can not send nor receive files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stumbo 2431 F pulseaudio /dev/snd/controlC0: stumbo 2431 F pulseaudio Date: Wed Dec 17 12:28:42 2014 HibernationDevice: RESUME=UUID=cbbe8973-68a9-4eda-b1ff-9cf98e1279c6 InstallationDate: Installed on 2014-04-28 (233 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=45f86510-c10c-4bb4-85f7-8b4e2c9a6708 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55-M 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.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M: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/1403473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403868] Re: Lockup during boot with latest 14.10 and 14.04 LTS
No, booting older kernels doesn't work either. What usually does work, however, is to boot any kernel in recovery mode and then hit resume in the recovery menu. Booting this way, graphics will look a bit jaggy, and two CIFS mounts will be missing. I vaguely suspect that the problem may be related to the CIFS mounts, but haven't been able to confirm it, so far. Unfortunately, all of this happens before the netconsole will start transmitting messages to the machine which does the logging, so I'll be glad for any hints what I might do to defer the crash until later in the boot process. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403868 Title: Lockup during boot with latest 14.10 and 14.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot. There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: masterbrain 1936 F lxpanel CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE Date: Thu Dec 18 13:43:11 2014 HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688 InstallationDate: Installed on 2014-12-12 (5 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 002: ID 4146:ba63 USBest Technology 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: System Manufacturer System Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004 dmi.board.name: P4PE-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/1403868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403999] [NEW] libcrc32c: module verification failed: signature and/or required key missing - tainting kernel
Public bug reported: Hello, I updated Ubuntu yesterday w/ the following packages: Start-Date: 2014-12-17 16:46:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.406' Upgrade: linux-headers-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-common:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en:amd64 (14.10+20141020, 14.10+20141205), linux-headers-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-extra-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-signed-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en-base:amd64 (14.10+20141020, 14.10+20141205), linux-libc-dev:amd64 (3.16.0-28.37, 3.16.0-28.38) End-Date: 2014-12-17 16:47:03 After the update, I noticed the following lines in dmesg: [450533.640533] Request for unknown module key 'Magrathea: Glacier signing key: af30e7f37b41301c96f985f4789da5f4373e9e92' err -11 [450533.640575] libcrc32c: module verification failed: signature and/or required key missing - tainting kernel Should I be worried? I didn't reboot yet but I have secure boot disabled so I don't think that I would have any issue bug I'm wondering why I got hat msg. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403999 Title: libcrc32c: module verification failed: signature and/or required key missing - tainting kernel Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated Ubuntu yesterday w/ the following packages: Start-Date: 2014-12-17 16:46:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.406' Upgrade: linux-headers-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-common:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en:amd64 (14.10+20141020, 14.10+20141205), linux-headers-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-extra-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-signed-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en-base:amd64 (14.10+20141020, 14.10+20141205), linux-libc-dev:amd64 (3.16.0-28.37, 3.16.0-28.38) End-Date: 2014-12-17 16:47:03 After the update, I noticed the following lines in dmesg: [450533.640533] Request for unknown module key 'Magrathea: Glacier signing key: af30e7f37b41301c96f985f4789da5f4373e9e92' err -11 [450533.640575] libcrc32c: module verification failed: signature and/or required key missing - tainting kernel Should I be worried? I didn't reboot yet but I have secure boot disabled so I don't think that I would have any issue bug I'm wondering why I got hat msg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403999] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1403999 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403999 Title: libcrc32c: module verification failed: signature and/or required key missing - tainting kernel Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated Ubuntu yesterday w/ the following packages: Start-Date: 2014-12-17 16:46:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.406' Upgrade: linux-headers-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-common:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en:amd64 (14.10+20141020, 14.10+20141205), linux-headers-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-tools-3.16.0-28:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-image-extra-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), linux-signed-image-3.16.0-28-generic:amd64 (3.16.0-28.37, 3.16.0-28.38), language-pack-gnome-en-base:amd64 (14.10+20141020, 14.10+20141205), linux-libc-dev:amd64 (3.16.0-28.37, 3.16.0-28.38) End-Date: 2014-12-17 16:47:03 After the update, I noticed the following lines in dmesg: [450533.640533] Request for unknown module key 'Magrathea: Glacier signing key: af30e7f37b41301c96f985f4789da5f4373e9e92' err -11 [450533.640575] libcrc32c: module verification failed: signature and/or required key missing - tainting kernel Should I be worried? I didn't reboot yet but I have secure boot disabled so I don't think that I would have any issue bug I'm wondering why I got hat msg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge
Stephane The network itself is pretty stock; the mtu on the switches is set to 9000; other than that its pretty much the standard cisco configuration for the switch model. I have the full details (but can't put them here :-)). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402763 Title: Multicast traffic not propating correctly over linux bridge Status in juju-core: Triaged Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: There's a lot of supposition in the title of this bug but its currently my best guess. In this deployment, I have a number of services running in LXC containers across multiple physical hosts; each service is clustered across three units, all on separate physical hosts, using corosync and pacemaker; when using multicast to support cluster communication, I occasionally see a container drop out of the cluster and use its isolation response (to shutdown all managed services); when using unicast I've not yet see this same problem. LXC containers are bridged to the main physical network using a linux bridge: eth0 - juju-br0 - vethXXX - | vethXXX | All MTU's are standard (1500). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.6-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 15 17:20:08 2014 ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 17 10:16 seq crw-rw 1 root audio 116, 33 Dec 17 10:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: lxc 1.0.6-0ubuntu0.1 PackageArchitecture: amd64 PciMultimedia: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images trusty uec-images apparmor Uname: Linux 3.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo video _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dmi.bios.date: 08/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.0.7 dmi.board.name: 0F0XJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1404005] [NEW] backlight problem ubuntu 14-04
Public bug reported: unless you decrease the value of the brighness, the screen stays at maximum brightness. I do not like to type all kind of unsure command line code from which my ubuntu crashes, so i report it this way. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kees 2136 F pulseaudio /dev/snd/controlC0: kees 2136 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 18 20:43:18 2014 HibernationDevice: RESUME=UUID=f68b02a8-1195-4854-b575-f030bc5179cc InstallationDate: Installed on 2014-09-09 (100 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8570w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=b2358b56-bfb8-4787-b341-8dd2789fbe7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.43 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.43:bd10/08/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1009C12:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8570w dmi.product.version: A1009C12 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404005 Title: backlight problem ubuntu 14-04 Status in linux package in Ubuntu: New Bug description: unless you decrease the value of the brighness, the screen stays at maximum brightness. I do not like to type all kind of unsure command line code from which my ubuntu crashes, so i report it this way. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kees 2136 F pulseaudio /dev/snd/controlC0: kees 2136 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 18 20:43:18 2014 HibernationDevice: RESUME=UUID=f68b02a8-1195-4854-b575-f030bc5179cc InstallationDate: Installed on 2014-09-09 (100 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8570w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=b2358b56-bfb8-4787-b341-8dd2789fbe7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.43 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.43:bd10/08/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1009C12:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8570w dmi.product.version: A1009C12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1404005] 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/1404005 Title: backlight problem ubuntu 14-04 Status in linux package in Ubuntu: Confirmed Bug description: unless you decrease the value of the brighness, the screen stays at maximum brightness. I do not like to type all kind of unsure command line code from which my ubuntu crashes, so i report it this way. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kees 2136 F pulseaudio /dev/snd/controlC0: kees 2136 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 18 20:43:18 2014 HibernationDevice: RESUME=UUID=f68b02a8-1195-4854-b575-f030bc5179cc InstallationDate: Installed on 2014-09-09 (100 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 8570w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=b2358b56-bfb8-4787-b341-8dd2789fbe7b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.43 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.43:bd10/08/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1009C12:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8570w dmi.product.version: A1009C12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251065]
(In reply to Ander Conselvan de Oliveira from comment #34) (In reply to Peter Rimshnick from comment #33) Comment on attachment 93360 [details] tarball of dmesg output and Xorg.0.log Did you set drm.debug=6 in the kernel command line? The dmesg output is missing debugging information. I think I accidentally commented on the wrong attachment. My logs are attachment 110965. If you grep dmesg for drm you can see my command line. Please let me know if it is incorrect. 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/1251065 Title: HP Mini 1000 fails to resume from suspend Status in The Linux Kernel: Confirmed Status in linux package in Ubuntu: In Progress Bug description: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1251065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]
I'm running precise with the Trusty HWE. I just installed the latest from proposed - virtualbox 4.1.12-dfsg-2ubuntu0.7 It seems to have loaded up find after a reboot, and I could start up a VM. 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/1292118 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected] Status in NULL Project: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Committed Status in linux source package in Precise: New Status in virtualbox source package in Precise: Fix Committed Bug description: The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 DKMSKernelVersion: 3.13.0-17-generic Date: Thu Mar 13 12:40:09 2014 DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected InstallationDate: Installed on 2012-04-29 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.5 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1292118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
if someone treats you steadily disrespectful there's no single reason for continuing the business. Because there's no single excuse for mistreating other people. That's funny. Have you ever considered how dismissing tons of bug reports just because they don't meet some rigid criteria is actually disrespectful to those who took the time to report them, if not to users who simply suffer from them? And in the case at hand, even to people (and I'm not talking about myself, obviously) who are actively trying to help triage it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
Teo, could you please confirm whether or not you've used hibernate again and if it has triggered the bug? You mention later that it happens randomly, but I just want to make it very certain that it can't be reliably triggered by hibernation... rather than assuming anything. I'm sorry, I can't confirm nor discard that. I can definitely say that resuming from hibernation does not _systematically_ trigger the issue, that is, it is not a _sufficient_ condition to trigger the issue, but I can't tell for sure whether it is a _necessary_ condition. In other words, I have certainly hibernated and resumed many times without observing the issue, but I can't tell for sure if every time I observed the issue it was after resuming from hibernation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
#222 can you help me at installing your driver for gnome ubuntu 14.10 ? i could not opened makefile and others in the submenu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
apt log history ** Attachment added: history.log.4 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+attachment/4283714/+files/history.log.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
along with if you remember when the computer had last been rebooted before you did last reboot you mention in this bug report. Sorry, no idea. I usually only suspend and resume. I only shut down when I have to carry the laptop somewhere, in which case I either actually shut down or just hibernate. Regarding pure reboot (as opposed to shutdown) I almost never do that unless I'm forced to (e.g. when the prompt to do so becomes really annoying or when the OS is misbehaving beyond telling). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
Copied to -proposed. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) ** Changed in: linux-ti-omap4 (Ubuntu) Status: New = Invalid -- 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/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 18. December 2014 16:02 UTC kernel-stable-Prepare-package-end:Thursday, 18. December 2014 16:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 18. December 2014 16:02 UTC ppa-package-testing-start:Thursday, 18. December 2014 16:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
In reply to @Teo, for the future, you can also report bugs against Ubuntu itself without pre-assigning any package at all. I'll try next time. I gave up trying that long ago because 1) $ ubuntu-bug ubuntu dpkg-query: no packages found matching ubuntu 2) The Report a bug link used to point to an annoying page full of bla bla bla, and I got tired of sorting out the path of links that would eventually land you to the page for reporting a bug (I see it nows points directly to it) 3) A few times I tried by doing ubuntu-bug linux (or whatever other package) from the terminal and then check the I don't know radio button instead of the named package, but the result was the same as choosing the given package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
teo1978: That's funny. Have you ever considered how dismissing tons of bug reports just because they don't meet some rigid criteria is actually disrespectful to those who took the time to report them, if not to users who simply suffer from them? Why do you think asking to upgrade your BIOS is rigid criteria? teo1978: And in the case at hand, even to people (and I'm not talking about myself, obviously) who are actively trying to help triage it. That's me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388583] Re: 15c2:0038 Unable to boot from S5 with Soundgraph iMon IR module
Thank you, Tocinillo! Works like a charm even without lirc (which seems to break the remote wake up facility)... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1388583 Title: 15c2:0038 Unable to boot from S5 with Soundgraph iMon IR module Status in linux package in Ubuntu: Triaged Bug description: After complete Ubuntu shut down, the system does not wake up with Soundgraph Imon IR. Since complete remote boot is possible after Windows shutdown, this seems to be a Linux Kernel bug and related to the way Linux handles the shut down process. Some users have reported that remote boot was possible with Kernels prior to 2.6.32 version. There are several topics around the issue I have, but I was unable to find any bug reports of the issue. Please refer: http://ubuntuforums.org/showthread.php?t=2014242 http://www.soundgraph.com/forums/showthread.php?p=37616 http://forum.kodi.tv/showthread.php?tid=194870 http://ubuntuforums.org/showthread.php?t=2219778 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niemikorpi 1861 F pulseaudio /dev/snd/controlC0: niemikorpi 1861 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 2 18:01:57 2014 HibernationDevice: RESUME=UUID=deab300a-6f47-44e7-834e-94ac0954061a InstallationDate: Installed on 2014-10-15 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=78e2c4b6-1ff6-4e09-ae97-92a0f97acbb5 ro nomodeset quiet splash nomodeset video=uvesafb:mode_option=800x600-24[A,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux StagingDrivers: lirc_imon UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A:rvrRev1.xx: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/1388583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385137] Re: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse
Unfortunately not. :( Even in Linux 3.18. Of course I am willing to assist anyone who could try to fix this. Any idea? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1385137 Title: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: The touchpad on my ASUS N550JK laptop is being recognized as a PS/2 Logitech Wheel Mouse, rather than as a touchpad. In this configuration it only works to move the pointer or clicking, all the advanced features (multi-touch, pinch, zoom, scroll...) can't be properly configured. This is the output of xinput: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB2.0 UVC HD Webcamid=11 [slave keyboard (3)] ↳ Asus WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2857 F pulseaudio /dev/snd/controlC0: ubuntu 2857 F pulseaudio CasperVersion: 1.345 CurrentDesktop: Unity Date: Fri Oct 24 09:09:20 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. N550JK ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/home/fil/Downloads/username-14.10-desktop-amd64.iso locale=en_US.UTF-8 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.207:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403943] Re: linux: 2.6.32-71.138 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403943 Title: linux: 2.6.32-71.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-71.138 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 18. December 2014 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Thursday, 18. December 2014 16:18 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403239] Re: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 18. December 2014 16:02 UTC kernel-stable-Prepare-package-end:Thursday, 18. December 2014 16:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 18. December 2014 16:02 UTC ppa-package-testing-start:Thursday, 18. December 2014 16:02 UTC + kernel-stable-Promote-to-proposed-end:Thursday, 18. December 2014 22:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1403239 Title: linux-ti-omap4: 3.2.0-1458.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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 3.2.0-1458.78 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 16. December 2014 23:03 UTC kernel-stable-master-bug:1403154 kernel-stable-Certification-testing-end:Thursday, 18. December 2014 12:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Thursday, 18. December 2014 16:02 UTC kernel-stable-Prepare-package-end:Thursday, 18. December 2014 16:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 18. December 2014 16:02 UTC ppa-package-testing-start:Thursday, 18. December 2014 16:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 18. December 2014 22:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1403239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1378547] Re: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse
*** This bug is a duplicate of bug 1385137 *** https://bugs.launchpad.net/bugs/1385137 ** This bug has been marked a duplicate of bug 1385137 [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378547 Title: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse Status in linux package in Ubuntu: Triaged Bug description: The touchpad on my ASUS N550JK laptop is being recognized as a PS/2 Logitech Wheel Mouse, rather than as a touchpad. As such, I haven't been able to turn on edge- or two-finger-scrolling, which would be most desirable. The touchpad does function as a simple mouse for moving the cursor and clicking, however. (I'm sure there are other issues appearing in the log, too. This is a fresh install on a new computer, so I'm working out the issues in the order in which they annoy me.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carla 2146 F pulseaudio /dev/snd/controlC0: carla 2146 F pulseaudio CurrentDesktop: XFCE Date: Tue Oct 7 18:03:16 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-04 (3 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) MachineType: ASUSTeK COMPUTER INC. N550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=04a55b0a-be76-49d3-a58a-c6707a5840ef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.207:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
Why do you think asking to upgrade your BIOS is rigid criteria? Asking to upgrade the BIOS is fine. Refusing to look into the issue unless the BIOS is updated is ridiculous. Updating the BIOS is a tremendously cumbersome (and risky) process for a user whose main working OS is Ubuntu. Hence most users just won't do that (I won't), which means the bug will expire. And in the vast majority of cases, there won't be a good reason for that because (1) it's extremely unlikely that the issue is caused _solely_ by a bug in the bios; (2) even if updating the bios makes the issue disappear, it doesn't mean that the issue is a bug in the bios; actually it may mean that it is an issue in the software triggered by some peculiarity in the bios that is not even a bug, in which case the issue SHOULD be investigated with the bios that triggers it, in order to fix a bug rather than make it invisible (and perhaps resurface later); (3) even in the event that the bug is triggered by a bug in the bios, chances are that the OS is not responding correctly to the incorrect behavior of the bios, i.e. there could be a bug in the bios _and_ the OS, and finally (4) I remember Ubuntu being announced as linux for human beings or something like that: if you really want it to be that, you must assume that there are a lot of machines out there with outdated bioses, and some of their human being owners just won't ever update a bios (or have an idea of what it is) until the day when a friendly popup appears allowing them to do it as easily as installing software updates (let's forget for a moment that even upgrading Ubuntu can brick a computer). So, given that the vast majority of bios bugs can almost certainly be worked around by the OS (just think of other OSes that work on machines with the same outdated bios and don't exhibit the issue), the OS should either do that or provide a really stright-forward way to update the bios. The latter may (to some extent) be not in the OS developers' hands ; the former definitely is. That's me! Yes, I guess, but I was referring more specifically to another contributor who has been accused of being rude. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in linux package in Ubuntu: Incomplete Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1404036] [NEW] USB3 stop working after some seconds of usage
Public bug reported: On trusty I plug a pendrive to my USB3 and try copying a big file. After less than a minute the drive files. This pendrive work ok on any usb2 port on the same computer. The USB is: 03:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) And firmware is updated to latest version (F402103FWUP1.zip). Device works ok on windows7 ** Affects: linux (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/1404036 Title: USB3 stop working after some seconds of usage Status in linux package in Ubuntu: New Bug description: On trusty I plug a pendrive to my USB3 and try copying a big file. After less than a minute the drive files. This pendrive work ok on any usb2 port on the same computer. The USB is: 03:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) And firmware is updated to latest version (F402103FWUP1.zip). Device works ok on windows7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1404036] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1404036 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/1404036 Title: USB3 stop working after some seconds of usage Status in linux package in Ubuntu: Incomplete Bug description: On trusty I plug a pendrive to my USB3 and try copying a big file. After less than a minute the drive files. This pendrive work ok on any usb2 port on the same computer. The USB is: 03:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) And firmware is updated to latest version (F402103FWUP1.zip). Device works ok on windows7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402141] Re: Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
I see an updated patch has landed here:
https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/commit/?h=nextid=d70a54e2d08510a99b1f10eceeae6f2f7086e226
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402141
Title:
Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
Status in linux package in Ubuntu:
Triaged
Bug description:
== Comment: #0 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-18
12:28:42 ==
Using Ubuntu as the host, if you add smt-enabled=off as kernel argument, the
system will boot until the Freeing initrd memory line:
...
[1.371729] vgaarb: loaded
[1.372989] SCSI subsystem initialized
[1.373977] libata version 3.00 loaded.
[1.374158] usbcore: registered new interface driver usbfs
[1.374246] usbcore: registered new interface driver hub
[1.374382] usbcore: registered new device driver usb
[1.374505] pps_core: LinuxPPS API ver. 1 registered
[1.374563] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
Giometti giome...@linux.it
[1.374671] PTP clock support registered
[1.377135] NetLabel: Initializing
[1.377218] NetLabel: domain hash size = 128
[1.377328] NetLabel: protocols = UNLABELED CIPSOv4
[1.377472] NetLabel: unlabeled traffic allowed by default
[1.377983] Switched to clocksource timebase
[1.395029] AppArmor: AppArmor Filesystem Enabled
[1.402044] NET: Registered protocol family 2
[1.403795] TCP established hash table entries: 524288 (order: 6, 4194304
bytes)
[1.408343] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[1.409301] TCP: Hash tables configured (established 524288 bind 65536)
[1.409490] TCP: reno registered
[1.409645] UDP hash table entries: 65536 (order: 5, 2097152 bytes)
[1.411943] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes)
[1.415409] NET: Registered protocol family 1
[1.415753] PCI: CLS 128 bytes, default 128
[1.415962] Trying to unpack rootfs image as initramfs...
[2.250464] Freeing initrd memory: 21952K (c382 -
c4d9)
Machine Type = Power 8 (S822L)
== Comment: #1 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com -
2014-11-18 13:42:37 ==
What is the firmware version?
Cascardo.
== Comment: #2 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
07:13:35 ==
Currently is FW810.02 (SV810_061). Will update it today.
Smorigo.
== Comment: #3 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
12:47:24 ==
Updated to FW810.20 (SV810_101). Nothing changed.
== Comment: #4 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 05:47:45 ==
I reproduce it on a s824 with the FW810.20 (TV810_101) firmware, running
14.04.2 alpha (kernel 3.16.0-25). The issue doesn't show up with kernel
3.13.0-39. I shall try mainline and do some bisect.
== Comment: #5 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 13:31:03 ==
FYI issue is upstream.
== Comment: #6 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-24
11:23:04 ==
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
== Comment: #7 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-24 12:08:33 ==
(In reply to comment #6)
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
Yes I am.
== Comment: #8 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 04:56:07 ==
The hang occurs because all running threads are looping in the split core
code:
static void wait_for_sync_step(int step)
{
int i, cpu = smp_processor_id();
for (i = cpu + 1; i cpu + threads_per_core; i++)
while(per_cpu(split_state, i).step step)
barrier();
The problem is that the split core code needs all possible threads to
participate... if the kernel is booted with smt-enabled set to something
different than the maximum value, some threads are missing and this ruins the
sync.
== Comment: #9 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 05:24:28 ==
The current implementaqtion for smt-enabled= is a hack: it simply leaves hw
threads looping where they happen to be (firmware probably)... This isn't
acceptable in a production environment.
An acceptable fix would be to start all threads anyway and offline
the ones that need to be to honour the requested SMT mode AFTER
subcores init. This requires a non-trivial patch.
Since changing SMT mode from userspace when the system is booted is
really straightforward, Michael Ellerman suggests we simply drop that
smt-enabled= feature.
Smorigo,
Why were you using smt-enabled= ? Is there a reason not to do it after the
system is booted with
ppc64_cpu --smt or writing directly to /sys/devices/system/cpu/cpu*/online ?
== Comment: #10 - Paulo
