[Kernel-packages] [Bug 1308871] [NEW] dmesg prints xhci error messages after resuming from s3
Public bug reported: kernel: 3.13.0-24-generic xhci controller: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:501c] Flags: bus master, medium devsel, latency 0, IRQ 56 Memory at f170 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Adam Lee (adam8157) Status: New ** Tags: blocks-hwcert-enablement ** Description changed: [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 - error messages popped out after resuming from s3, annoying. + error messages popped up after resuming from s3, annoying. ** Summary changed: - xhci error messages after resuming from s3 + dmesg prints xhci error messages after resuming from s3 ** Tags added: blocks-hwcert-enablement ** Description changed: + kernel: 3.13.0-24-generic + [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. ** Description changed: kernel: 3.13.0-24-generic + + xhci controller: + 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) + Subsystem: Lenovo Device [17aa:501c] + Flags: bus master, medium devsel, latency 0, IRQ 56 + Memory at f170 (64-bit, non-prefetchable) [size=64K] + Capabilities: [70] Power Management version 2 + Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ + Kernel driver in use: xhci_hcd + [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308871 Title: dmesg prints xhci error messages after resuming from s3 Status in HWE Next Project: New Status in “linux” package in Ubuntu: New Bug description: kernel: 3.13.0-24-generic xhci controller: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:501c] Flags: bus master, medium devsel, latency 0, IRQ 56 Memory at f170 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700
[Kernel-packages] [Bug 1308871] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1308871 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/1308871 Title: dmesg prints xhci error messages after resuming from s3 Status in HWE Next Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: kernel: 3.13.0-24-generic xhci controller: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:501c] Flags: bus master, medium devsel, latency 0, IRQ 56 Memory at f170 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308871] Re: dmesg prints xhci error messages after resuming from s3
** Changed in: linux (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308871 Title: dmesg prints xhci error messages after resuming from s3 Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Bug description: kernel: 3.13.0-24-generic xhci controller: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:501c] Flags: bus master, medium devsel, latency 0, IRQ 56 Memory at f170 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304246] Re: Reboot hangs with Dell computers on 64 bits
I understood something today :
When i pass kernel option reboot=bios, on all dell machine, only reboot
command works
Ctrl+alt+suppr, and graphic reboot hangs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304246
Title:
Reboot hangs with Dell computers on 64 bits
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
On xubuntu 12.04.3 64 bits, with Dell computer (7010 and some other
optiplex), reboot hangs and display terminal :
acpid exiting
running unnatend : ...
I had same problem on 32 bits 12.04, but solved by adding acpi=force
reboot=pci in /etc/default/grub
Here, on 64 bits, tried that and didn't work.
I also tried every other reboot parameter, without success.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-54-generic 3.2.0-54.82
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
Uname: Linux 3.2.0-54-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: speech-dispatcher 1289 F pulseaudio
root 2212 F xfce4-volumed
/dev/snd/pcmC0D0p: speech-dispatcher 1289 F...m pulseaudio
/dev/snd/timer: speech-dispatcher 1289 f pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf irq 43'
Mixer name : 'Generic 1af4 ID 21'
Components : 'HDA:1af40021,1af40021,00100101'
Controls : 2
Simple ctrls : 2
Date: Tue Apr 8 10:00:21 2014
HibernationDevice: RESUME=UUID=2b0136a6-76ae-42a5-a166-a2e6af4c0e17
InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
MachineType: Bochs Bochs
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-54-generic
root=UUID=1be3fd89-b18b-4f55-ab8f-1f9e26e57c01 ro quiet splash acpi=force
reboot=b 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.2.0-54-generic N/A
linux-backports-modules-3.2.0-54-generic N/A
linux-firmware1.79.9
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304246/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308761] Re: apparmor spams log with warning message
For me I have a similar issues... the log says: Apr 17 02:29:36 trusty-01 kernel: [70827.909934] [ cut here ] Apr 17 02:29:36 trusty-01 kernel: [70827.909960] WARNING: CPU: 0 PID: 2985 at /build/buildd/linux-3.13.0/security/apparmor/lsm.c:839 apparmor_unix_may_send+0x16c/0x180() Apr 17 02:29:36 trusty-01 kernel: [70827.909964] AppArmor WARN apparmor_unix_may_send: ((!aa_label_is_subset(cxt-label, label))): Apr 17 02:29:36 trusty-01 kernel: [70827.909968] Modules linked in: kvm_intel kvm cirrus snd_hda_intel ttm snd_hda_codec drm_kms_helper snd_hwdep psmouse serio_raw snd_pcm drm snd_page_alloc snd_timer syscopyarea snd soundcore sysfillrect sysimgblt i2c_piix4 lp parport mac_hid 8139too 8139cp mii floppy Apr 17 02:29:36 trusty-01 kernel: [70827.910014] CPU: 0 PID: 2985 Comm: dhcpd Tainted: GW3.13.0-24-generic #46-Ubuntu Apr 17 02:29:36 trusty-01 kernel: [70827.910018] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Apr 17 02:29:36 trusty-01 kernel: [70827.910022] 0009 88063bd0 81715a64 88063c18 Apr 17 02:29:36 trusty-01 kernel: [70827.910030] 88063c08 810676bd 88003e00a430 88003d618000 Apr 17 02:29:36 trusty-01 kernel: [70827.910036] 88003b33f010 88003d70f400 88003c1a8000 88063c68 Apr 17 02:29:36 trusty-01 kernel: [70827.910043] Call Trace: Apr 17 02:29:36 trusty-01 kernel: [70827.910056] [81715a64] dump_stack+0x45/0x56 Apr 17 02:29:36 trusty-01 kernel: [70827.910066] [810676bd] warn_slowpath_common+0x7d/0xa0 Apr 17 02:29:36 trusty-01 kernel: [70827.910072] [8106772c] warn_slowpath_fmt+0x4c/0x50 Apr 17 02:29:36 trusty-01 kernel: [70827.910080] [8130ed5c] apparmor_unix_may_send+0x16c/0x180 Apr 17 02:29:36 trusty-01 kernel: [70827.910089] [812cf876] security_unix_may_send+0x16/0x20 Apr 17 02:29:36 trusty-01 kernel: [70827.910097] [816b2575] unix_dgram_sendmsg+0x2a5/0x620 Apr 17 02:29:36 trusty-01 kernel: [70827.910108] [816024eb] sock_sendmsg+0x8b/0xc0 Apr 17 02:29:36 trusty-01 kernel: [70827.910116] [81602691] SYSC_sendto+0x121/0x1c0 Apr 17 02:29:36 trusty-01 kernel: [70827.910125] [8109dd84] ? vtime_account_user+0x54/0x60 Apr 17 02:29:36 trusty-01 kernel: [70827.910137] [81020d35] ? syscall_trace_enter+0x145/0x250 Apr 17 02:29:36 trusty-01 kernel: [70827.910145] [8160319e] SyS_sendto+0xe/0x10 Apr 17 02:29:36 trusty-01 kernel: [70827.910154] [8172663f] tracesys+0xe1/0xe6 Apr 17 02:29:36 trusty-01 kernel: [70827.910158] ---[ end trace 0b1a05a3a90a9dc7 ]--- Apr 17 02:29:46 trusty-01 kernel: [70838.210778] [ cut here ] Apr 17 02:29:46 trusty-01 kernel: [70838.210791] WARNING: CPU: 0 PID: 2985 at /build/buildd/linux-3.13.0/security/apparmor/lsm.c:839 apparmor_unix_may_send+0x16c/0x180() Apr 17 02:29:46 trusty-01 kernel: [70838.210793] AppArmor WARN apparmor_unix_may_send: ((!aa_label_is_subset(cxt-label, label))): Apr 17 02:29:46 trusty-01 kernel: [70838.210794] Modules linked in: kvm_intel kvm cirrus snd_hda_intel ttm snd_hda_codec drm_kms_helper snd_hwdep psmouse serio_raw snd_pcm drm snd_page_alloc snd_timer syscopyarea snd soundcore sysfillrect sysimgblt i2c_piix4 lp parport mac_hid 8139too 8139cp mii floppy Apr 17 02:29:46 trusty-01 kernel: [70838.210817] CPU: 0 PID: 2985 Comm: dhcpd Tainted: GW3.13.0-24-generic #46-Ubuntu Apr 17 02:29:46 trusty-01 kernel: [70838.210818] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Apr 17 02:29:46 trusty-01 kernel: [70838.210820] 0009 88063bd0 81715a64 88063c18 Apr 17 02:29:46 trusty-01 kernel: [70838.210823] 88063c08 810676bd 88003e00a430 88003d618000 Apr 17 02:29:46 trusty-01 kernel: [70838.210826] 88003b33f010 88003d70f400 88003c1a8000 88063c68 Apr 17 02:29:46 trusty-01 kernel: [70838.210829] Call Trace: Apr 17 02:29:46 trusty-01 kernel: [70838.210835] [81715a64] dump_stack+0x45/0x56 Apr 17 02:29:46 trusty-01 kernel: [70838.210840] [810676bd] warn_slowpath_common+0x7d/0xa0 Apr 17 02:29:46 trusty-01 kernel: [70838.210842] [8106772c] warn_slowpath_fmt+0x4c/0x50 Apr 17 02:29:46 trusty-01 kernel: [70838.210846] [8130ed5c] apparmor_unix_may_send+0x16c/0x180 Apr 17 02:29:46 trusty-01 kernel: [70838.210850] [812cf876] security_unix_may_send+0x16/0x20 Apr 17 02:29:46 trusty-01 kernel: [70838.210854] [816b2575] unix_dgram_sendmsg+0x2a5/0x620 Apr 17 02:29:46 trusty-01 kernel: [70838.210860] [816024eb] sock_sendmsg+0x8b/0xc0 Apr 17 02:29:46 trusty-01 kernel: [70838.210863] [81602691] SYSC_sendto+0x121/0x1c0 Apr 17 02:29:46 trusty-01 kernel: [70838.210867] [8109dd84] ? vtime_account_user+0x54/0x60 Apr 17 02:29:46 trusty-01 kernel: [70838.210873]
[Kernel-packages] [Bug 989817] Re: Cannot change bluetooth device name
This bug is still present in Saucy Salamander (13.10) and affects Trusty Tahr (14.04) after upgrading from a previous release. In addition to that in 14.04 there is no way to override the name specified in /var/lib/bluetooth/$ADDR/config through the GUI tools so I have created https://bugs.launchpad.net/ubuntu/+source/unity-control- center/+bug/1308922. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/989817 Title: Cannot change bluetooth device name Status in “bluez” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “bluez” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Confirmed Bug description: First, the bluetooth device name is incorrect by default. It should be like computer name + device number. In Ubuntu 11.10, if the computer name is mypc, the BT device name will be mypc0. However, in 12.04, it's always ubuntu0. Second, the trick using hciconfig hci0 name new_name won't work for 12.04 while it did work for 11.10. The name will restore to ubuntu0 after reboot or restarting bluetooth service. Third, /etc/bluetooth/main.conf doesn't work. If I set the value for name field in the config file, it won't affect the device name. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 Date: Fri Apr 27 23:09:10 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) LANG=en_SG.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/989817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 837196] Re: Cannot change bluetooth name
Hi Mathieu, With regards to changing the hostname in System Information (or through Details in Unity Control Center) - at least on my laptop that is not possible - the field is greyed-out and my hostname is the correct one. Thanks to TJ's comment https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/989817/comments/12, the source of the ubuntu-0 name is clear - it is put there by ubiquity during installation (when the system still has the default hostname - ubuntu). The problem is that, once recorded there (and copied from Live install to /target) it is impossible to override it without editing the corresponding files. At least this is a bug with Ubiquity, but I think that it should be possible to change the device name without editing the config files by hand, so I have opened #1308922 against unity-control-center. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/837196 Title: Cannot change bluetooth name Status in GNOME Bluetooth: Invalid Status in “bluez” package in Ubuntu: Invalid Status in “gnome-bluetooth” package in Ubuntu: Won't Fix Bug description: There is no option to change friendly name in the bluetooth settings. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-bluetooth 3.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.279 Date: Tue Aug 30 07:01:31 2011 LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110828) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/837196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present
** Description changed: I have smart card reader built-into this laptop, however, whenever I insert a card - it'll read it for a few seconds, then the USB connection to the reader gets powered down and thus the card disappears in the systems eyes. After a few seconds, it comes back and everything's happy. Then the cycle repeats again and again and again. - - I think this is more a kernel issue than a pcscd one as, going by the - logs, pcscd appears to be doing the right thing when the card - disappears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpds 3933 F pulseaudio /dev/snd/controlC0: jpds 3933 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 6 18:37:24 2014 HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89 InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307109 Title: Alcor Micro AU9540 keeps powering down when card is present Status in “linux” package in Ubuntu: Confirmed Status in “pcsc-lite” package in Ubuntu: Confirmed Bug description: I have smart card reader built-into this laptop, however, whenever I insert a card - it'll read it for a few seconds, then the USB connection to the reader gets powered down and thus the card disappears in the systems eyes. After a few seconds, it comes back and everything's happy. Then the cycle repeats again and again and again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpds 3933 F pulseaudio /dev/snd/controlC0: jpds 3933 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 6 18:37:24 2014 HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89 InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
Hi Andrew, sorry about the dyndbg. It all lokked like it would be tied to that but right now I am not sure it is. I need to check the code again. If anything else fails we can do a special kernel. I have the same issue as Boris in that I am not able to cause the same problem on HVM guests locally. I am using an Ubuntu base install (Xen-4.2.2 + dom kernel 3.8). xend-config is set to allow ballooning. Now the question is how memory for a guest is configured on the host. I can see the issue on a c3.large instance but we have no way of knowing anything outside the guest. One note, too. There is one other memory related message in the guests dmesg: [0.00] NUMA: Warning: invalid memblk node 0 [mem 0x1-0x0fff] I vaguely remember NUMA related problems at some point. But I cannot remember whether this was something that needed fixes in the hypervisor, the dom0 kernel or the guest kernel. Or combinations of that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
** Changed in: neutron Milestone: icehouse-rc1 = 2014.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/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in devstack - openstack dev environments: In Progress Status in OpenStack Neutron (virtual network service): Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1273386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265885] Re: regression: SynPS/2 touchpad detected as DLL060A:00 pointer
** Description changed: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. WORKAROUND: Execute at a terminal and then reboot your system: echo blacklist i2c_hid | sudo tee -a /etc/modprobe.d/blacklist.conf + + Release Notes Text + Bug:1265885 On some Dell XPS13 systems the Synaptics touchpad is incorrectly recognised as a mouse. See the bug for possible workarounds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265885 Title: regression: SynPS/2 touchpad detected as DLL060A:00 pointer Status in Release Notes for Ubuntu: New Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. WORKAROUND: Execute at a terminal and then reboot your system: echo blacklist i2c_hid | sudo tee -a /etc/modprobe.d/blacklist.conf Release Notes Text Bug:1265885 On some Dell XPS13 systems the Synaptics touchpad is incorrectly recognised as a mouse. See the bug for possible workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300928] Re: linux: 3.11.0-20.34 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed and results are available here: http://people.canonical.com/~hwcert/sru-testing/saucy/3.11.0-20.34 /saucy-proposed.html ** Changed in: kernel-sru-workflow/certification-testing Assignee: Brendan Donegan (brendan-donegan) = Sylvain Pineau (sylvain-pineau) ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress = Fix Released ** Tags added: certification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300928 Title: linux: 3.11.0-20.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: Confirmed Bug description: This bug is for tracking the 3.11.0-20.34 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, 01. April 2014 18:18 UTC kernel-stable-Prepare-package-end:Wednesday, 02. April 2014 17:09 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. April 2014 17:09 UTC ppa-package-testing-start:Wednesday, 02. April 2014 18:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:05 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Certification-testing-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:06 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300455] Re: linux: 3.2.0-61.92 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed and results are available here: http://people.canonical.com/~hwcert/sru-testing/precise/3.2.0-61.92 /precise-proposed.html ** Changed in: kernel-sru-workflow/certification-testing Assignee: Brendan Donegan (brendan-donegan) = Sylvain Pineau (sylvain-pineau) ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress = Fix Released ** Tags added: certification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300455 Title: linux: 3.2.0-61.92 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released 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-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: Fix Released 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: Confirmed Bug description: This bug is for tracking the 3.2.0-61.92 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, 31. March 2014 21:30 UTC kernel-stable-Prepare-package-end:Tuesday, 01. April 2014 16:10 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. April 2014 16:10 UTC ppa-package-testing-start:Tuesday, 01. April 2014 17:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Certification-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Regression-testing-end:Thursday, 10. April 2014 14:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308871] Re: dmesg prints xhci error messages after resuming from s3
** Also affects: linux (Ubuntu Trusty) Importance: Medium Assignee: Adam Lee (adam8157) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308871 Title: dmesg prints xhci error messages after resuming from s3 Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: kernel: 3.13.0-24-generic xhci controller: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:501c] Flags: bus master, medium devsel, latency 0, IRQ 56 Memory at f170 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd [ 1410.931247] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad6c0 [ 1410.931248] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad700 [ 1410.931249] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021e3ad740 [ 1410.931250] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded1980 [ 1410.931251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88021ded19c0 error messages popped up after resuming from s3, annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265885] Re: regression: SynPS/2 touchpad detected as DLL060A:00 pointer
** Changed in: ubuntu-release-notes Status: New = 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/1265885 Title: regression: SynPS/2 touchpad detected as DLL060A:00 pointer Status in Release Notes for Ubuntu: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. WORKAROUND: Execute at a terminal and then reboot your system: echo blacklist i2c_hid | sudo tee -a /etc/modprobe.d/blacklist.conf Release Notes Text Bug:1265885 On some Dell XPS13 systems the Synaptics touchpad is incorrectly recognised as a mouse. See the bug for possible workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1218687] Re: Top-Panel Menus Won't Drop Down for Dbeaver
Thank you Skeewiff, your fix in comment #12 worked for me (Linux 3.11.0-19-generic i686 ubuntu 13.10) aswell - globalmenu is gone but menu is accessible again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1218687 Title: Top-Panel Menus Won't Drop Down for Dbeaver Status in Eclipse: New Status in The Application Menu: Invalid Status in The Kepler Solar Project: New Status in Unity: Invalid Status in Unity GTK+ module: In Progress Status in “linux” package in Ubuntu: Invalid Bug description: I initially installed Dbeaver in 13.04 and then upgraded to Ubuntu 13.10. In 13.04, I was able to drop-down menus located in Unity's top-panel when Dbeaver had focus. However, now these menus won't drop down. I'm not sure that this is Dbeaver specific, or if this bug should be forwarded to the platform that Dbeaver runs on. Video of the issue: http://neartalk.com/ss/dbeaver.mp4 Also see: http://dbeaver.jkiss.org/forum/viewtopic.php?f=2t=1100p=2388#p2388 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lonnie 2077 F pulseaudio /dev/snd/controlC1: lonnie 2077 F pulseaudio /dev/snd/pcmC1D0p: lonnie 2077 F...m pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Thu Aug 29 20:06:25 2013 HibernationDevice: RESUME=UUID=22488e01-19fd-4a14-a063-f03cf6e74e20 InstallationDate: Installed on 2013-08-03 (26 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Studio 1737 MarkForUpload: True ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=09eefca9-6a0b-4c3b-93c6-e4aff4bf1dc7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-28 (1 days ago) dmi.bios.date: 04/14/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Studio 1737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1218687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309007] [NEW] Trusty update to v3.13.10 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 v3.13.10 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 v3.13.10 stable release: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Trusty) 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/1309007 Title: Trusty update to v3.13.10 stable release Status in “linux” package in Ubuntu: New Status in “linux” source package in Trusty: 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 v3.13.10 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 v3.13.10 stable release: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
** 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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 cat9689.tub Here, /usr/bin/time ... is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands ulimit -a, top when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:27 rcu_sched 14 root
[Kernel-packages] [Bug 1309007] Re: Trusty update to v3.13.10 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 v3.13.10 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 v3.13.10 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 v3.13.10 stable release: -The following patches are in the v3.13.10 stable release: + selinux: correctly label /proc inodes in use before the policy is loaded + net: sctp: fix skb leakage in COOKIE ECHO path of chunk-auth_chunk + bridge: multicast: add sanity check for query source addresses + tipc: allow connection shutdown callback to be invoked in advance + tipc: fix connection refcount leak + tipc: drop subscriber connection id invalidation + tipc: fix memory leak during module removal + tipc: don't log disabled tasklet handler errors + inet: frag: make sure forced eviction removes all frags + net: unix: non blocking recvmsg() should not return -EINTR + ipv6: Fix exthdrs offload registration. + bnx2: Fix shutdown sequence + pkt_sched: fq: do not hold qdisc lock while allocating memory + Xen-netback: Fix issue caused by using gso_type wrongly + vlan: Set correct source MAC address with TX VLAN offload enabled + tcp: tcp_release_cb() should release socket ownership + bridge: multicast: add sanity check for general query destination + bridge: multicast: enable snooping on general queries only + net: socket: error on a negative msg_namelen + bonding: set correct vlan id for alb xmit path + eth: fec: Fix lost promiscuous mode after reconnecting cable + ipv6: Avoid unnecessary temporary addresses being generated + ipv6: ip6_append_data_mtu do not handle the mtu of the second fragment properly + net: cdc_ncm: fix control message ordering + vxlan: fix potential NULL dereference in arp_reduce() + vxlan: fix nonfunctional neigh_reduce() + tcp: syncookies: do not use getnstimeofday() + rtnetlink: fix fdb notification flags + ipmr: fix mfc notification flags + ip6mr: fix mfc notification flags + net: micrel : ks8851-ml: add vdd-supply support + netpoll: fix the skb check in pkt_is_ns + tipc: fix spinlock recursion bug for failed subscriptions + ip_tunnel: Fix dst ref-count. + tg3: Do not include vlan acceleration features in vlan_features + virtio-net: correct error handling of virtqueue_kick() + usbnet: include wait queue head in device structure + vlan: Set hard_header_len according to available acceleration + vhost: fix total length when packets are too short + tcp: fix get_timewait4_sock() delay computation on 64bit + xen-netback: remove pointless clause from if statement + ipv6: some ipv6 statistic counters failed to disable bh + netlink: don't compare the nul-termination in nla_strcmp + xen-netback: disable rogue vif in kthread context + Call efx_set_channels() before efx-type-dimension_resources() + net: vxlan: fix crash when interface is created with no group + isdnloop: Validate NUL-terminated strings from user. + isdnloop: several buffer overflows + powernow-k6: disable cache when changing frequency + powernow-k6: correctly initialize default parameters + powernow-k6: reorder frequencies + ARC: [nsimosci] Change .dts to use generic 8250 UART + ARC: [nsimosci] Unbork console + futex: Allow architectures to skip futex_atomic_cmpxchg_inatomic() test + m68k: Skip futex_atomic_cmpxchg_inatomic() test + crypto: ghash-clmulni-intel - use C implementation for setkey() + Linux 3.13.10 ** Changed in: linux (Ubuntu Trusty) 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/1309007 Title: Trusty update to v3.13.10 stable release Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: 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
[Kernel-packages] [Bug 1308297] Re: dell mic mute and audio mute leds can't work
** Also affects: linux (Ubuntu Trusty) Importance: High Assignee: Hui Wang (hui.wang) Status: Incomplete ** Changed in: linux (Ubuntu Trusty) Status: Incomplete = 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/1308297 Title: dell mic mute and audio mute leds can't work Status in HWE Next Project: New Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Bug description: The fix has been accepted by linux-leds repository, it will be merged to linux-3.16. And I need to backport the fix to ubuntu kernel. This bug is for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308796] Re: Bad page map in openjdk-7
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [81715a64] dump_stack+0x45/0x56 [ 2808.161884] [81174183] print_bad_pte+0x1a3/0x250 [ 2808.161886] [81175439] vm_normal_page+0x69/0x80 [ 2808.161888] [8117580b] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [81175cc1] unmap_single_vma+0x81/0xf0 [ 2808.161892] [81176d39] unmap_vmas+0x49/0x90 [ 2808.161894] [8117feec] exit_mmap+0x9c/0x170 [ 2808.161898] [8110fcf3] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [8106482c] mmput+0x5c/0x120 [ 2808.161903] [81069bbc] do_exit+0x26c/0xa50 [ 2808.161906] [810d7591] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [810d83b6] ? futex_wait+0x126/0x290 [ 2808.161909] [8106a41f] do_group_exit+0x3f/0xa0 [ 2808.161912] [8107a050] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [81013448] do_signal+0x48/0x960 [ 2808.161919] [8101b7d9] ? sched_clock+0x9/0x10 [ 2808.161921] [8109d13d] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [82fc] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [8109d76b] ? account_user_time+0x8b/0xa0 [ 2808.161927] [8109dd84] ? vtime_account_user+0x54/0x60 [ 2808.161929] [81013dc9] do_notify_resume+0x69/0xb0 [ 2808.161932] [817266ea] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307105] Re: Kernel install fails due PAE checks
Comment to #11 : Actually the system works with or without the forcepae at boot arguments. When option is removed from /etc/grup/default (and grub updated), everything still works, but /proc/cpuinfo just does not show the pae over there. System bootet without forcepae option: foo@t42:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 1.70GHz stepping: 6 microcode : 0x18 cpu MHz : 1700.000 cache size : 2048 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts est tm2 bogomips: 3397.00 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 32 bits virtual power management: foo@t42:~$ uname -a Linux t42 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks Status in “linux” package in Ubuntu: Triaged Bug description: [TRIAGE NOTE] When a user boots Ubuntu Live/Install media with 'forcepae' option, the option should automatically be added to /etc/default/grub, or kernel upgrades will refuse to install when they do not see pae capability in cpuinfo. [ORIGINAL REPORT] On Thinkpad T42 with Pentium M processor linux image upgrade fails with message This kernel does not support a non-PAE CPU.. System was installed from ubuntu-14.04-beta2-desktop-i386.iso with forcepae kernel option. After install, system works, but cannot be upgraded to laters kernel. root@t42:/boot# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic but it is not installed linux-image-generic : Depends: linux-image-3.13.0-24-generic but it is not installed E: Unmet dependencies. Try using -f. root@t42:/boot# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-24-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-24-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.6 MB of archives. After this operation, 32.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 196089 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1162073] Re: [NP900X4C-A04US] System freeze on high memory usage
I can confirm that I'm also experieancing this bug. 12.04, clean install 16gb ram, 32 swap. It can be replicated in python with: import numpy as np l=[] for i in range(1): l.append(np.array(np.ones(1000), dtype=np.float64)) this can be done in console mode or GUI, the arrays are allocated, ram fills and swap begins, then the system freezes requiring a hard reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1162073 Title: [NP900X4C-A04US] System freeze on high memory usage Status in “linux” package in Ubuntu: Incomplete Bug description: When I use MATLAB and all 8GB of RAM are full, system freezes and only a hard restart can get it working. I have tested it with the newest kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc4-raring/ and it still persists. Would need to increase swap space as outlined in http://www.mathworks.com/help/matlab/matlab_prog/resolving-out-of- memory-errors.html . ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-26-generic 3.5.0-26.42 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivan 2469 F pulseaudio Date: Sat Mar 30 00:49:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4def1db0-01fa-4505-8eb6-97442bc58e4a InstallationDate: Installed on 2013-02-28 (29 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=4936fe74-689d-4768-951a-d793b24ad3cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-26-generic N/A linux-backports-modules-3.5.0-26-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAC:bd08/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307105] Re: Kernel install fails due PAE checks
I'm not sure if a software fix is appropriate here. Should the ubiquity installer do a special check to see if it's been s tarted with forcepae and copy that option to the install regardless of what side of the '--' the user put it on? If not, then this really isn't a bug per se, as better documentation by those suggesting the forcepae option would be the appropriate fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks Status in “linux” package in Ubuntu: Triaged Bug description: [TRIAGE NOTE] When a user boots Ubuntu Live/Install media with 'forcepae' option, the option should automatically be added to /etc/default/grub, or kernel upgrades will refuse to install when they do not see pae capability in cpuinfo. [ORIGINAL REPORT] On Thinkpad T42 with Pentium M processor linux image upgrade fails with message This kernel does not support a non-PAE CPU.. System was installed from ubuntu-14.04-beta2-desktop-i386.iso with forcepae kernel option. After install, system works, but cannot be upgraded to laters kernel. root@t42:/boot# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic but it is not installed linux-image-generic : Depends: linux-image-3.13.0-24-generic but it is not installed E: Unmet dependencies. Try using -f. root@t42:/boot# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-24-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-24-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.6 MB of archives. After this operation, 32.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 196089 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304246] Re: Reboot hangs with Dell computers on 64 bits
What i said, just before was not true... still random reboot problems
with, reboot, shutdown -r, CTRL+ALT+SUPPR
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304246
Title:
Reboot hangs with Dell computers on 64 bits
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
On xubuntu 12.04.3 64 bits, with Dell computer (7010 and some other
optiplex), reboot hangs and display terminal :
acpid exiting
running unnatend : ...
I had same problem on 32 bits 12.04, but solved by adding acpi=force
reboot=pci in /etc/default/grub
Here, on 64 bits, tried that and didn't work.
I also tried every other reboot parameter, without success.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-54-generic 3.2.0-54.82
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
Uname: Linux 3.2.0-54-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: speech-dispatcher 1289 F pulseaudio
root 2212 F xfce4-volumed
/dev/snd/pcmC0D0p: speech-dispatcher 1289 F...m pulseaudio
/dev/snd/timer: speech-dispatcher 1289 f pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf irq 43'
Mixer name : 'Generic 1af4 ID 21'
Components : 'HDA:1af40021,1af40021,00100101'
Controls : 2
Simple ctrls : 2
Date: Tue Apr 8 10:00:21 2014
HibernationDevice: RESUME=UUID=2b0136a6-76ae-42a5-a166-a2e6af4c0e17
InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
MachineType: Bochs Bochs
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-54-generic
root=UUID=1be3fd89-b18b-4f55-ab8f-1f9e26e57c01 ro quiet splash acpi=force
reboot=b 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.2.0-54-generic N/A
linux-backports-modules-3.2.0-54-generic N/A
linux-firmware1.79.9
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304246/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305522] Re: Backport Synaptics HID touchpad driver for 14.04
** Tags added: hw-specific 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/1305522 Title: Backport Synaptics HID touchpad driver for 14.04 Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: Synaptics just upstreamed a new set of HID touchpad driver: http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736 It's better we can have it in 14.04 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1040557] Re: UEFI boot live-usb bricks SAMSUNG 530U3C, np700z5c laptop
The problem is solved in samsung serie 7 chronos (np700z5c) ? In the version ubuntu 14.04? Can I activate the secureboot and install new ubuntu? Thanks, Miguel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1040557 Title: UEFI boot live-usb bricks SAMSUNG 530U3C,np700z5c laptop Status in Ubuntu CD image build software: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in Release Notes for Ubuntu quantal series: Fix Released Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Oneiric: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Bug description: I cannot provide detailed log massages because laptop is bricked right now. If you have courage to try it select UEFI boot from bios and than try to boot laptop using liveusb (made form Precise Pangolin 12.04.1 amd64). Laptop hangs up in black screen. If you force power-off, after it, laptop wont start. I mean it not event start bios, just black screen no sounds nothing. I filing this report, because i already bricked second laptop. At first i thought it was unrelated issue and laptop was fixed by warranty service (replaced motherboard), but after second time i quite sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304246] Re: Reboot hangs with Dell computers on 64 bits
Can you also give the latest 3.8 upstream kernel a test? It is version
3.8.13.21 and can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.21-raring/
Also, the 3.15-rc1 kernel is now out as well. Can you give that a test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/
** 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/1304246
Title:
Reboot hangs with Dell computers on 64 bits
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
On xubuntu 12.04.3 64 bits, with Dell computer (7010 and some other
optiplex), reboot hangs and display terminal :
acpid exiting
running unnatend : ...
I had same problem on 32 bits 12.04, but solved by adding acpi=force
reboot=pci in /etc/default/grub
Here, on 64 bits, tried that and didn't work.
I also tried every other reboot parameter, without success.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-54-generic 3.2.0-54.82
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
Uname: Linux 3.2.0-54-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: speech-dispatcher 1289 F pulseaudio
root 2212 F xfce4-volumed
/dev/snd/pcmC0D0p: speech-dispatcher 1289 F...m pulseaudio
/dev/snd/timer: speech-dispatcher 1289 f pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf irq 43'
Mixer name : 'Generic 1af4 ID 21'
Components : 'HDA:1af40021,1af40021,00100101'
Controls : 2
Simple ctrls : 2
Date: Tue Apr 8 10:00:21 2014
HibernationDevice: RESUME=UUID=2b0136a6-76ae-42a5-a166-a2e6af4c0e17
InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
MachineType: Bochs Bochs
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-54-generic
root=UUID=1be3fd89-b18b-4f55-ab8f-1f9e26e57c01 ro quiet splash acpi=force
reboot=b 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.2.0-54-generic N/A
linux-backports-modules-3.2.0-54-generic N/A
linux-firmware1.79.9
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304246/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296554] Re: bluetooth settings not remembered on reboot
It seems that this bug is a duplicate of Bug #1296114 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1296554 Title: bluetooth settings not remembered on reboot Status in “bluez” package in Ubuntu: Confirmed Bug description: [ The bug ] Bluetooth always remains on when I boot ubuntu, though it switches off when I switch it off. However, if I switch bluetooth off, in the next boot, it will be on. [ How to reproduce ] Reboot ubuntu. The bluetooth will be on. Switch it off manually using the bluetooth icon on the status menu indicator- it switches off. Now reboot ubuntu- bluetooth will be on. [ What did I expect to happen ] Bluetooth will remember whether it was on or off in the previous boot. [ What actually happened ] Bluetooth switches off if manually switched off. However, it remains on on each reboot. [ Environment ] lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Codename: trusty apt-cache policy gnome-bluetooth gnome-bluetooth: Installed: 3.8.2.1-0ubuntu4 Candidate: 3.8.2.1-0ubuntu4 Version table: *** 3.8.2.1-0ubuntu4 0 500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-03-17 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP 630 Notebook PC Package: bluez 4.101-0ubuntu10 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e65dde38-8db3-4375-af07-da5265597b0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3672 dmi.board.vendor: Hewlett-Packard dmi.board.version: 23.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd07/22/2011:svnHewlett-Packard:pnHP630NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3672:rvr23.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 630 Notebook PC dmi.product.version: 058A10004C1000260 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: D0:DF:9A:9F:A1:9A ACL MTU: 1022:8 SCO MTU: 121:3 DOWN RX bytes:505 acl:0 sco:0 events:23 errors:0 TX bytes:329 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1296554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
No difference between boot speeds (3.13 vs. 3.15); deeming: 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/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
Comment #9 also has the difference from the above charts that it's using legacy boot instead of EFI. ** 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/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
This is a bootchart of my system with a stripped down version of Ubuntu. Read: - No recommended packages installed by default. - pkgsel/include set to ubuntu-desktop firefox gnome-screensaver gnome-terminal indicator-application indicator-appmenu indicator-datetime indicator-messages indicator-power indicator-printers indicator-session indicator-sound libreoffice-calc libreoffice-gnome libreoffice-gtk libreoffice-impress libreoffice-writer network-manager network-manager-gnome plymouth-theme-ubuntu-logo rhythmbox ttf-ubuntu-font-family unity-lens-applications unity-lens-files unity-lens-music xchat xchat-indicator ** Attachment added: 3.15 kernel bootchart with stripped down Ubuntu https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+attachment/4086264/+files/ubuntu-trusty-20140417-2-stripped-3.15.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
** Attachment added: 3.15 kernel bootchart with normal Ubuntu (legacy, no EFI) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+attachment/4086265/+files/arwan-trusty-20140417-1.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308788] Re: IMA significantly increases boot time when enabled
** Attachment added: 3.13 kernel bootchart with normal Ubuntu (legacy, no EFI) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+attachment/4086266/+files/arwan-trusty-20140417-2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308788 Title: IMA significantly increases boot time when enabled Status in “linux” package in Ubuntu: Confirmed Bug description: I have a TPM-enabled laptop (sudo apt-get install trousers tpm-tools sudo tpm_takeownership) and enabled IMA with the following boot options in GRUB: ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix As shown from the attached bootcharts, the boot time goes from circa 25s to circa 225s on an i7, SSD-based system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpds 2204 F pulseaudio /dev/snd/controlC1: jpds 2204 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 19:00:53 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=31caa47c-4bb8-4d50-b4a7-6c3d2dbf407d ro quiet splash ima_tcb ima_audit=1 ima_appraise_tcb rootflags=i_version ima_appraise=fix 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309070] [NEW] Possible Bug Translation in the clock menu.
Public bug reported: I just installed Ubuntu 14.04, and downloaded all the updates and then downloaded the packages in the following section translation for my language, so far so good without a single problem, but I noticed that the menu settings for the Date and Time were not aplicas translation . here is the link with pictures for better explanation of what happened. https://www.dropbox.com/sh/8w7jdxsui8f2joq/Rume3ILyAt ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: images for better explanation of what happened. https://bugs.launchpad.net/bugs/1309070/+attachment/4086268/+files/Imagens.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309070 Title: Possible Bug Translation in the clock menu. Status in “linux” package in Ubuntu: New Bug description: I just installed Ubuntu 14.04, and downloaded all the updates and then downloaded the packages in the following section translation for my language, so far so good without a single problem, but I noticed that the menu settings for the Date and Time were not aplicas translation . here is the link with pictures for better explanation of what happened. https://www.dropbox.com/sh/8w7jdxsui8f2joq/Rume3ILyAt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
This warning implies that SRAT may be wrong. And I just noticed that this may not be vanilla 4.2: [0.00] DMI: Xen HVM domU, BIOS 4.2.amazon 01/24/2014 Are we on a custom HVM BIOS? That's where memory is described to domain. Although NUMA issue may be somewhat orthogonal, it still may be worh looking at. Andrew, can you do this on booted guest: acpidump acpi.dat acpixtract -a acpi.dat iasl -d srat.dat and post here srat.dsl And again, seeing guest config file would be important. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309070] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1309070 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/1309070 Title: Possible Bug Translation in the clock menu. Status in “linux” package in Ubuntu: Incomplete Bug description: I just installed Ubuntu 14.04, and downloaded all the updates and then downloaded the packages in the following section translation for my language, so far so good without a single problem, but I noticed that the menu settings for the Date and Time were not aplicas translation . here is the link with pictures for better explanation of what happened. https://www.dropbox.com/sh/8w7jdxsui8f2joq/Rume3ILyAt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309112] [NEW] x120e does not resume from suspend
Public bug reported: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309112] 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/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309112] Re: x120e does not resume from suspend
This is regression for me from 13.10, but in addition to re-install I also replaced disk with an SSD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309112] Re: x120e does not resume from suspend
Attaching /var/crash/susres.2014-04-17_12:45:58.004375.crash ** Attachment added: susres.2014-04-17_12:45:58.004375.crash https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+attachment/4086387/+files/susres.2014-04-17_12%3A45%3A58.004375.crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present
Your reader firmware is newer than the one I have at http://pcsclite.alioth.debian.org/ccid/readers/AU9540.txt I confirm the reader firmware is bogus according to the output.txt you attached in #27. bNumDataRatesSupported: 138 IFD does not support GET_DATA_RATES request: Resource temporarily unavailable You should get a list of 138 values, not an error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307109 Title: Alcor Micro AU9540 keeps powering down when card is present Status in “linux” package in Ubuntu: Confirmed Status in “pcsc-lite” package in Ubuntu: Confirmed Bug description: I have smart card reader built-into this laptop, however, whenever I insert a card - it'll read it for a few seconds, then the USB connection to the reader gets powered down and thus the card disappears in the systems eyes. After a few seconds, it comes back and everything's happy. Then the cycle repeats again and again and again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpds 3933 F pulseaudio /dev/snd/controlC0: jpds 3933 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 6 18:37:24 2014 HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89 InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265885] Re: regression: SynPS/2 touchpad detected as DLL060A:00 pointer
What is the fix that was released? Do I still need to blacklist in 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/1265885 Title: regression: SynPS/2 touchpad detected as DLL060A:00 pointer Status in Release Notes for Ubuntu: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: This regression occurs somewhere between 3.11.0-14-generic (latest on saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier kernel, I actually get settings for setting up my touchpad in the unity interface. With the updated kernel, those options disappear. I only get one set of options both my mouse and my touchpad instead of each one independently. It means that I can't set the pointer speed differently or turn on natural scrolling for my touchpad. WORKAROUND: Execute at a terminal and then reboot your system: echo blacklist i2c_hid | sudo tee -a /etc/modprobe.d/blacklist.conf Release Notes Text Bug:1265885 On some Dell XPS13 systems the Synaptics touchpad is incorrectly recognised as a mouse. See the bug for possible workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1265885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300455] Re: linux: 3.2.0-61.92 -proposed tracker
No CVEs ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = 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/1300455 Title: linux: 3.2.0-61.92 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released 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-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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-61.92 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, 31. March 2014 21:30 UTC kernel-stable-Prepare-package-end:Tuesday, 01. April 2014 16:10 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. April 2014 16:10 UTC ppa-package-testing-start:Tuesday, 01. April 2014 17:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Certification-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:01 UTC kernel-stable-Regression-testing-end:Thursday, 10. April 2014 14:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300852] Re: linux: 2.6.32-58.120 -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/1300852 Title: linux: 2.6.32-58.120 -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: Fix Released 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 prepare-package-ports-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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-58.120 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, 01. April 2014 15:31 UTC kernel-stable-Prepare-package-end:Wednesday, 02. April 2014 00:05 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. April 2014 00:05 UTC ppa-package-testing-start:Wednesday, 02. April 2014 01:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:02 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:02 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:02 UTC kernel-stable-Certification-testing-start:Tuesday, 08. April 2014 07:02 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:03 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:03 UTC kernel-stable-Regression-testing-end:Thursday, 10. April 2014 16:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1285792] Re: Saucy update to v3.11.10.5 stable release
** Changed in: linux (Ubuntu) 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/1285792 Title: Saucy update to v3.11.10.5 stable release Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: Fix Released 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 v3.11.10.5 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 v3.11.10.5 stable release: Linux 3.11.10.5 EDAC: Correct workqueue setup path EDAC: Poll timeout cannot be zero, p2 drivers/edac/edac_mc_sysfs.c: poll timeout cannot be zero EDAC: Replace strict_strtol() with kstrtol() s390: fix kernel crash due to linkage stack instructions retrieving CIFS ACLs when mounted with SMB2 fails dropping session Add protocol specific operation for CIFS xattrs [CIFS] Fix SMB2 mounts so they don't try to set or get xattrs via cifs xen: Fix possible user space selector corruption xen/p2m: check MFN is in range before using the m2p table x86: mm: change tlb_flushall_shift for IvyBridge hwmon: (ntc_thermistor) Avoid math overflow IB/qib: Add missing serdes init sequence tick: Clear broadcast pending bit when switching to oneshot lockd: send correct lock when granting a delayed lock. vt: Fix secure clear screen x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off x86, smap: Don't enable SMAP if CONFIG_X86_SMAP is disabled compiler/gcc4: Make quirk for asm_volatile_goto() unconditional md/raid5: Fix CPU hotplug callback registration target: Fix free-after-use regression in PR unregister block: add cond_resched() to potentially long running ioctl discard loop ftrace/x86: Use breakpoints for converting function graph caller usb: option: blacklist ZTE MF667 net interface ring-buffer: Fix first commit on sub-buffer having non-zero delta xen: install xen/gntdev.h and xen/gntalloc.h genirq: Add missing irq_to_desc export for CONFIG_SPARSE_IRQ=n mm/memory-failure.c: move refcount only in !MF_COUNT_INCREASED mm: fix page leak at nfs_symlink() fs/file.c:fdtable: avoid triggering OOMs from alloc_fdmem iio: adis16400: Set timestamp as the last element in chan_spec iio: ak8975: Fix calculation formula for convert micro tesla to gauss unit block: Fix nr_vecs for inline integrity vectors Modpost: fixed USB alias generation for ranges including 0x9 and 0xA xen-blkfront: handle backend CLOSED without CLOSING staging: comedi: adv_pci1710: fix analog output readback value tty: n_gsm: Fix for modems with brk in modem status control raw: test against runtime value of max_raw_minors Drivers: hv: vmbus: Don't timeout during the initial connection with host Drivers: hv: vmbus: Specify the target CPU that should receive notification VME: Correct read/write alignment algorithm mei: don't unset read cb ptr on reset mei: clear write cb from waiting list on reset ALSA: hda - Fix mic capture on Sony VAIO Pro 11 ALSA: hda - Add a headset quirk for Dell XPS 13 drm/radeon: fix UVD IRQ support on 7xx drm/radeon: fix UVD IRQ support on SI time: Fix overflow when HZ is smaller than 60 mac80211: fix fragmentation code, particularly for encryption mac80211: release the channel in error path in start_ap nl80211: Reset split_start when netlink skb is exhausted mac80211: move roc cookie assignment earlier USB: ftdi_sio: add Tagsys RFID Reader IDs usb: qcserial: add Netgear Aircard 340U of: fix PCI bus match for PCIe slots md/raid1: restore ability for check and repair to fix read errors. usb-storage: enable multi-LUN scanning when needed usb-storage: add unusual-devs entry for BlackBerry 9000 usb-storage: restrict bcdDevice range for Super Top in Cypress ATACB usb: ftdi_sio: add Mindstorms EV3 console adapter spi: nuc900: Set SPI_LSB_FIRST for master-mode_bits if hw-pdata-lsb is true ath9k: Do not support PowerSave by default ar5523: fix usb id for Gigaset. ath9k_htc: Do not support PowerSave by default ath9k_htc: make -sta_rc_update atomic for most calls s390/dump: Fix dump memory detection iwlwifi: mvm: don't allow A band if SKU forbids it iwlwifi: mvm: BT Coex - disable BT when TXing probe request in scan power: max17040: Fix NULL pointer dereference when there is no platform_data block: __elv_next_request() shouldn't call into the elevator if bypassing iwlwifi: mvm: print the version of the firmware
[Kernel-packages] [Bug 1285777] Re: Quantal update to v3.5.7.31 stable release
** Changed in: linux (Ubuntu) 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/1285777 Title: Quantal update to v3.5.7.31 stable release Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Quantal: Fix Released 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 v3.5.7.31 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 v3.5.7.31 stable release: Linux 3.5.7.31 block: add cond_resched() to potentially long running ioctl discard loop s390: fix kernel crash due to linkage stack instructions dm sysfs: fix a module unload race EDAC: Correct workqueue setup path IB/qib: Add missing serdes init sequence lockd: send correct lock when granting a delayed lock. md/raid5: Fix CPU hotplug callback registration usb: option: blacklist ZTE MF667 net interface ring-buffer: Fix first commit on sub-buffer having non-zero delta genirq: Add missing irq_to_desc export for CONFIG_SPARSE_IRQ=n fs/file.c:fdtable: avoid triggering OOMs from alloc_fdmem iio: ak8975: Fix calculation formula for convert micro tesla to gauss unit Modpost: fixed USB alias generation for ranges including 0x9 and 0xA xen-blkfront: handle backend CLOSED without CLOSING staging: comedi: adv_pci1710: fix analog output readback value tty: n_gsm: Fix for modems with brk in modem status control raw: test against runtime value of max_raw_minors VME: Correct read/write alignment algorithm time: Fix overflow when HZ is smaller than 60 mac80211: fix fragmentation code, particularly for encryption USB: ftdi_sio: add Tagsys RFID Reader IDs usb-storage: enable multi-LUN scanning when needed usb-storage: add unusual-devs entry for BlackBerry 9000 usb-storage: restrict bcdDevice range for Super Top in Cypress ATACB usb: ftdi_sio: add Mindstorms EV3 console adapter spi: nuc900: Set SPI_LSB_FIRST for master-mode_bits if hw-pdata-lsb is true ath9k: Do not support PowerSave by default ath9k_htc: Do not support PowerSave by default s390/dump: Fix dump memory detection power: max17040: Fix NULL pointer dereference when there is no platform_data KVM: return an error code in kvm_vm_ioctl_register_coalesced_mmio() xhci: Fix resume issues on Renesas chips in Samsung laptops staging:iio:ad799x fix error_free_irq which was freeing an irq that may not have been requested printk: Fix scheduling-while-atomic problem in console_cpu_notify() ftrace: Have function graph only trace based on global_ops filters ftrace: Fix synchronization location disabling and freeing ftrace_ops ftrace: Synchronize setting function_trace_op with ftrace_trace_function ahci: add an observed PCI ID for Marvell 88se9172 SATA controller ahci: Use PCI_VENDOR_ID_MARVELL_EXT for 0x1b4b timekeeping: fix 32-bit overflow in get_monotonic_boottime timekeeping: Avoid possible deadlock from clock_was_set_delayed rtc-cmos: Add an alarm disable quirk sched/rt: Avoid updating RT entry timeout twice within one tick period sched: Unthrottle rt runqueues in __disable_runtime() sched,rt: fix isolated CPUs leaving root_task_group indefinitely throttled mm: __set_page_dirty uses spin_lock_irqsave instead of spin_lock_irq mm: __set_page_dirty_nobuffers() uses spin_lock_irqsave() instead of spin_lock_irq() mm/swap: fix race on swap_info reuse between swapoff and swapon x86, hweight: Fix BUG when booting with CONFIG_GCOV_PROFILE_ALL=y SELinux: Fix kernel BUG on empty security contexts. ALSA: hda - Improve loopback path lookups for AD1983 drm/mgag200: fix typo causing bw limits to be ignored on some chips [media] mxl111sf: Fix compile when CONFIG_DVB_USB_MXL111SF is unset [media] mxl111sf: Fix unintentional garbage stack read ALSA: usb-audio: Add missing kconfig dependecy crypto: s390 - fix des and des3_ede ctr concurrency issue crypto: s390 - fix des and des3_ede cbc concurrency issue crypto: s390 - fix concurrency issue in aes-ctr mode PCI: Enable ARI if dev and upstream bridge support it; disable otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544]
(In reply to comment #37) We've merged a number of patches that might affect this since the last comments. Please try recent drm-intel-nightly branch and report back. Thanks. No blank screen issues in my UX302LA either at boot, or when mode setting or when suspend/resuming. Tested via: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2014-04-11-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/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG 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/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300867] Re: linux-ti-omap4: 3.2.0-1445.64 -proposed tracker
No CVEs ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = 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/1300867 Title: linux-ti-omap4: 3.2.0-1445.64 -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: 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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled 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, 01. April 2014 16:03 UTC kernel-stable-master-bug:1300455 kernel-stable-Certification-testing-end:Wednesday, 02. April 2014 09:01 UTC kernel-stable-Prepare-package-end:Wednesday, 02. April 2014 18:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. April 2014 18:02 UTC ppa-package-testing-start:Wednesday, 02. April 2014 19:01 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:03 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:03 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:03 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:03 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544]
Created attachment 97254 kernel 20140411 dmesg w/ drm.debug=0xe Hello, so far it works on the UX302LG, i've attached the dmesg with drm.debug=0xe enabled, I see the screen flashing black after grub but it works thereafter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG 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/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544]
So one or some of our fixes has indeed fixed the bug. If anyone wants to reverse bisect from broken to first good, we'd be able to identify and backport the fix(es) to stable kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG 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/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544]
(In reply to comment #38) (In reply to comment #37) We've merged a number of patches that might affect this since the last comments. Please try recent drm-intel-nightly branch and report back. Thanks. No blank screen issues in my UX302LA either at boot, or when mode setting or when suspend/resuming. Tested via: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2014-04-11- trusty/ Will test report for UX302LG asap. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG 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/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544] Re: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7
** Changed in: linux 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/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG 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/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300894] Re: linux: 3.5.0-49.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/1300894 Title: linux: 3.5.0-49.73 -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: In Progress 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 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: Fix Released 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 Quantal: New Bug description: This bug is for tracking the 3.5.0-49.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:Tuesday, 01. April 2014 17:17 UTC kernel-stable-Certification-testing-end:Tuesday, 01. April 2014 18:03 UTC kernel-stable-Prepare-package-end:Wednesday, 02. April 2014 00:17 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. April 2014 00:17 UTC ppa-package-testing-start:Wednesday, 02. April 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:05 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:05 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:05 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300928] Re: linux: 3.11.0-20.34 -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/1300928 Title: linux: 3.11.0-20.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: Confirmed Bug description: This bug is for tracking the 3.11.0-20.34 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, 01. April 2014 18:18 UTC kernel-stable-Prepare-package-end:Wednesday, 02. April 2014 17:09 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. April 2014 17:09 UTC ppa-package-testing-start:Wednesday, 02. April 2014 18:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:05 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Certification-testing-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:06 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:06 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1300928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290449] Re: linux: 3.5.0-48.72 -proposed tracker
*** This bug is a duplicate of bug 1290459 *** https://bugs.launchpad.net/bugs/1290459 ** This bug has been marked a duplicate of bug 1290459 linux: 3.5.0-48.72 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1290449 Title: linux: 3.5.0-48.72 -proposed tracker Status in Kernel SRU Workflow: Invalid 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: New Status in Kernel SRU Workflow prepare-package-signed 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 verification-testing series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Quantal: New Bug description: This bug is for tracking the 3.5.0-48.72 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, 10. March 2014 16:51 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 10. March 2014 16:51 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1290449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301073] Re: linux-ti-omap4: 3.5.0-241.57 -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-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1301073 Title: linux-ti-omap4: 3.5.0-241.57 -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: 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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-ti-omap4” source package in Saucy: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 02. April 2014 00:07 UTC kernel-stable-master-bug:1300894 kernel-stable-Certification-testing-end:Thursday, 03. April 2014 17:04 UTC kernel-stable-Prepare-package-end:Friday, 04. April 2014 16:05 UTC kernel-stable-Promote-to-proposed-start:Friday, 04. April 2014 16:05 UTC ppa-package-testing-start:Friday, 04. April 2014 17:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 08. April 2014 05:06 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 08. April 2014 07:09 UTC kernel-stable-Security-signoff-start:Tuesday, 08. April 2014 07:09 UTC kernel-stable-Verification-testing-start:Tuesday, 08. April 2014 07:09 UTC kernel-stable-Regression-testing-start:Tuesday, 08. April 2014 07:09 UTC kernel-stable-Regression-testing-end:Wednesday, 09. April 2014 04:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1301073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1271441] Re: CVE-2014-1438
** No longer affects: linux-lts-backport-maverick (Ubuntu) ** No longer affects: linux-lts-backport-natty (Ubuntu) -- 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/1271441 Title: CVE-2014-1438 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: 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-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 Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: New Status in “linux-lts-backport-natty” source package in Quantal: New Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: New Status in “linux-lts-backport-natty” source package in Raring: New Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The restore_fpu_checking function in arch/x86/include/asm/fpu- internal.h in the Linux kernel before 3.12.8 on the AMD K7 and K8 platforms does not clear pending exceptions before proceeding to an EMMS instruction, which allows local users to cause a denial of service (task kill) or possibly gain privileges via a crafted application. Break-Fix: - 26bef1318adc1b3a530ecc807ef99346db2aa8b0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1309112] Re: x120e does not resume from suspend
Scott - please attach the output of 'sudo dmidecode' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-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/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1295285] Re: [Asus UX31A] suspend/resume failure
Same here, everything was ok with 12.04 (all kernels). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295285 Title: [Asus UX31A] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Wifi or network stack stop working, after notebook resumed from suspend. Toggle networking by network applet nothing change. Ubuntu 14.04 Asus zenbook prime ux31a. 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ur 1978 F pulseaudio CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Thu Mar 20 19:32:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4f2dae9f-e237-4163-86d5-aecc46159037 InstallationDate: Installed on 2014-03-18 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. UX31A ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=5349e06c-59f5-4efa-aa59-87fd57fc0464 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-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux StagingDrivers: rts5139 Title: [ASUSTeK COMPUTER INC. UX31A] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31A.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31A 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.:bvrUX31A.219:bd06/14/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX31A 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/1295285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307105] Re: Kernel install fails due PAE checks
Jii wrote: No, I was not booting with forcepae option. After installer, the system was fully operational so I didn't know there was need to add it. How did you boot the installer? Normally syslinux will boot the kernel in 16-bit mode and you would get the forcepae error message. Andy Whitcroft wrote: If the kernel is booted, then forcepae must have been supplied This is not always true. A PAE kernel will boot on a PAE capable Pentium M without forcepae if the boot loader skips the 16-bit entry code of the Linux kernel. This is the case with a default install of grub on Ubuntu - which is why many Pentium M users who had installed Ubuntu before the switch to PAE-only didn't have any problems when they got upgraded (but later ran into problems when the check for pae in /proc/cpuinfo was added to the linux-image preinst). You can force grub to boot the kernel in 16-bit mode by using the linux16 and initrd16 commands instead of plain linux and initrd; using the 16-bit boot path seems to be preferred by upstream since then the kernel CPU checks get run, but it is probably too late for Ubuntu to switch. Daniel Letzeisen wrote: Should the ubiquity installer do a special check to see if it's been s tarted with forcepae Could do, the check is not hard (running pae kernel and (forcepae or no pae in cpuinfo flags). It would be nice for the user to not have to bother with forcepae; I would have preferred to enable it automatically rather than having the kernel parameter, but the x86 maintainers thought that a user should have to consent to operating their CPU out of spec. If Ubuntu were happy with assuming consent, then you could just add it to the default pae- kernel boot parameters and make the whole thing invisible to the user. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks Status in “linux” package in Ubuntu: Triaged Bug description: [TRIAGE NOTE] When a user boots Ubuntu Live/Install media with 'forcepae' option, the option should automatically be added to /etc/default/grub, or kernel upgrades will refuse to install when they do not see pae capability in cpuinfo. [ORIGINAL REPORT] On Thinkpad T42 with Pentium M processor linux image upgrade fails with message This kernel does not support a non-PAE CPU.. System was installed from ubuntu-14.04-beta2-desktop-i386.iso with forcepae kernel option. After install, system works, but cannot be upgraded to laters kernel. root@t42:/boot# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic but it is not installed linux-image-generic : Depends: linux-image-3.13.0-24-generic but it is not installed E: Unmet dependencies. Try using -f. root@t42:/boot# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-24-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-24-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.6 MB of archives. After this operation, 32.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 196089 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1079859] Re: CVE-2012-4444
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1079859 Title: CVE-2012- Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-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: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The ip6_frag_queue function in net/ipv6/reassembly.c in the Linux kernel before 2.6.36 allows remote attackers to bypass intended network restrictions via overlapping IPv6 fragments. Break-Fix: - 70789d7052239992824628db8133de08dc78e593 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079859/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1071314] Re: CVE-2012-4508
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1071314 Title: CVE-2012-4508 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: Race condition in fs/ext4/extents.c in the Linux kernel before 3.4.16 allows local users to obtain sensitive information from a deleted file by reading an extent that was not properly marked as uninitialized. Break-Fix: - dee1f973ca341c266229faa5a1a5bb268bed3531 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1143817] Re: CVE-2013-1774
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1143817 Title: CVE-2013-1774 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The chase_port function in drivers/usb/serial/io_ti.c in the Linux kernel before 3.7.4 allows local users to cause a denial of service (NULL pointer dereference and system crash) via an attempted /dev/ttyUSB read or write operation on a disconnected Edgeport USB serial converter.
[Kernel-packages] [Bug 1134513] Re: CVE-2013-1772
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1134513 Title: CVE-2013-1772 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The log_prefix function in kernel/printk.c in the Linux kernel 3.x before 3.4.33 does not properly remove a prefix string from a syslog header, which allows local users to cause a denial of service (buffer overflow and system crash) by leveraging /dev/kmsg write access and triggering a call_console_drivers function call. Break-Fix: 162a7e7500f9664636e649ba59defe541b7c2c60
[Kernel-packages] [Bug 1134503] Re: CVE-2013-0349
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1134503 Title: CVE-2013-0349 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux”
[Kernel-packages] [Bug 1131340] Re: CVE-2013-0313
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1131340 Title: CVE-2013-0313 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The evm_update_evmxattr function in
[Kernel-packages] [Bug 1132896] Re: CVE-2013-1763
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1132896 Title: CVE-2013-1763 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: Array index error in the __sock_diag_rcv_msg function in net/core/sock_diag.c in the Linux kernel before 3.7.10 allows local
[Kernel-packages] [Bug 1143796] Re: CVE-2013-0228
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1143796 Title: CVE-2013-0228 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux”
[Kernel-packages] [Bug 1134523] Re: CVE-2013-1773
** Changed in: linux-armadaxp (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1134523 Title: CVE-2013-1773 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released Status in “linux” source package in Precise: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Won't Fix Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: Buffer
[Kernel-packages] [Bug 1117325] Re: CVE-2013-0216
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1117325 Title: CVE-2013-0216 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The Xen netback functionality in the Linux kernel before 3.7.8 allows guest OS users to cause a denial of
[Kernel-packages] [Bug 1130943] Re: CVE-2013-0309
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1130943 Title: CVE-2013-0309 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: arch/x86/include/asm/pgtable.h in the Linux kernel before 3.6.2, when transparent huge pages are used, does not properly support PROT_NONE memory regions, which allows local users to cause a denial of service (system crash) via a crafted application. Break-Fix: - 027ef6c87853b0a9df53175063028edb4950d476 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1130950] Re: CVE-2013-0310
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1130950 Title: CVE-2013-0310 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The cipso_v4_validate function in net/ipv4/cipso_ipv4.c in the Linux kernel before 3.4.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via an IPOPT_CIPSO IP_OPTIONS setsockopt system call. Break-Fix: - 89d7ae34cdda4195809a5a987f697a517a2a3177 To manage notifications about this bug go
[Kernel-packages] [Bug 1129184] Re: CVE-2013-0290
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1129184 Title: CVE-2013-0290 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The __skb_recv_datagram function in net/core/datagram.c in the Linux kernel before 3.8 does not properly handle the MSG_PEEK flag with
[Kernel-packages] [Bug 1123049] Re: CVE-2013-0268
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1123049 Title: CVE-2013-0268 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux”
[Kernel-packages] [Bug 1117331] Re: CVE-2013-0217
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1117331 Title: CVE-2013-0217 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: Memory leak in drivers/net/xen-netback/netback.c in the Xen netback functionality in the Linux kernel
[Kernel-packages] [Bug 1102374] Re: CVE-2013-0190
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1102374 Title: CVE-2013-0190 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” 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 Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy:
[Kernel-packages] [Bug 1131331] Re: CVE-2012-4542
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1131331 Title: CVE-2012-4542 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty:
[Kernel-packages] [Bug 1068888] Re: CVE-2012-4530
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/106 Title: CVE-2012-4530 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Bug description: The load_script function in fs/binfmt_script.c in the Linux kernel before 3.7.2 does not properly handle recursion, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: bf2a9a39639b8b51377905397a5005f444e9a892 d740269867021faf4ce38a449353d2b986c34a67 Break-Fix:
[Kernel-packages] [Bug 1156761] Re: CVE-2012-6547
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156761 Title: CVE-2012-6547 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The __tun_chr_ioctl function in drivers/net/tun.c in the Linux kernel before 3.6 does not initialize a certain structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: - a117dacde0288f3ec60b6e5bcedae8fa37ee0dfc To manage notifications about this bug go to:
[Kernel-packages] [Bug 1151527] Re: CVE-2013-1819
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1151527 Title: CVE-2013-1819 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Bug description: The _xfs_buf_find function in fs/xfs/xfs_buf.c in the Linux kernel before 3.7.6 does not validate block numbers, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging the ability to mount an XFS filesystem containing a metadata inode with an invalid extent map. Break-Fix:
[Kernel-packages] [Bug 1156768] Re: CVE-2012-6548
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156768 Title: CVE-2012-6548 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The udf_encode_fh function in fs/udf/namei.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. Break-Fix: - 0143fc5e9f6f5aad4764801015bc8d4b4a278200 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1156790] Re: CVE-2013-2546
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156790 Title: CVE-2013-2546 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The report API in the crypto user configuration API in the Linux kernel through 3.8.2 uses an incorrect C library
[Kernel-packages] [Bug 1155018] Re: CVE-2012-6138
** Changed in: linux (Ubuntu Raring) Status: New = Won't Fix ** Changed in: linux-armadaxp (Ubuntu Raring) Status: New = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: New = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1155018 Title: CVE-2012-6138 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: New 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Won't Fix Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Won't Fix Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: Linux kernel: various info leaks To manage notifications about this
[Kernel-packages] [Bug 1156728] Re: CVE-2012-6539
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156728 Title: CVE-2012-6539 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The dev_ifconf function in net/socket.c in the Linux kernel before 3.6 does not initialize a certain structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: - 43da5f2e0d0c69ded3d51907d9552310a6b545e8 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1155029] Re: CVE-2013-1827
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1155029 Title: CVE-2013-1827 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: net/dccp/ccid.h in the Linux kernel before 3.5.4 allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by leveraging the CAP_NET_ADMIN capability for a certain (1) sender or (2) receiver getsockopt call. Break-Fix: - 276bdb82dedb290511467a5a4fdbe9f0b52dce6f To manage notifications about this bug go to:
[Kernel-packages] [Bug 1153811] Re: CVE-2013-0913
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1153811 Title: CVE-2013-0913 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: Integer overflow in drivers/gpu/drm/i915/i915_gem_execbuffer.c in the i915 driver in the Direct Rendering Manager (DRM) subsystem in the Linux kernel through 3.8.3, as used in Google Chrome OS before 25.0.1364.173 and other products, allows local users to cause a denial of service (heap-based
[Kernel-packages] [Bug 1156774] Re: CVE-2012-6549
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156774 Title: CVE-2012-6549 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The isofs_export_encode_fh function in fs/isofs/export.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. Break-Fix: - fe685aabf7c8c9f138e5ea900954d295bf229175 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1156712] Re: CVE-2012-6536
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156712 Title: CVE-2012-6536 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: net/xfrm/xfrm_user.c in the Linux kernel before 3.6 does not verify that the actual Netlink message length is consistent with a certain header field, which allows local users to obtain sensitive information from kernel heap memory by leveraging the CAP_NET_ADMIN capability and providing a (1) new or (2) updated state. Break-Fix: d8647b79c3b7e223ac051439d165bc8e7bbb832f
[Kernel-packages] [Bug 1155026] Re: CVE-2013-1826
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1155026 Title: CVE-2013-1826 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The xfrm_state_netlink function in net/xfrm/xfrm_user.c in the Linux kernel before 3.5.7 does not properly handle error conditions in dump_one_state function calls, which allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by leveraging the CAP_NET_ADMIN capability. Break-Fix: -
[Kernel-packages] [Bug 1156750] Re: CVE-2012-6543
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156750 Title: CVE-2012-6543 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” 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 Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The l2tp_ip6_getname function in net/l2tp/l2tp_ip6.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: a32e0eec7042b21ccb52896cf715e3e2641fed93 04d4fbca1017c11381e7d82acea21dd741e748bc To manage notifications about this bug go to:
[Kernel-packages] [Bug 1156738] Re: CVE-2012-6541
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156738 Title: CVE-2012-6541 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The ccid3_hc_tx_getsockopt function in net/dccp/ccids/ccid3.c in the Linux kernel before 3.6 does not initialize a certain structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: 67b67e365f07d6dc70f3bb266af3268bac0a4836 7b07f8eb75aa3097cdfd4f6eac3da49db787381d To manage notifications about this bug go to:
[Kernel-packages] [Bug 1156795] Re: CVE-2013-2547
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156795 Title: CVE-2013-2547 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The crypto_report_one function in crypto/crypto_user.c in the report API in the crypto user configuration API in the
[Kernel-packages] [Bug 1156778] Re: CVE-2013-1858
** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Won't Fix ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156778 Title: CVE-2013-1858 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” 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 Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux” source package in Raring: Won't Fix Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The clone system-call implementation in the Linux kernel before 3.8.3
[Kernel-packages] [Bug 1156759] Re: CVE-2012-6546
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156759 Title: CVE-2012-6546 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The ATM implementation in the Linux kernel before 3.6 does not initialize certain structures, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: - 3c0c5cfdcd4d69ffc4b9c0907cec99039f30a50a Break-Fix: - e862f1a9b7df4e8196ebec45ac62295138aa3fc2 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1156716] Re: CVE-2012-6537
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156716 Title: CVE-2012-6537 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: net/xfrm/xfrm_user.c in the Linux kernel before 3.6 does not initialize certain structures, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability. Break-Fix: - 1f86840f897717f86d523a13e99a447e6a5d2fa5 Break-Fix: - 7b789836f434c87168eab067cfbed1ec4783dffd Break-Fix: -
[Kernel-packages] [Bug 1152791] Re: CVE-2013-1828
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1152791 Title: CVE-2013-1828 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” 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 Oneiric: Invalid Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” 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 Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Hardy: Invalid Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The sctp_getsockopt_assoc_stats function in net/sctp/socket.c in the Linux kernel before 3.8.4 does not validate a size value before proceeding
[Kernel-packages] [Bug 1156743] Re: CVE-2012-6542
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156743 Title: CVE-2012-6542 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The llc_ui_getname function in net/llc/af_llc.c in the Linux kernel before 3.6 has an incorrect return value in certain circumstances, which allows local users to obtain sensitive information from kernel stack memory via a crafted application that leverages an uninitialized pointer argument. Break-Fix: - 3592aaeb80290bda0f2cf0b5456c97bfc638b192 To manage notifications
[Kernel-packages] [Bug 1156732] Re: CVE-2012-6540
** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156732 Title: CVE-2012-6540 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Bug description: The do_ip_vs_get_ctl function in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 3.6 does not initialize a certain structure for IP_VS_SO_GET_TIMEOUT commands, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. Break-Fix: - 2d8a041b7bfe1097af21441cb77d6af95f4f4680 To manage notifications about this bug
