[Kernel-packages] [Bug 1514853] Re: Trusty update to 3.13.11-ckt29 stable release

2015-11-10 Thread Luis Henriques
** 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/1514853

Title:
  Trusty update to 3.13.11-ckt29 stable release

Status in linux package in Ubuntu:
  Invalid
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 either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.13.11-ckt29 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.13.11-ckt29 stable release:

  sctp: donot reset the overall_error_count in SHUTDOWN_RECEIVE state
  KEYS: Fix race between key destruction and finding a keyring by name
  KEYS: Fix crash when attempt to garbage collect an uninstantiated keyring
  KEYS: Don't permit request_key() to construct a new keyring
  [stable-only] net: add length argument to skb_copy_and_csum_datagram_iovec
  spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
  spi: Fix documentation of spi_alloc_master()
  ARM: 8429/1: disable GCC SRA optimization
  powerpc/MSI: Fix race condition in tearing down MSI interrupts
  CIFS: fix type confusion in copy offload ioctl
  hwmon: (nct6775) Swap STEP_UP_TIME and STEP_DOWN_TIME registers for most chips
  USB: option: add ZTE PIDs
  x86/apic: Serialize LVTT and TSC_DEADLINE writes
  Btrfs: fix read corruption of compressed and shared extents
  btrfs: skip waiting on ordered range for special files
  arm64: head.S: initialise mdcr_el2 in el2_setup
  kvm: fix zero length mmio searching
  iser-target: remove command with state ISTATE_REMOVE
  ARM: fix Thumb2 signal handling when ARMv6 is enabled
  powerpc/mm: Recompute hash value after a failed update
  x86/platform: Fix Geode LX timekeeping in the generic x86 build
  arm64: compat: fix vfp save/restore across signal handlers in big-endian
  arm64: errata: add module build workaround for erratum #843419
  arm64: KVM: Disable virtual timer even if the guest is not using it
  arm: KVM: Disable virtual timer even if the guest is not using it
  KVM: x86: trap AMD MSRs for the TSeg base and mask
  usb: Use the USB_SS_MULT() macro to get the burst multiplier.
  xhci: give command abortion one more chance before killing xhci
  usb: xhci: Clear XHCI_STATE_DYING on start
  xhci: change xhci 1.0 only restrictions to support xhci 1.1
  disabling oplocks/leases via module parm enable_oplocks broken for SMB3
  cifs: use server timestamp for ntlmv2 authentication
  x86/paravirt: Replace the paravirt nop with a bona fide empty function
  x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
  ASoC: pxa: pxa2xx-ac97: fix dma requestor lines
  drm/qxl: only report first monitor as connected if we have no state
  PCI: Fix devfn for VPD access through function 0
  PCI: Use function 0 VPD for identical functions, regular VPD for others
  perf header: Fixup reading of HEADER_NRCPUS feature
  netfilter: nft_compat: skip family comparison in case of NFPROTO_UNSPEC
  ASoC: fix broken pxa SoC support
  ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets
  vxlan: set needed headroom correctly
  usbnet: Get EVENT_NO_RUNTIME_PM bit before it is cleared
  net/ipv6: Correct PIM6 mrt_lock handling
  netlink, mmap: transform mmap skb into full skb on taps
  openvswitch: Zero flows on allocation.
  fib_rules: fix fib rule dumps across multiple skbs
  Btrfs: update fix for read corruption of compressed and shared extents
  Linux 3.13.11-ckt29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514853/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514821] Re: SD card reader on Dell E7250 doesn't work in Ubuntu 15.10

2015-11-10 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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'.

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/v4.3-wily/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514821

Title:
  SD card reader on Dell E7250 doesn't work in Ubuntu 15.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My experience with the SD card is the same as experienced by Simon James 
Greer in bug #1509119
  Christopher M. Penalver notified me that i would be ok to subscribe him to 
this report.

  > lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  > apt-cache policy pkgname
  N: Unable to locate package pkgname
  tud254222 ~$ apt-cache policy linux-image-4.2.0-18-generic
  linux-image-4.2.0-18-generic:
Installed: 4.2.0-18.22
Candidate: 4.2.0-18.22
Version table:
   *** 4.2.0-18.22 0
  500 http://nl.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  NOTE: i booted the machine with the SD card removed. Logged into
  Unity, i insterted the SD card and i was expecting to see the SD card
  mounted in the Unity actionbar, like in 15.04. Unfortunately i saw the
  error messages popping up in dmesg:

   sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning 
procedure, falling back to fixed sampling clock
   mmc0: tuning execution failed
   mmc0: error -5 whilst initialising SD card

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  feverdij   1864 F pulseaudio
   /dev/snd/controlC0:  feverdij   1864 F pulseaudio
  Date: Tue Nov 10 13:56:18 2015
  HibernationDevice: RESUME=UUID=a507736b-2856-48bd-ae57-a3a1a678c150
  InstallationDate: Installed on 2015-06-19 (144 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7250
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=fe9cd698-4d8c-4ea1-9cce-af132d859b83 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-02 (8 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.asset.tag: TUD254222
  dmi.board.name: 0TVD2T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: TUD254222
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0TVD2T:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7250
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514821/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514861] Re: mlx5 EN driver wrongly enables sets VLAN filtering under promiscuous mode

2015-11-10 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514861

Title:
   mlx5 EN driver wrongly enables sets VLAN filtering under promiscuous
  mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Description of problem: The mlx5 Ethernet driver doesn't allow packets
  marked with all possible VLAN tags to be accepted under promiscuous
  mode. This is wrong and disallows Open-Stack to properly function in
  Para-Virtual configuration.

  
  How reproducible: 

   just put the NIC to promiscuous mode and send packet from another
  node tagged any vlan which was not previously configured on the NIC
  vlan filter, it will not be accepted.

  
  Actual results:
  ARP packets sent on vlan 52 packets are dropped 

  Expected results:
  packets should received 

  Host info:
  #uname -a
  Linux dev-h-vrt-006 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 15.10
  Release:15.10
  Codename:   wily

  
  The following upstream commit fix it:

  commit c07543431e9f3d126d083808efa0e76461d8833b
  Author: Achiad Shochat 
  Date:   Thu Oct 8 15:26:18 2015 +0300

  net/mlx5e: Disable VLAN filter in promiscuous mode

  When the device was set to promiscuous mode, we didn't disable
  VLAN filtering, which is wrong behaviour, fix that.

  Now when the device is set to promiscuous mode RX packets
  sent over any VLAN (or no VLAN tag at all) will be accepted.

  Signed-off-by: Achiad Shochat 
  Signed-off-by: Or Gerlitz 
  Signed-off-by: David S. Miller 

  I backported it to Ubuntu 15.10 (please see the attached patch). This
  issue need to be fix also in Ubuntu 14.04.4 not only 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514861/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514889] [NEW] Wily update to v4.2.6 stable release

2015-11-10 Thread Tim Gardner
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 v4.2.6 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 v4.2.6 stable release:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Wily)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Wily)
   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/1514889

Title:
  Wily update to v4.2.6 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  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 v4.2.6 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 v4.2.6 stable release:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514889/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace

2015-11-10 Thread Serge Hallyn
@oleg,

yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1480411

Title:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace.

  If overlayfs is mounted as follows,

     mount -n -t overlay overlay -o
  lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt

  and if lowerdir contains lowerdir/foo/bar.txt, then,

     rm -r mntpt/foo

  fails with error message,

     "rm: cannot remove ‘mntpt/foo’: Operation not permitted"

  strace shows,

  unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM
  (Operation not permitted)

  OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid
  kernel (3.19).

  The bug does not occur on ubuntu 14.04.2 with the default linux-
  generic 3.13 kernel.

  The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch,
  "overlayfs: allow unprivileged mounts" is added.  (The patch is at,
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea)

  The bug occurs regardless of whether the filesystem underlying
  overlayfs is tmpfs or ext4.

  The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a
  virtual machine (qemu-system-x86_64).  The host is ubuntu 14.04.2 with
  the default 3.13 kernel.

  A script which reproduces the bug is attached and is also available at
  http://paste.ubuntu.com/11974137/

  Hardware: intel core2 duo processor in a macbook-4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler

2015-11-10 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Wily)
   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/1463584

Title:
  [Hyper-V] Add support for VMBus panic notifier handler

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Please take these patches to our Hyper-V VMBus driver to enable kernel
  crash notification:

  Drivers: hv: vmbus: Add support for VMBus panic notifier handler
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

  Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13

  
  In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514907] [NEW] package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-11-10 Thread Bob Guilfoyle
Public bug reported:

Following prompting to submit info. Haven't a clue what even happened.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-68-generic 3.13.0-68.111
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bguilfoyle   2780 F pulseaudio
Date: Tue Nov 10 08:05:53 2015
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
HibernationDevice: RESUME=UUID=2c98cf1a-2238-454e-b55e-98ef172d4bd6
InstallationDate: Installed on 2013-11-11 (728 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: Dell Inc. OptiPlex 990
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/xubuntu-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to trusty on 2014-07-09 (489 days ago)
WifiSyslog:
 
dmi.bios.date: 12/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/30/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514907

Title:
  package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Following prompting to submit info. Haven't a clue what even happened.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-68-generic 3.13.0-68.111
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bguilfoyle   2780 F pulseaudio
  Date: Tue Nov 10 08:05:53 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=2c98cf1a-2238-454e-b55e-98ef172d4bd6
  InstallationDate: Installed on 2013-11-11 (728 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/xubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-09 (489 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/30/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514907/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1512997] Re: Support Edge Gateway's WIFI LED

2015-11-10 Thread Luis Henriques
** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512997

Title:
  Support Edge Gateway's WIFI LED

Status in HWE Next:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no
  code for controlling LED in mwifiex). It is requested to be ON and OFF
  when the radio is on and off accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1512997/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514861] Re: mlx5 EN driver wrongly enables sets VLAN filtering under promiscuous mode

2015-11-10 Thread Tim Gardner
Talat - I assume you have had positive test results with your backport
patch ?

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu Wily)
   Status: New => In Progress

** Changed in: linux (Ubuntu Wily)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514861

Title:
   mlx5 EN driver wrongly enables sets VLAN filtering under promiscuous
  mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Description of problem: The mlx5 Ethernet driver doesn't allow packets
  marked with all possible VLAN tags to be accepted under promiscuous
  mode. This is wrong and disallows Open-Stack to properly function in
  Para-Virtual configuration.

  
  How reproducible: 

   just put the NIC to promiscuous mode and send packet from another
  node tagged any vlan which was not previously configured on the NIC
  vlan filter, it will not be accepted.

  
  Actual results:
  ARP packets sent on vlan 52 packets are dropped 

  Expected results:
  packets should received 

  Host info:
  #uname -a
  Linux dev-h-vrt-006 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 15.10
  Release:15.10
  Codename:   wily

  
  The following upstream commit fix it:

  commit c07543431e9f3d126d083808efa0e76461d8833b
  Author: Achiad Shochat 
  Date:   Thu Oct 8 15:26:18 2015 +0300

  net/mlx5e: Disable VLAN filter in promiscuous mode

  When the device was set to promiscuous mode, we didn't disable
  VLAN filtering, which is wrong behaviour, fix that.

  Now when the device is set to promiscuous mode RX packets
  sent over any VLAN (or no VLAN tag at all) will be accepted.

  Signed-off-by: Achiad Shochat 
  Signed-off-by: Or Gerlitz 
  Signed-off-by: David S. Miller 

  I backported it to Ubuntu 15.10 (please see the attached patch). This
  issue need to be fix also in Ubuntu 14.04.4 not only 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514861/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV

2015-11-10 Thread Chris J Arges
** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1508767

Title:
  IBM POWER8 unhandled signal 11 / SEGV

Status in Ubuntu Cloud Archive:
  New
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  We have a few IBM POWER8 servers which we're currently using as
  OpenStack nova compute nodes. It seems we're regularly running into
  issues where processes are segfaulting:

  | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' 
/var/log/syslog.5.gz
  | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: 
unhandled signal 11 at 88f90100 nip 100ba0d8 lr 
101ad860 code 30001
  | Oct 16 23:31:38 gligar kernel: [88351.566909] init: 
neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal
  | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled 
signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 
30001
  | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: 
unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 
1014b544 code 30001
  | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: 
unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 
100b73e4 code 30001
  | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: 
unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 
100aa794 code 30001
  | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: 
unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 
10060384 code 30001
  | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: 
unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 
3fffaef811a0 code 30001
  | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: 
unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 
10060384 code 30001
  | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: 
unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 
3fff9a84c42c code 30001
  | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: 
unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 
100b74e8 code 30001
  | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: 
unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 
100b7c38 code 30001
  | Oct 16 23:35:23 gligar kernel: [88576.804961] init: 
neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal
  | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: 
unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 
10151080 code 30001
  | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled 
signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 
30001
  | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main 
process (4331) killed by SEGV signal
  | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: 
unhandled signal 11 at 02f8 nip 101abeac lr 
100a8738 code 30001
  | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled 
signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 
30001

  
  | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' 
/var/log/syslog.7.gz
  | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled 
signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 
30001
  | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: 
unhandled signal 11 at 08680f00 nip 1004bbf8 lr 
10028de4 code 30001
  | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: 
unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 
100b74e8 code 30001
  | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: 
unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 
100e6900 code 30001
  | Oct 14 22:21:37 floette kernel: [168893.597834] init: 
neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal
  | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: 
unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 
100ab42c code 30001
  | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: 
unhandled signal 11 at 08c90df31820 nip 101ac260 lr 
101ad92c code 30001
  | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: 
unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr 
100d9cac code 

[Kernel-packages] [Bug 1505241] Re: Phone does not suspend

2015-11-10 Thread Simon Fels
** Changed in: bluez (Ubuntu)
   Importance: Undecided => High

-- 
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/1505241

Title:
  Phone does not suspend

Status in Canonical System Image:
  Invalid
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar 
behavior
  According to the logs they are not able to suspend due to active wakeup 
sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads

2015-11-10 Thread TJ
As I suspected the cause was in hardware, and specifically due to the
motherboard using Master Write 0-wait state access, which meant the
device had not completed mapping its registers into the PCI Config
address space when the kernel probed for the Vendor ID.

User applied my recommended BIOS configuration changes and the device is
now correctly identified.

The solution is to alter the BIOS settings. In this case the "LDT and
PCI Bus Control", and set "PCI1/PCI2 Master 0 WS Write" to Disabled to
enforce 1 wait state. The device also had to be in ports PC1 or PCI2
(nearest the AGP slot) on this Abit KV8-MAX3 mobo.

** Summary changed:

- PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads
+ PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait writes

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1513477

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  writes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514911] [NEW] Trusty update to 3.16.7-ckt19 stable release

2015-11-10 Thread Luis Henriques
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 3.16.7-ckt19 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://kernel.ubuntu.com/ubuntu/linux.git

TEST CASE: TBD

   The following patches are in the 3.16.7-ckt19 stable release:

ARM: 8429/1: disable GCC SRA optimization
CIFS: fix type confusion in copy offload ioctl
hwmon: (nct6775) Swap STEP_UP_TIME and STEP_DOWN_TIME registers for most chips
x86/apic: Serialize LVTT and TSC_DEADLINE writes
arm64: head.S: initialise mdcr_el2 in el2_setup
kvm: don't try to register to KVM_FAST_MMIO_BUS for non mmio eventfd
kvm: factor out core eventfd assign/deassign logic
kvm: fix double free for fast mmio eventfd
kvm: fix zero length mmio searching
ARM: fix Thumb2 signal handling when ARMv6 is enabled
powerpc/boot: Specify ABI v2 when building an LE boot wrapper
powerpc/mm: Recompute hash value after a failed update
x86/platform: Fix Geode LX timekeeping in the generic x86 build
arm64: compat: fix vfp save/restore across signal handlers in big-endian
arm64: errata: add module build workaround for erratum #843419
arm64: KVM: Disable virtual timer even if the guest is not using it
arm: KVM: Disable virtual timer even if the guest is not using it
hp-wmi: Add missing __init annotations to initialization code
hp-wmi: limit hotkey enable
zram: fix possible use after free in zcomp_create()
perf header: Fixup reading of HEADER_NRCPUS feature
spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
spi: Fix documentation of spi_alloc_master()
USB: option: add ZTE PIDs
drm/vmwgfx: Fix up user_dmabuf refcounting
ARM: dts: omap3-beagle: make i2c3, ddc and tfp410 gpio work again
Btrfs: fix read corruption of compressed and shared extents
btrfs: skip waiting on ordered range for special files
usb: chipidea: udc: using the correct stall implementation
net: mvneta: fix DMA buffer unmapping in mvneta_rx()
iser-target: remove command with state ISTATE_REMOVE
staging: ion: fix corruption of ion_import_dma_buf
KVM: x86: trap AMD MSRs for the TSeg base and mask
usb: Use the USB_SS_MULT() macro to get the burst multiplier.
xhci: give command abortion one more chance before killing xhci
usb: xhci: Clear XHCI_STATE_DYING on start
usb: xhci: Allow usb_add/remove_hcd() to be called repeatedly
xhci: change xhci 1.0 only restrictions to support xhci 1.1
xhci-mem: Use setup_timer
xhci: init command timeout timer earlier to avoid deleting it uninitialized
spi: xtensa-xtfpga: fix register endianness
disabling oplocks/leases via module parm enable_oplocks broken for SMB3
cifs: use server timestamp for ntlmv2 authentication
x86/paravirt: Replace the paravirt nop with a bona fide empty function
x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
ASoC: pxa: pxa2xx-ac97: fix dma requestor lines
ocfs2/dlm: fix deadlock when dispatch assert master
drm/i915/bios: handle MIPI Sequence Block v3+ gracefully
drm/qxl: only report first monitor as connected if we have no state
PCI: Fix devfn for VPD access through function 0
PCI: Use function 0 VPD for identical functions, regular VPD for others
netfilter: nft_compat: skip family comparison in case of NFPROTO_UNSPEC
ASoC: fix broken pxa SoC support
ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets
vxlan: set needed headroom correctly
Revert "ARM: orion5x: fix legacy orion5x IRQ numbers"
jbd2: avoid infinite loop when destroying aborted journal
asix: Don't reset PHY on if_up for ASIX 88772
asix: Do full reset during ax88772_bind
fib_rules: Fix dump_rules() not to exit early
net/xen-netfront: only napi_synchronize() if running
cpufreq: intel_pstate: Remove unnecessary type casting in div_s64() call
intel_pstate: Fix overflow in busy_scaled due to long delay
tools lib traceevent: Fix string handling in heterogeneous arch environments
perf tools: Fix copying of /proc/kcore
m68k: Define asmlinkage_protect
UBI: Validate data_size
UBI: return ENOSPC if no enough space available
MIPS: dma-default: Fix 32-bit fall back to GFP_DMA
MIPS: CPS: Stop dangling delay slot from has_mt.
MIPS: CPS: Don't include MT code in non-MT kernels.
MIPS: CPS: #ifdef on CONFIG_MIPS_MT_SMP rather than CONFIG_MIPS_MT
drm/qxl: recreate the primary surface when the bo is not primary
genirq: Fix race in register_irq_proc()
x86/efi: Fix boot crash by mapping EFI memmap entries bottom-up at runtime, 
instead of top-down
Use WARN_ON_ONCE for missing X86_FEATURE_NRIPS
mm: hugetlbfs: skip shared VMAs when unmapping private pages to satisfy a fault
x86/mm: Set NX on gap between __ex_table and rodata
clocksource: Fix abs() usage w/ 64bit values
dmaengine: dw: properly read 

[Kernel-packages] [Bug 1514914] [NEW] linux-lts-utopic: 3.16.0-54.73~14.04.1 -proposed tracker

2015-11-10 Thread Luis Henriques
Public bug reported:

This bug is for tracking the 3.16.0-54.73~14.04.1 upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 16:52 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 10. November 2015 16:52 UTC

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: New


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Also affects: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** 

[Kernel-packages] [Bug 1514875] [NEW] linux: 3.19.0-34.39 -proposed tracker

2015-11-10 Thread Luis Henriques
Public bug reported:

This bug is for tracking the 3.19.0-34.39 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 15:06 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 10. November 2015 15:06 UTC

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux (Ubuntu Vivid)
 Importance: Medium
 Status: New


** Tags: block-proposed-vivid kernel-release-tracking-bug vivid

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-vivid

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Tags added: vivid

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1512999] Re: Support Edge Gateway's Bluetooth LED

2015-11-10 Thread Luis Henriques
** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512999

Title:
  Support Edge Gateway's Bluetooth LED

Status in HWE Next:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  The Bluetooth LED of Marvell 88W8897 is not enabled by default
  (there's no code for controlling LED). It is requested to be ON and
  OFF when the radio is on and off accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1512999/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1513847] Re: WWAN modules is recognized as an ethernet device

2015-11-10 Thread Luis Henriques
** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1513847

Title:
  WWAN modules is recognized as an ethernet device

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Bus 001 Device 005: ID 413c:81ba Dell Computer Corp.

  This device should be a WWAN module, but it's recognized as an
  ethernet device instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513847/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514832] Re: Trusty update to 3.13.11-ckt28 stable release

2015-11-10 Thread Luis Henriques
** 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/1514832

Title:
  Trusty update to 3.13.11-ckt28 stable release

Status in linux package in Ubuntu:
  Invalid
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 either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.13.11-ckt28 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.13.11-ckt28 stable release:

  sctp: fix race on protocol/netns initialization
  [media] v4l: omap3isp: Fix sub-device power management code
  [media] rc-core: fix remove uevent generation
  xtensa: fix threadptr reload on return to userspace
  ARM: OMAP2+: DRA7: clockdomain: change l4per2_7xx_clkdm to SW_WKUP
  mac80211: enable assoc check for mesh interfaces
  PCI: Add dev_flags bit to access VPD through function 0
  PCI: Add VPD function 0 quirk for Intel Ethernet devices
  usb: dwc3: ep0: Fix mem corruption on OUT transfers of more than 512 bytes
  serial: 8250_pci: Add support for Pericom PI7C9X795[1248]
  KVM: MMU: fix validation of mmio page fault
  auxdisplay: ks0108: fix refcount
  devres: fix devres_get()
  iio: adis16400: Fix adis16448 gyroscope scale
  iio: Add inverse unit conversion macros
  iio: adis16480: Fix scale factors
  iio: industrialio-buffer: Fix iio_buffer_poll return value
  iio: event: Remove negative error code from iio_event_poll
  NFSv4: don't set SETATTR for O_RDONLY|O_EXCL
  unshare: Unsharing a thread does not require unsharing a vm
  ASoC: adav80x: Remove .read_flag_mask setting from adav80x_regmap_config
  drivers: usb :fsl: Implement Workaround for USB Erratum A007792
  drivers: usb: fsl: Workaround for USB erratum-A005275
  serial: 8250: don't bind to SMSC IrCC IR port
  staging: comedi: adl_pci7x3x: fix digital output on PCI-7230
  blk-mq: fix buffer overflow when reading sysfs file of 'pending'
  xtensa: fix kernel register spilling
  NFS: nfs_set_pgio_error sometimes misses errors
  NFS: Fix a NULL pointer dereference of migration recovery ops for v4.2 client
  usb: host: ehci-sys: delete useless bus_to_hcd conversion
  USB: symbolserial: Use usb_get_serial_port_data
  USB: ftdi_sio: Added custom PID for CustomWare products
  HID: usbhid: Fix the check for HID_RESET_PENDING in hid_io_error
  eCryptfs: Invalidate dcache entries when lower i_nlink is zero
  libxfs: readahead of dir3 data blocks should use the read verifier
  xfs: Fix xfs_attr_leafblock definition
  arm64: kconfig: Move LIST_POISON to a safe value
  Btrfs: check if previous transaction aborted to avoid fs corruption
  DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd
  rtlwifi: rtl8192cu: Add new device ID
  rtlwifi: rtl8192cu: Add new device ID
  of/address: Don't loop forever in of_find_matching_node_by_address().
  drivercore: Fix unregistration path of platform devices
  xfs: return errors from partial I/O failures to files
  IB/qib: Change lkey table allocation to support more MRs
  tg3: Fix temperature reporting
  drm/i915: Always mark the object as dirty when used by the GPU
  Add radeon suspend/resume quirk for HP Compaq dc5750.
  IB/uverbs: reject invalid or unknown opcodes
  hpfs: update ctime and mtime on directory modification
  Input: evdev - do not report errors form flush()
  crypto: ghash-clmulni: specify context size for ghash async algorithm
  fs: create and use seq_show_option for escaping
  ALSA: hda - Enable headphone jack detect on old Fujitsu laptops
  ALSA: hda - Use ALC880_FIXUP_FUJITSU for FSC Amilo M1437
  scsi: fix scsi_error_handler vs. scsi_host_dev_release race
  parisc: Use double word condition in 64bit CAS operation
  vmscan: fix increasing nr_isolated incurred by putback unevictable pages
  hfs,hfsplus: cache pages correctly between bnode_create and bnode_free
  hfs: fix B-tree corruption after insertion at position 0
  drm/qxl: validate monitors config modes
  PCI: Fix TI816X class code quirk
  x86/mm: Initialize pmd_idx in page_table_range_init_count()
  powerpc/rtas: Introduce rtas_get_sensor_fast() for IRQ handlers
  jbd2: avoid infinite loop when destroying aborted journal
  clk: versatile: off by one in clk_sp810_timerclken_of_get()
  usb: gadget: m66592-udc: forever loop in set_feature()
  windfarm: decrement client count when unregistering
  perf hists: Update the column width for the "srcline" sort key
  batman-adv: Make DAT 

[Kernel-packages] [Bug 1442186] Comment bridged from LTC Bugzilla

2015-11-10 Thread bugproxy
--- Comment From wenxi...@us.ibm.com 2015-11-10 16:44 EDT---
Talked to Bill. He has verified the 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/1442186

Title:
  NVMe device driver failing w/nvme-user and htx tools

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  NVMe device driver running with a Samsung SM1715 card fails (hits EEH) 
w/nvme-user and htx tools
   
  Machine Type = Tuleta P8 
   
  ---Steps to Reproduce---
   1. Install the nvme-user tools package and run the nvme_rw tool
  or
  2. Install the htx I/O exerciser tool and run htx
   
  ---uname output---
  Linux ubuntu1504 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 13:44:26 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  EEH error in kernel log  after running HTX:

  [503195.365335] EEH: Frozen PE#2 on PHB#4 detected
  [503195.365346] EEH: PE location: U78CB.001.D123456-P1-C5  , PHB 
location: U
  78CB.001.D123456-P1-C33
  [503195.366226] EEH: This PCI device has failed 1 times in the last hour
  [503195.366227] EEH: Notify device drivers to shutdown
  [503195.366233] EEH: Collect temporary log
  [503195.366315] EEH: of node=/pciex@3fffe4200/pci@0/mass-storage@0
  [503195.366321] EEH: PCI device/vendor: a820144d
  [503195.366327] EEH: PCI cmd/status register: 00100546
  [503195.366329] EEH: PCI-E capabilities and status follow:
  [503195.366356] EEH: PCI-E 00: 00024010 10008fe1 202e 00416c43 
  [503195.366372] EEH: PCI-E 10: 10430040    
  [503195.366374] EEH: PCI-E 20:  
  [503195.366375] EEH: PCI-E AER capability register set follows:
  [503195.366396] EEH: PCI-E AER 00: 18020001  0040 00440010
  [503195.366413] EEH: PCI-E AER 10:  e000 01e0  
  [503195.366429] EEH: PCI-E AER 20:     
  [503195.366435] EEH: PCI-E AER 30:   
  [503195.366438] PHB3 PHB#4 Diag-data (Version: 1)
  [503195.366440] brdgCtl: 0002
  [503195.366442] UtlSts:  0020  
  [503195.366444] RootSts: 0020 0040 f0430048 00100147 
  [503195.366446] PhbSts:  001c 001c
  [503195.366448] Lem: 0400 42498e327f502eae 

  [503195.366450] InAErr:  4000 4000 
 
  [503195.366452] PE[  2] A/B: 80003025 8000
  [503195.366454] EEH: Reset with hotplug activity
  [503195.367741] nvme 0004:01:00.0: Cancelling I/O 0 QID 57
  [503199.411764] EEH: Sleep 5s ahead of complete hotplug
  [503204.415815] pci 0004:01:00.0: [144d:a820] type 00 class 0x010802
  [503204.415874] pci 0004:01:00.0: reg 0x10: [mem 0x-0x3fff 64bit]
  [503204.423731] pci 0004:01:00.0: BAR 0: assigned [mem 
0x3ff0-0x3ff03fff 64bit]
  [503204.423970] nvme 0004:01:00.0: enabling device (0140 -> 0142)
  [503204.423998] nvme 0004:01:00.0: Using 64-bit DMA iommu bypass
  [503207.914466]  nvme1n1: unknown partition table
  [503207.914643] EEH: Notify device driver to resume

  
  The PHB3 diag-data is telling: DMA write to PCI bus address 0x0, which 
doesn't have corresponding valid TCE entries. As I know, there are 2 
possibilities and (A) might be the case.

  (A) As MSI/MSIx interrupt is essentially DMA write transaction, the
  PCI bus address 0x0 would be MSI/MSIx message address. The address 0x0
  is obviously invalid. It indicates there is spurious MSI/MSIx
  interrupt whose MSI/MSIx message wasn't populated and updated to
  hardware yet.

  (B) We really have 0x0 DMA write transaction and the TCE entries
  wasn't populated and built yet. From the kernel log, we're using
  direct DMA window. So the DMA address shouldn't less than (0x1ul <<
  59).

  Recap the PHB3 diag-data
  

  [503195.366438] PHB3 PHB#4 Diag-data (Version: 1)
  [503195.366440] brdgCtl: 0002
  [503195.366442] UtlSts:  0020  
  [503195.366444] RootSts: 0020 0040 f0430048 00100147 
  [503195.366446] PhbSts:  001c 001c
  [503195.366448] Lem: 0400 42498e327f502eae 

  [503195.366450] InAErr:  4000 4000 
 
  [503195.366452] PE[  2] A/B: 80003025 8000

  William helped run following command, which triggers EEH error, which
  has same root cause as we saw before. After that, re-running the
  command won't trigger EEH again:

  # sudo dd if=/dev/nvme1n1 of=/dev/null bs=1k count=512
  # dmesg | grep EEH.*has\ failed
  [ 2377.124104] EEH: This PCI device has failed 1 times in the last hour

  I'm not sure if there is possibility of content in MSIx table is
  overwritten because the device has only one memory BAR. The top 4KB
  region of the BAR is 

[Kernel-packages] [Bug 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads

2015-11-10 Thread TJ
** Summary changed:

- Ralink RT2800pci doesnt work by default
+ PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1513477

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  reads

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1513297] Re: XE500C12-K01US Samsung Chromebook 2 Ubuntu 14.04 touchpad not responsive

2015-11-10 Thread rgkirch
I downloaded the following:
linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
linux-image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
I installed them with
sudo dpkg -i 
linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb 
linux-image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
and got an error like in error-both.txt.
I tried to install just the header and got an error like in error-header.txt. I 
tried installing them again and got the same thing. I rebooted and didn't catch 
the grub menu. Neither the laptops keyboard nor the touchpad worked. I plugged 
in an external keyboard and that worked. I edited /etc/defaults/grub to show 
the grub menu. I rebooted and picked the 4.3.0-040300-generic... kernel from 
the grub menu.
Now I'm in 4.3.0-040300-generic and the keyboard works but not the touchpad is 
not responsive at all.
$ uname -r
4.3.0-040300-generic
Were the errors misleading and the kernel installed correctly? Did I download 
the correct kernel? Was this the latest kernel? Do I test any more kernels or 
just add the tags as per your previous instructions?

Thank you for your help!

** Attachment added: "error.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513297/+attachment/4516302/+files/error.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/1513297

Title:
  XE500C12-K01US Samsung Chromebook 2 Ubuntu 14.04 touchpad not
  responsive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad is not responsive at all. It worked fine with chomium os
  but not ubuntu. I'm totally willing to work with you guys to get this
  fixed. Ubuntu 14.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Nov  4 22:14:54 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation ValleyView Gen7 [8086:0f31]
  InstallationDate: Installed on 2015-11-04 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 2232:1068  
   Bus 001 Device 005: ID 04e8:6863 Samsung Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Winky
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=ee476124-1af2-4cf8-8bd6-f0bcf555b924 ro acpi_backlight=vendor
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd09/19/2014:svnGOOGLE:pnWinky:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Winky
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Nov  4 19:45:44 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4188 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513297/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514861] Missing required logs.

2015-11-10 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1514861

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/1514861

Title:
   mlx5 EN driver wrongly enables sets VLAN filtering under promiscuous
  mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description of problem: The mlx5 Ethernet driver doesn't allow packets
  marked with all possible VLAN tags to be accepted under promiscuous
  mode. This is wrong and disallows Open-Stack to properly function in
  Para-Virtual configuration.

  
  How reproducible: 

   just put the NIC to promiscuous mode and send packet from another
  node tagged any vlan which was not previously configured on the NIC
  vlan filter, it will not be accepted.

  
  Actual results:
  ARP packets sent on vlan 52 packets are dropped 

  Expected results:
  packets should received 

  Host info:
  #uname -a
  Linux dev-h-vrt-006 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 15.10
  Release:15.10
  Codename:   wily

  
  The following upstream commit fix it:

  commit c07543431e9f3d126d083808efa0e76461d8833b
  Author: Achiad Shochat 
  Date:   Thu Oct 8 15:26:18 2015 +0300

  net/mlx5e: Disable VLAN filter in promiscuous mode

  When the device was set to promiscuous mode, we didn't disable
  VLAN filtering, which is wrong behaviour, fix that.

  Now when the device is set to promiscuous mode RX packets
  sent over any VLAN (or no VLAN tag at all) will be accepted.

  Signed-off-by: Achiad Shochat 
  Signed-off-by: Or Gerlitz 
  Signed-off-by: David S. Miller 

  I backported it to Ubuntu 15.10 (please see the attached patch). This
  issue need to be fix also in Ubuntu 14.04.4 not only 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514861/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1463911] Re: IPV6 fragmentation and mtu issue

2015-11-10 Thread Joseph Salisbury
** Tags removed: kernel-key
** 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/1463911

Title:
  IPV6 fragmentation and mtu issue

Status in neutron:
  Confirmed
Status in OpenStack Compute (nova):
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fragmented IPv6 packets are REJECTED by ip6tables on compute nodes.
  The traffic is goign through an intra-VM network and the packet loss
  is hurting the system.

  There is a patch for this issue:
  http://patchwork.ozlabs.org/patch/434957/

  I would like to know is there any bug report or official release date
  for this issue ?

  This is pretty critical for my deployment.

  Thanks in advance,

  BR,

  Gyula

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1463911/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514911] Re: Trusty update to 3.16.7-ckt19 stable release

2015-11-10 Thread Luis Henriques
** 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 3.16.7-ckt19 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 3.16.7-ckt19 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://kernel.ubuntu.com/ubuntu/linux.git
  
-git://kernel.ubuntu.com/ubuntu/linux.git
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches are in the 3.16.7-ckt19 stable release:
  
-The following patches are in the 3.16.7-ckt19 stable release:
+ ARM: 8429/1: disable GCC SRA optimization
+ CIFS: fix type confusion in copy offload ioctl
+ hwmon: (nct6775) Swap STEP_UP_TIME and STEP_DOWN_TIME registers for most chips
+ x86/apic: Serialize LVTT and TSC_DEADLINE writes
+ arm64: head.S: initialise mdcr_el2 in el2_setup
+ kvm: don't try to register to KVM_FAST_MMIO_BUS for non mmio eventfd
+ kvm: factor out core eventfd assign/deassign logic
+ kvm: fix double free for fast mmio eventfd
+ kvm: fix zero length mmio searching
+ ARM: fix Thumb2 signal handling when ARMv6 is enabled
+ powerpc/boot: Specify ABI v2 when building an LE boot wrapper
+ powerpc/mm: Recompute hash value after a failed update
+ x86/platform: Fix Geode LX timekeeping in the generic x86 build
+ arm64: compat: fix vfp save/restore across signal handlers in big-endian
+ arm64: errata: add module build workaround for erratum #843419
+ arm64: KVM: Disable virtual timer even if the guest is not using it
+ arm: KVM: Disable virtual timer even if the guest is not using it
+ hp-wmi: Add missing __init annotations to initialization code
+ hp-wmi: limit hotkey enable
+ zram: fix possible use after free in zcomp_create()
+ perf header: Fixup reading of HEADER_NRCPUS feature
+ spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
+ spi: Fix documentation of spi_alloc_master()
+ USB: option: add ZTE PIDs
+ drm/vmwgfx: Fix up user_dmabuf refcounting
+ ARM: dts: omap3-beagle: make i2c3, ddc and tfp410 gpio work again
+ Btrfs: fix read corruption of compressed and shared extents
+ btrfs: skip waiting on ordered range for special files
+ usb: chipidea: udc: using the correct stall implementation
+ net: mvneta: fix DMA buffer unmapping in mvneta_rx()
+ iser-target: remove command with state ISTATE_REMOVE
+ staging: ion: fix corruption of ion_import_dma_buf
+ KVM: x86: trap AMD MSRs for the TSeg base and mask
+ usb: Use the USB_SS_MULT() macro to get the burst multiplier.
+ xhci: give command abortion one more chance before killing xhci
+ usb: xhci: Clear XHCI_STATE_DYING on start
+ usb: xhci: Allow usb_add/remove_hcd() to be called repeatedly
+ xhci: change xhci 1.0 only restrictions to support xhci 1.1
+ xhci-mem: Use setup_timer
+ xhci: init command timeout timer earlier to avoid deleting it uninitialized
+ spi: xtensa-xtfpga: fix register endianness
+ disabling oplocks/leases via module parm enable_oplocks broken for SMB3
+ cifs: use server timestamp for ntlmv2 authentication
+ x86/paravirt: Replace the paravirt nop with a bona fide empty function
+ x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
+ ASoC: pxa: pxa2xx-ac97: fix dma requestor lines
+ ocfs2/dlm: fix deadlock when dispatch assert master
+ drm/i915/bios: handle MIPI Sequence Block v3+ gracefully
+ drm/qxl: only report first monitor as connected if we have no state
+ PCI: Fix devfn for VPD access through function 0
+ PCI: Use function 0 VPD for identical functions, regular VPD for others
+ netfilter: nft_compat: skip family comparison in case of NFPROTO_UNSPEC
+ ASoC: fix broken pxa SoC support
+ ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets
+ vxlan: set needed headroom correctly
+ Revert "ARM: orion5x: fix legacy orion5x IRQ numbers"
+ jbd2: avoid infinite loop when destroying aborted journal
+ asix: Don't reset PHY on if_up for ASIX 88772
+ asix: Do full reset during ax88772_bind
+ fib_rules: Fix dump_rules() not to exit early
+ net/xen-netfront: only napi_synchronize() if running
+ cpufreq: intel_pstate: Remove unnecessary type casting in div_s64() call
+ intel_pstate: Fix overflow in busy_scaled due to long delay
+ tools lib traceevent: Fix string handling in heterogeneous arch environments
+ perf tools: Fix 

[Kernel-packages] [Bug 1514808] Re: linux: 3.2.0-95.135 -proposed tracker

2015-11-10 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514808

Title:
  linux: 3.2.0-95.135 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-95.135 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, 10. November 2015 12:07 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 12:07 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514808/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514907] Re: package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-11-10 Thread Joseph Salisbury
You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514907

Title:
  package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following prompting to submit info. Haven't a clue what even happened.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-68-generic 3.13.0-68.111
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bguilfoyle   2780 F pulseaudio
  Date: Tue Nov 10 08:05:53 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=2c98cf1a-2238-454e-b55e-98ef172d4bd6
  InstallationDate: Installed on 2013-11-11 (728 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/xubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-09 (489 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/30/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514907/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 899463] Re: CVE-2011-1162

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
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/899463

Title:
  CVE-2011-1162

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
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-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-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 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-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-utopic source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Invalid
Status in linux-lts-backport-natty source package in Utopic:
  Invalid
Status in linux-lts-backport-oneiric source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  Invalid
Status in linux-lts-backport-natty source package in Vivid:
  Invalid
Status in linux-lts-backport-oneiric source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  Invalid
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  Invalid
Status in linux-lts-backport-maverick source package in Wily:
  Invalid
Status in linux-lts-backport-natty source package in Wily:
  Invalid
Status in linux-lts-backport-oneiric source package in Wily:
  Invalid
Status in 

[Kernel-packages] [Bug 1514911] Re: Trusty update to 3.16.7-ckt19 stable release

2015-11-10 Thread Luis Henriques
** 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/1514911

Title:
  Trusty update to 3.16.7-ckt19 stable release

Status in linux package in Ubuntu:
  Invalid
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 either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.16.7-ckt19 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.16.7-ckt19 stable release:

  ARM: 8429/1: disable GCC SRA optimization
  CIFS: fix type confusion in copy offload ioctl
  hwmon: (nct6775) Swap STEP_UP_TIME and STEP_DOWN_TIME registers for most chips
  x86/apic: Serialize LVTT and TSC_DEADLINE writes
  arm64: head.S: initialise mdcr_el2 in el2_setup
  kvm: don't try to register to KVM_FAST_MMIO_BUS for non mmio eventfd
  kvm: factor out core eventfd assign/deassign logic
  kvm: fix double free for fast mmio eventfd
  kvm: fix zero length mmio searching
  ARM: fix Thumb2 signal handling when ARMv6 is enabled
  powerpc/boot: Specify ABI v2 when building an LE boot wrapper
  powerpc/mm: Recompute hash value after a failed update
  x86/platform: Fix Geode LX timekeeping in the generic x86 build
  arm64: compat: fix vfp save/restore across signal handlers in big-endian
  arm64: errata: add module build workaround for erratum #843419
  arm64: KVM: Disable virtual timer even if the guest is not using it
  arm: KVM: Disable virtual timer even if the guest is not using it
  hp-wmi: Add missing __init annotations to initialization code
  hp-wmi: limit hotkey enable
  zram: fix possible use after free in zcomp_create()
  perf header: Fixup reading of HEADER_NRCPUS feature
  spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
  spi: Fix documentation of spi_alloc_master()
  USB: option: add ZTE PIDs
  drm/vmwgfx: Fix up user_dmabuf refcounting
  ARM: dts: omap3-beagle: make i2c3, ddc and tfp410 gpio work again
  Btrfs: fix read corruption of compressed and shared extents
  btrfs: skip waiting on ordered range for special files
  usb: chipidea: udc: using the correct stall implementation
  net: mvneta: fix DMA buffer unmapping in mvneta_rx()
  iser-target: remove command with state ISTATE_REMOVE
  staging: ion: fix corruption of ion_import_dma_buf
  KVM: x86: trap AMD MSRs for the TSeg base and mask
  usb: Use the USB_SS_MULT() macro to get the burst multiplier.
  xhci: give command abortion one more chance before killing xhci
  usb: xhci: Clear XHCI_STATE_DYING on start
  usb: xhci: Allow usb_add/remove_hcd() to be called repeatedly
  xhci: change xhci 1.0 only restrictions to support xhci 1.1
  xhci-mem: Use setup_timer
  xhci: init command timeout timer earlier to avoid deleting it uninitialized
  spi: xtensa-xtfpga: fix register endianness
  disabling oplocks/leases via module parm enable_oplocks broken for SMB3
  cifs: use server timestamp for ntlmv2 authentication
  x86/paravirt: Replace the paravirt nop with a bona fide empty function
  x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
  ASoC: pxa: pxa2xx-ac97: fix dma requestor lines
  ocfs2/dlm: fix deadlock when dispatch assert master
  drm/i915/bios: handle MIPI Sequence Block v3+ gracefully
  drm/qxl: only report first monitor as connected if we have no state
  PCI: Fix devfn for VPD access through function 0
  PCI: Use function 0 VPD for identical functions, regular VPD for others
  netfilter: nft_compat: skip family comparison in case of NFPROTO_UNSPEC
  ASoC: fix broken pxa SoC support
  ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets
  vxlan: set needed headroom correctly
  Revert "ARM: orion5x: fix legacy orion5x IRQ numbers"
  jbd2: avoid infinite loop when destroying aborted journal
  asix: Don't reset PHY on if_up for ASIX 88772
  asix: Do full reset during ax88772_bind
  fib_rules: Fix dump_rules() not to exit early
  net/xen-netfront: only napi_synchronize() if running
  cpufreq: intel_pstate: Remove unnecessary type casting in div_s64() call
  intel_pstate: Fix overflow in busy_scaled due to long delay
  tools lib traceevent: Fix string handling in heterogeneous arch environments
  perf tools: Fix copying of /proc/kcore
  m68k: Define asmlinkage_protect
  UBI: Validate data_size
  UBI: return ENOSPC if no enough space available
  MIPS: dma-default: Fix 32-bit fall back to GFP_DMA
  MIPS: CPS: Stop dangling delay slot from has_mt.
  MIPS: CPS: Don't 

[Kernel-packages] [Bug 1514066] Re: Touchpad not working on ASUS ZenBook UX305CA-FC037T

2015-11-10 Thread zoulou77
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514066

Title:
  Touchpad not working on ASUS ZenBook UX305CA-FC037T

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not working on a new installation of ubuntu 15.10
  HW is ok; was tested on W10.

  Same issue as described here:
  
http://askubuntu.com/questions/693701/touchpad-not-workingon-asus-ux305-under-ubuntu-15-10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tmp1724 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov  7 13:29:42 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=38e264e5-e90e-4b33-a8a3-302a4327fe70
  InstallationDate: Installed on 2015-11-07 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 004: ID 046d:c06c Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic.efi.signed 
root=UUID=3d3973ea-7464-4c42-8e63-e7d3f13cf052 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-17-generic N/A
   linux-backports-modules-4.2.0-17-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  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/1514066/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514875] Re: linux: 3.19.0-34.39 -proposed tracker

2015-11-10 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514875

Title:
  linux: 3.19.0-34.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-34.39 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 15:06 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 15:06 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514875/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514907] Status changed to Confirmed

2015-11-10 Thread Brad Figg
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/1514907

Title:
  package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following prompting to submit info. Haven't a clue what even happened.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-68-generic 3.13.0-68.111
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bguilfoyle   2780 F pulseaudio
  Date: Tue Nov 10 08:05:53 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=2c98cf1a-2238-454e-b55e-98ef172d4bd6
  InstallationDate: Installed on 2013-11-11 (728 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/xubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-68-generic 3.13.0-68.111 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-07-09 (489 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/30/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514907/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514959] Status changed to Confirmed

2015-11-10 Thread Brad Figg
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/1514959

Title:
  package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade:
  package linux-headers-4.2.0-17 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is because my mistake, while process dpkg running I force stop
  that. so this what I get... unfortunately I do not how to solve that,
  even I try `sudo apt-get install --reinstall linux-image-`uname -r`
  just this is what I've got

   Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/26,4 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 324990 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.2.0-17-generic_4.2.0-17.21_i386.deb ...
  Examining /etc/kernel/preinst.d/
  run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Done.
  Unpacking linux-image-4.2.0-17-generic (4.2.0-17.21) over (4.2.0-17.21) ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  dpkg: error processing package linux-headers-4.2.0-17 (--configure):
   package linux-headers-4.2.0-17 is not ready for configuration
   cannot configure (current status 'half-installed')
  Setting up linux-image-4.2.0-17-generic (4.2.0-17.21) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Not updating initrd symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Not updating image symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  update-initramfs: Generating /boot/initrd.img-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.2.0-17-generic /boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  Errors were encountered while processing:
   linux-headers-4.2.0-17
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  just send an email to me (ryuffhan...@gmail.com) also can tell through
  gTalk/Hangouts if there's any advice to fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-17 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   linux-headers-4.2.0-17: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 891 F pulseaudio
irfan  1385 F pulseaudio
  Date: Wed Nov 11 01:35:35 2015
  DpkgTerminalLog:
   dpkg: error processing package linux-headers-4.2.0-17 (--configure):
package linux-headers-4.2.0-17 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature: package:linux-headers-4.2.0-17:4.2.0-17.21:package 
linux-headers-4.2.0-17 is not ready for configuration  cannot configure 
(current status 'half-installed')
  ErrorMessage: package linux-headers-4.2.0-17 is not ready for configuration  
cannot configure (current status 'half-installed')
  HibernationDevice: 

[Kernel-packages] [Bug 887299] Re: CVE-2011-4081

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/887299

Title:
  CVE-2011-4081

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 894369] Re: CVE-2011-4110

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/894369

Title:
  CVE-2011-4110

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 911397] Re: CVE-2011-4127

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/911397

Title:
  CVE-2011-4127

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-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 source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 1115753] Re: Umount of Multiple LVM Snapshots Causes 'soft lockup CPU#0 stuck for'

2015-11-10 Thread Tomas Pospisek
So I'm reporting my current further findings here in case somebody else
than me stumbles upon this bug report in search of help.

I'll not create a new bug report as of now, since I'm still researching
the problem and I think there's no point in opening a new bug report if
it'll turn out to be invalid anyway.

So to the point: in my case the problem has been:

  8 05:02:51 foo kernel: [987432.148305] device-mapper: snapshots:
Invalidating snapshot: Unable to allocate exception.

after that umount goes berzerk:

  Nov  8 05:02:51 foo kernel: [987432.163602] Buffer I/O error on device dm-11, 
logical block 11985789
  Nov  8 05:02:51 foo kernel: [987432.163638] Buffer I/O error on device dm-11, 
logical block 11985790
  ...
  Nov  8 05:02:51 foo kernel: [987432.299393] EXT4-fs warning (device loop0): 
__ext4_read_dirblock:901: error reading directory block (ino 3539872, block 0)
  Nov  8 05:02:57 foo kernel: [987437.577541] quiet_error: 4396 callbacks 
suppressed
  Nov  8 05:02:57 foo kernel: [987437.577547] Buffer I/O error on device dm-11, 
logical block 12622895
  Nov  8 05:02:57 foo kernel: [987437.577609] lost page write due to I/O error 
on dm-11

and now umount is hanging there with 100% CPU usage with no possibility
to `kill` it.

So one problem here is that the `lvsnapshot` is running out of
`exception` space. Thus I should either allow the snapshot to be
autoextended or to increase the `-L`size I have given it.

But even so, umount shouldn't get stuck on the ext4 FS. Since I was
`umount`ing without `-f` I will try that today and see what happens and
report back here hopefully.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753

Title:
  Umount of Multiple LVM Snapshots Causes  'soft lockup CPU#0 stuck for'

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Simultaneous umount of multiple lvm snapshots causes system to hang /
  freeze / deadlock.  Window manager freezes.  If umount is executed in
  a non window-manager tty,  messages containing "BUG", "blocked for
  more than xx seconds", and a list of tasks associated with each of the
  8 cpu cores will scroll up at regular intervals.  The tasks assigned
  to each cpu core are unchanging over time, appearing to be deadlocked.
  No relevant information is left in system logs.  Hard reset / poweroff
  is required.  Problem does not occur 100% of the time.  It is less
  likely to occur if umount is done shortly after mount.  Problem still
  occurs -- but less frequently -- if lazy umount -l is used.  Snapshots
  are read-only, and are mounted read-only.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  craig  3257 F pulseaudio
   /dev/snd/controlC0:  craig  3257 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1043846b,0014'
 Controls  : 49
 Simple ctrls  : 24
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfea3 irq 98'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Feb  4 18:58:37 2013
  HibernationDevice: RESUME=UUID=b788f786-ba76-4eb0-991f-d3bbc339d3f7
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-37-generic 
root=/dev/mapper/volgroup0-root ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-10-23 (104 days ago)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0813
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Crosshair V Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1513477] Re: PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait writes

2015-11-10 Thread TJ
** Tags removed: amd64 apport-bug kernel-bug-exists-upstream kernel-bug-
exists-upstream-4.3 needs-bisect regression-release xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1513477

Title:
  PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait
  writes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  No wifi connection showing, wifi network card is unclaimed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.2.0.16.18
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1410 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  5 14:57:40 2015
  HibernationDevice: RESUME=UUID=c391bf39-6cd0-4357-89f6-46b8c496b553
  InstallationDate: Installed on 2015-10-28 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp0s14   no wireless extensions.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c53d01a4-d573-4ab2-ad75-f2c8bd8645c3 ro pci=realloc
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.152
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (8 days ago)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

2015-11-10 Thread oleg
** No longer affects: lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463

Title:
  OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
  2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).

  There are two issues in OverlayFS as follows:

   1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
  /proc//mountinfo)

   2. /proc//fd/ shows incorrect path for the symlink target

  These issues were previously reported and patched for the Ubuntu Vivid
  kernel (3.19) in bug #1479468, but the patch was not applied to the
  3.13 kernel, possibly because it contains an older version of
  overlayfs.

  These issues are now adversely affecting some versions of lxc when
  used in conjunction with the 3.13 kernel, because lxc has recently
  been patched to pass /proc//fd/ to the mount syscall.  This
  change to lxc was made in response to cve-2015-1335; see bug #1476662.

  The kernel issues cause some overlayfs-backed containers to fail to
  start, with error message,

  strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
  0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)

  The mount fails because /proc/self/fd/16, which should point to a file
  in overlayfs, has an invalid value.

  The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
  is not affected.  The following versions of lxc are affected:

  repository lxc version
  
  ppa:ubuntu-lxc/lxc-git-stable-1.0  1.0.7+stable~20151014-2143-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-stable-1.1  1.1.3+stable~20151007-2301-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-master  1.1.3+master~20151012-0541-0ubuntu1~trusty

  To reproduce the lxc failure-to-start issue:

  # Install the 3.13 kernel and also an affected version of lxc.
  lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
  touch $HOME/test.txt;
  echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none 
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
  lxc-clone -s -B overlayfs trusty trusty_overlay;
  lxc-start -n trusty_overlay; # fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1357090] Re: Black screen on resume in Xubuntu 14.04.1

2015-11-10 Thread Frank Earl
Still busted.  Guys...this is on 15.10, some 18 months past the time
that you honestly found this to be a problem and largely should've found
the blasted thing.

Desktops, servers, and phones aren't and shouldn't be your sole focus.
FIX THIS.  I don't care who, upstream, you have to dopeslap to do this,
but it's a noxious combination of logind (it screws up on a second
login, guys...there's a hint...) LightDM, and Lightlocker.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1357090

Title:
  Black screen on resume in Xubuntu 14.04.1

Status in linux package in Ubuntu:
  Expired

Bug description:
  It seems #1303736 is Not fixed.

  Black screen on resume when using standby on close lid is confirmed on
  Dell Latitude D400 on completely new install of Xubuntu 14.04.1 32
  bit. downloaded 14 Aug from repository as a .ISO image.

  This despite claims to the contrary on the website.
  http://xubuntu.org/news/xubuntu-14-04-1-released/ pointing to
  https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-
  settings/+bug/1303736

  Using the "Suspend" key results in correct operation, i.e. the laptop
  suspends and resumes correctly on lid open. Suspending by closing the
  laptop lid results in the black screen when re-opening. Once in black
  screen mode, the only recourse is power off re-boot.

  Although power manager is set correctly to "Suspend" in the power
  manager , on closing the lid the system does NOT appear to suspend as
  it does when the "Log-off Suspend" button is clicked or the hardware
  "Suspend" key is pressed i.e. the problem APPEARS to be on lid close.

  Power manager and light-locker set NOT to lock on suspend or shutdown
  makes no difference to behaviour.

  Xubuntu up to 12.04.4 (plus latest updates) worked absolutely
  correctly before new install of 14.04.1

  This is a MAJOR inconvenience for an upgrade of an LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357090/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend

2015-11-10 Thread Daniele Cruciani
I upgraded to 15.10, I can not suspend anymore (laptop freeze). These are the 
relative log:
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.315877] wlan0: 
deauthenticating from 00:0f:b5:57:61:64 by local choice (Reason: 
3=DEAUTH_LEAVING)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328304] cfg80211: World 
regulatory domain updated:
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328306] cfg80211:  DFS 
Master region: unset
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328307] cfg80211:   
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), 
(dfs_cac_time)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328309] cfg80211:   
(2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328310] cfg80211:   
(2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328311] cfg80211:   
(2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328312] cfg80211:   
(517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328314] cfg80211:   
(525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328315] cfg80211:   
(549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328316] cfg80211:   
(5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.328317] cfg80211:   
(5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)


Then it freeze and my only option is to cold switch-off.
it is a toshiba satellite, but it look like to be wifi related this.

I will try the suggested
sudo wpa_cli suspend

now.
see you tomorrow

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1487919

Title:
  macbookrpro12,1 fails to suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed wily on a new macbookpro12,1 (2015 model), and
  suspending the system results in the screen going black and the apple
  light turning off, but the system is not fully asleep -- the 'force
  touch' pad still makes clicking feedback, and the machine continues to
  generate heat and spin fans if put into a bag.  Once in this state,
  the machine cannot be woken up from the state its in either.

  did a "journalctl -f | tee sleep.log' while this was happening and got
  the following output -- let me know if there is a better way to figure
  out where things are going wrong:


  Aug 23 15:13:21 spiny NetworkManager[820]:  sleep requested (sleeping: 
no  enabled: yes)
  Aug 23 15:13:21 spiny NetworkManager[820]:  sleeping...
  Aug 23 15:13:21 spiny NetworkManager[820]:  (wlp3s0): device state 
change: activated -> unmanaged (reason 'sleeping') [100 10 37]
  Aug 23 15:13:21 spiny NetworkManager[820]:  (wlp3s0): deactivating 
device (reason 'sleeping') [37]
  Aug 23 15:13:21 spiny NetworkManager[820]:  (wlp3s0): canceled DHCP 
transaction, DHCP client pid 925
  Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 
2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 
2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on 
interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on 
interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for 
fe80::290:4cff:fe0d:f43e on wlp3s0.*.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 
fe80::290:4cff:fe0d:f43e on wlp3s0.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on 
interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer 
relevant for mDNS.
  Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED 
bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1
  Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local 
disconnect but got another disconnect event first
  Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 
192.168.1.83 on wlp3s0.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on 
interface wlp3s0.IPv4 with address 192.168.1.83.
  Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer 
relevant for mDNS.
  Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world 
regulatory domain
  Aug 23 

[Kernel-packages] [Bug 1514858] Re: linux: 3.13.0-69.112 -proposed tracker

2015-11-10 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514858

Title:
  linux: 3.13.0-69.112 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-69.112 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, 10. November 2015 14:31 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 14:31 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1513540] Re: CVE-2015-5307

2015-11-10 Thread Steve Beattie
** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu.
https://bugs.launchpad.net/bugs/1513540

Title:
  CVE-2015-5307

Status in linux package in Ubuntu:
  New
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  New
Status in linux-fsl-imx51 source package in Precise:
  New
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-mvl-dove source package in Precise:
  New
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-ec2 source package in Trusty:
  New
Status in linux-fsl-imx51 source package in Trusty:
  New
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-mvl-dove source package in Trusty:
  New
Status in linux-ti-omap4 source package in Trusty:
  New
Status in linux source package in Vivid:
  Fix Released
Status in linux-ec2 source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Released
Status in linux-ec2 source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  New
Status in linux-lts-backport-maverick source package in Wily:
  New
Status in linux-lts-backport-natty source package in Wily:
  New
Status in linux-mvl-dove source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  New
Status in linux source package in Xenial:
  New
Status in linux-ec2 source package in Xenial:
  New
Status in linux-fsl-imx51 source package in Xenial:
  New
Status in linux-lts-backport-maverick source package in Xenial:
  New
Status in linux-lts-backport-natty source package in Xenial:
  New
Status in linux-mvl-dove source package in Xenial:
  New
Status in linux-ti-omap4 source package in Xenial:
  New

Bug description:
  Placeholder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513540/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514914] Re: linux-lts-utopic: 3.16.0-54.73~14.04.1 -proposed tracker

2015-11-10 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1514914

Title:
  linux-lts-utopic: 3.16.0-54.73~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-54.73~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 16:52 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 16:52 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514914/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1441303] Re: CVE-2010-5321

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1441303

Title:
  CVE-2010-5321

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal 

[Kernel-packages] [Bug 1514808] Re: linux: 3.2.0-95.135 -proposed tracker

2015-11-10 Thread Brad Figg
All builds are complete, packages in this bug can be copied to
-proposed.

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-ti-omap4 - bug 1514962
linux-armadaxp - bug 1514964

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.2.0-95.135 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, 10. November 2015 12:07 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 10. November 2015 12:07 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 10. November 2015 19:03 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 10. November 2015 19:03 UTC
+ kernel-stable-phase-changed:Tuesday, 10. November 2015 19:03 UTC

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514808

Title:
  linux: 3.2.0-95.135 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-95.135 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, 10. November 2015 12:07 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 10. November 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 10. November 2015 19:03 UTC
  kernel-stable-phase-changed:Tuesday, 10. November 2015 19:03 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514808/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 887298] Re: CVE-2011-4077

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/887298

Title:
  CVE-2011-4077

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 1514959] Re: package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade: package linux-headers-4.2.0-17 is not ready for configuration cannot configure (current status

2015-11-10 Thread Joseph Salisbury
You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "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/1514959

Title:
  package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade:
  package linux-headers-4.2.0-17 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is because my mistake, while process dpkg running I force stop
  that. so this what I get... unfortunately I do not how to solve that,
  even I try `sudo apt-get install --reinstall linux-image-`uname -r`
  just this is what I've got

   Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/26,4 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 324990 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.2.0-17-generic_4.2.0-17.21_i386.deb ...
  Examining /etc/kernel/preinst.d/
  run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Done.
  Unpacking linux-image-4.2.0-17-generic (4.2.0-17.21) over (4.2.0-17.21) ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  dpkg: error processing package linux-headers-4.2.0-17 (--configure):
   package linux-headers-4.2.0-17 is not ready for configuration
   cannot configure (current status 'half-installed')
  Setting up linux-image-4.2.0-17-generic (4.2.0-17.21) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Not updating initrd symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Not updating image symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  update-initramfs: Generating /boot/initrd.img-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.2.0-17-generic /boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  Errors were encountered while processing:
   linux-headers-4.2.0-17
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  just send an email to me (ryuffhan...@gmail.com) also can tell through
  gTalk/Hangouts if there's any advice to fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-17 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   linux-headers-4.2.0-17: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 891 F pulseaudio
irfan  1385 F pulseaudio
  Date: Wed Nov 11 01:35:35 2015
  DpkgTerminalLog:
   dpkg: error processing package linux-headers-4.2.0-17 (--configure):
package linux-headers-4.2.0-17 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature: package:linux-headers-4.2.0-17:4.2.0-17.21:package 
linux-headers-4.2.0-17 is not ready for configuration  cannot configure 
(current status 'half-installed')
  ErrorMessage: package 

[Kernel-packages] [Bug 1357090] Re: Black screen on resume in Xubuntu 14.04.1

2015-11-10 Thread Frank Earl
Now, for reference...

MSI Apache Pro GE72-2QE.

i7-5700hq
16Gb of DDR3
NVidia GTX960m

Nothing that isn't supported, either with a bit of telling nouveau to
not do modesetting, or the like.  I should be able to, once I get
Bumblebee/Optimus/Primus running, have a beast of a laptop that doesn't
have suspend or similar problems.  Furious about this not being fixed by
now doesn't begin to describe this, guys.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1357090

Title:
  Black screen on resume in Xubuntu 14.04.1

Status in linux package in Ubuntu:
  Expired

Bug description:
  It seems #1303736 is Not fixed.

  Black screen on resume when using standby on close lid is confirmed on
  Dell Latitude D400 on completely new install of Xubuntu 14.04.1 32
  bit. downloaded 14 Aug from repository as a .ISO image.

  This despite claims to the contrary on the website.
  http://xubuntu.org/news/xubuntu-14-04-1-released/ pointing to
  https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-
  settings/+bug/1303736

  Using the "Suspend" key results in correct operation, i.e. the laptop
  suspends and resumes correctly on lid open. Suspending by closing the
  laptop lid results in the black screen when re-opening. Once in black
  screen mode, the only recourse is power off re-boot.

  Although power manager is set correctly to "Suspend" in the power
  manager , on closing the lid the system does NOT appear to suspend as
  it does when the "Log-off Suspend" button is clicked or the hardware
  "Suspend" key is pressed i.e. the problem APPEARS to be on lid close.

  Power manager and light-locker set NOT to lock on suspend or shutdown
  makes no difference to behaviour.

  Xubuntu up to 12.04.4 (plus latest updates) worked absolutely
  correctly before new install of 14.04.1

  This is a MAJOR inconvenience for an upgrade of an LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357090/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace

2015-11-10 Thread oleg
@Serge,

Thanks for the clarification;  I'll revert the status to un-marked.

** No longer affects: lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1480411

Title:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace.

  If overlayfs is mounted as follows,

     mount -n -t overlay overlay -o
  lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt

  and if lowerdir contains lowerdir/foo/bar.txt, then,

     rm -r mntpt/foo

  fails with error message,

     "rm: cannot remove ‘mntpt/foo’: Operation not permitted"

  strace shows,

  unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM
  (Operation not permitted)

  OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid
  kernel (3.19).

  The bug does not occur on ubuntu 14.04.2 with the default linux-
  generic 3.13 kernel.

  The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch,
  "overlayfs: allow unprivileged mounts" is added.  (The patch is at,
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea)

  The bug occurs regardless of whether the filesystem underlying
  overlayfs is tmpfs or ext4.

  The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a
  virtual machine (qemu-system-x86_64).  The host is ubuntu 14.04.2 with
  the default 3.13 kernel.

  A script which reproduces the bug is attached and is also available at
  http://paste.ubuntu.com/11974137/

  Hardware: intel core2 duo processor in a macbook-4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 899466] Re: CVE-2011-2203

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/899466

Title:
  CVE-2011-2203

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 1514959] [NEW] package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade: package linux-headers-4.2.0-17 is not ready for configuration cannot configure (current stat

2015-11-10 Thread Irfan Sopiyan
Public bug reported:

This is because my mistake, while process dpkg running I force stop
that. so this what I get... unfortunately I do not how to solve that,
even I try `sudo apt-get install --reinstall linux-image-`uname -r` just
this is what I've got

 Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
1 not fully installed or removed.
Need to get 0 B/26,4 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 324990 files and directories currently installed.)
Preparing to unpack .../linux-image-4.2.0-17-generic_4.2.0-17.21_i386.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
Done.
Unpacking linux-image-4.2.0-17-generic (4.2.0-17.21) over (4.2.0-17.21) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
dpkg: error processing package linux-headers-4.2.0-17 (--configure):
 package linux-headers-4.2.0-17 is not ready for configuration
 cannot configure (current status 'half-installed')
Setting up linux-image-4.2.0-17-generic (4.2.0-17.21) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled 
(4.2.0-17.21 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled 
(4.2.0-17.21 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
update-initramfs: Generating /boot/initrd.img-4.2.0-17-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.2.0-17-generic /boot/vmlinuz-4.2.0-17-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-4.2.0-17-generic
Found kernel: /boot/vmlinuz-4.2.0-16-generic
Found kernel: /boot/memtest86+.bin
Found kernel: /boot/vmlinuz-4.2.0-17-generic
Found kernel: /boot/vmlinuz-4.2.0-16-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

Errors were encountered while processing:
 linux-headers-4.2.0-17
E: Sub-process /usr/bin/dpkg returned an error code (1)

just send an email to me (ryuffhan...@gmail.com) also can tell through
gTalk/Hangouts if there's any advice to fix it.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-headers-4.2.0-17 4.2.0-17.21
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic i686
ApportVersion: 2.19.1-0ubuntu5
AptOrdering:
 linux-headers-4.2.0-17: Configure
 NULL: ConfigurePending
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 891 F pulseaudio
  irfan  1385 F pulseaudio
Date: Wed Nov 11 01:35:35 2015
DpkgTerminalLog:
 dpkg: error processing package linux-headers-4.2.0-17 (--configure):
  package linux-headers-4.2.0-17 is not ready for configuration
  cannot configure (current status 'half-installed')
DuplicateSignature: package:linux-headers-4.2.0-17:4.2.0-17.21:package 
linux-headers-4.2.0-17 is not ready for configuration  cannot configure 
(current status 'half-installed')
ErrorMessage: package linux-headers-4.2.0-17 is not ready for configuration  
cannot configure (current status 'half-installed')
HibernationDevice: RESUME=UUID=a64d8cc8-080b-459d-8153-8b7a2d8125c1
InstallationDate: Installed on 2015-11-06 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: TOSHIBA T20
PackageArchitecture: all
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=ddebefac-3dfc-49ab-8bc0-d3fef3cf3a8b ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
Title: package 

[Kernel-packages] [Bug 1514971] [NEW] [SRU trusty] arm64 USB support not enabled for APM Mustang

2015-11-10 Thread Craig Magina
Public bug reported:

[Impact]
Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

[Test Case]
Insert a USB device into an APM Mustang based platform.

[Regression Risk]
This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514971

Title:
  [SRU trusty] arm64 USB support not enabled for APM Mustang

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

  [Test Case]
  Insert a USB device into an APM Mustang based platform.

  [Regression Risk]
  This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514052] Re: erratic fan speed and little control kernel 4.2

2015-11-10 Thread Benjamin
The issue remains using the kernel 4.3.0 on my Dell Studio XPS 8000

This issue came when i upgraded My Ubuntu from vivid to wily so it
worked well on kernels 3.19.*

I have even done a fresh install of wily from the official ISO to be
sure it wasn't a configuration issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514052

Title:
  erratic fan speed and little control kernel 4.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 15.10 and almost immediately my CPU fan
  started speeding and slowing without good reason even when the PC is
  idle.

  I tried various things but then found that if I leave the computer off
  for a long time and let everything cool down then when I boot from
  cold the CPU fan is stable.

  To test my theory of cold start out I then ran
  sudo cpupower frequency-set -g powersave
  followed by
  sudo cpupower frequency-set -g ondemand

  The final mode is the initial mode.  Almost immediately as soon as I
  moved to powersave mode the erratic fan speed started.  It did not
  stop when I returned to ondemand.

  Temp fix for this behaviour is - go and have a cup of coffee and let
  the computer cool down when you restart: shutdown then start from
  cold.

  $ uname -a
  Linux HomeMegaUbuntu 4.2.0-17-generic #21-Ubuntu SMP Fri Oct 23 19:56:16 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily

  $ cpupower frequency-info
  analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.80 GHz
available frequency steps: 2.80 GHz, 2.80 GHz, 2.67 GHz, 2.53 GHz, 2.40 
GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 
GHz, 1.20 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 1.20 GHz and 2.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.20 GHz.
cpufreq stats: 2.80 GHz:11.93%, 2.80 GHz:0.00%, 2.67 GHz:0.40%, 2.53 
GHz:0.44%, 2.40 GHz:0.51%, 2.27 GHz:0.55%, 2.13 GHz:0.35%, 2.00 GHz:0.72%, 1.87 
GHz:0.84%, 1.73 GHz:1.00%, 1.60 GHz:2.16%, 1.47 GHz:4.61%, 1.33 GHz:16.83%, 
1.20 GHz:59.65%  (29241)
boost state support:
  Supported: yes
  Active: yes
  25500 MHz max turbo 4 active cores
  25500 MHz max turbo 3 active cores
  25500 MHz max turbo 2 active cores
  25500 MHz max turbo 1 active cores

  Tried intel_pstate but it is not supported for some reason on my
  machine ie the following does not work and I am left with driver:
  acpi-cpufreq

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable"

  Could not see ACPI Thermal Zones reported in dmesg
  $ dmesg | grep ACPI
  [0.00] BIOS-e820: [mem 0xbd78-0xbd78dfff] ACPI 
data
  [0.00] BIOS-e820: [mem 0xbd78e000-0xbd7c] ACPI NVS
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000F9B40 24 (v02 ACPIAM)
  [0.00] ACPI: XSDT 0xBD780100 6C (v01 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI: FACP 0xBD780290 F4 (v04 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in 
FADT/Gpe0Block: 128/64 (20150619/tbfadt-623)
  [0.00] ACPI: DSDT 0xBD780660 005B02 (v02 1  1000 
 INTL 20051117)
  [0.00] ACPI: FACS 0xBD78E000 40
  [0.00] ACPI: FACS 0xBD78E000 40
  [0.00] ACPI: APIC 0xBD780390 8C (v02 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI: MCFG 0xBD780420 3C (v01 DELL   OEMMCFG  
20101113 MSFT 0097)
  [0.00] ACPI: SLIC 0xBD780460 000176 (v01 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI: OSFR 0xBD7805E0 80 (v01 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI: OEMB 0xBD78E040 72 (v01 DELL   FX09 
20101113 MSFT 0097)
  [0.00] ACPI: HPET 0xBD78A660 38 (v01 DELL   OEMHPET  
20101113 MSFT 0097)
  [0.00] ACPI: ASF! 0xBD78A6A0 99 (v32 LEGEND I865PASF 
0001 INTL 20051117)
  [0.00] ACPI: SSDT 0xBD78F800 000363 (v01 DpgPmm CpuPm
0012 INTL 20051117)
  [0.00] ACPI: Local APIC address 0xfee0
  [0.00] ACPI: PM-Timer IO Port: 0x808
  [0.00] ACPI: Local APIC address 0xfee0
  [0.00] ACPI: INT_SRC_OVR 

[Kernel-packages] [Bug 1514964] Derivative package tracking bug

2015-11-10 Thread Brad Figg
This tracking bug was opened to be worked from linux-3.2.0-95.135 update
(bug 1514808)

-- 
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/1514964

Title:
  linux-armadaxp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-armadaxp package in Ubuntu:
  New
Status in linux-armadaxp source package in Precise:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 19:01 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 19:01 UTC
  kernel-stable-master-bug:1514808

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514964/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1514962] [NEW] linux-ti-omap4: -proposed tracker

2015-11-10 Thread Brad Figg
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 19:00 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 10. November 2015 19:00 UTC
kernel-stable-master-bug:1514808

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel)
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: armel block-proposed-precise kernel-release-tracking-bug precise

** Tags added: kernel-release-tracking-bug

** Tags added: armel

** Tags added: block-proposed-precise

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => ubuntu-armel-kernel (ubuntu-armel-kernel)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium


[Kernel-packages] [Bug 1514964] [NEW] linux-armadaxp: -proposed tracker

2015-11-10 Thread Brad Figg
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 10. November 2015 19:01 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 10. November 2015 19:01 UTC
kernel-stable-master-bug:1514808

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel)
 Status: New

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: armhf block-proposed-precise kernel-release-tracking-bug precise

** Tags added: kernel-release-tracking-bug

** Tags added: armhf

** Tags added: block-proposed-precise

** Also affects: linux-armadaxp (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: 

[Kernel-packages] [Bug 1514962] Derivative package tracking bug

2015-11-10 Thread Brad Figg
This tracking bug was opened to be worked from linux-3.2.0-95.135 update
(bug 1514808)

-- 
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/1514962

Title:
  linux-ti-omap4:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in linux-ti-omap4 source package in Precise:
  New

Bug description:
  This bug is for tracking the  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, 10. November 2015 19:00 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 10. November 2015 19:00 UTC
  kernel-stable-master-bug:1514808

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514962/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 880893] Re: CVE-2011-3347

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/880893

Title:
  CVE-2011-3347

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-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 source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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:
  New
Status in linux-lts-trusty source 

[Kernel-packages] [Bug 1514959] Re: package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade: package linux-headers-4.2.0-17 is not ready for configuration cannot configure (current status

2015-11-10 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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'.

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/v4.3-wily/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514959

Title:
  package linux-headers-4.2.0-17 4.2.0-17.21 failed to install/upgrade:
  package linux-headers-4.2.0-17 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is because my mistake, while process dpkg running I force stop
  that. so this what I get... unfortunately I do not how to solve that,
  even I try `sudo apt-get install --reinstall linux-image-`uname -r`
  just this is what I've got

   Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/26,4 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 324990 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.2.0-17-generic_4.2.0-17.21_i386.deb ...
  Examining /etc/kernel/preinst.d/
  run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Done.
  Unpacking linux-image-4.2.0-17-generic (4.2.0-17.21) over (4.2.0-17.21) ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  dpkg: error processing package linux-headers-4.2.0-17 (--configure):
   package linux-headers-4.2.0-17 is not ready for configuration
   cannot configure (current status 'half-installed')
  Setting up linux-image-4.2.0-17-generic (4.2.0-17.21) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Not updating initrd symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Not updating image symbolic links since we are being updated/reinstalled 
  (4.2.0-17.21 was configured last, according to dpkg)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  update-initramfs: Generating /boot/initrd.img-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.2.0-17-generic /boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.2.0-17-generic 
/boot/vmlinuz-4.2.0-17-generic
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Found kernel: /boot/vmlinuz-4.2.0-17-generic
  Found kernel: /boot/vmlinuz-4.2.0-16-generic
  Found kernel: /boot/memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  Errors were encountered while processing:
   linux-headers-4.2.0-17
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  just send an email to me (ryuffhan...@gmail.com) also can tell through
  gTalk/Hangouts if there's any advice to fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-17 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   linux-headers-4.2.0-17: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 891 F pulseaudio
irfan  1385 F pulseaudio
  Date: Wed Nov 11 01:35:35 2015
  

[Kernel-packages] [Bug 893148] Re: CVE-2011-4132

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/893148

Title:
  CVE-2011-4132

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 917706] Re: CVE-2012-0038

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/917706

Title:
  CVE-2012-0038

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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

[Kernel-packages] [Bug 1071314] Re: CVE-2012-4508

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty 

[Kernel-packages] [Bug 1089604] Re: CVE-2012-4461

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1089604

Title:
  CVE-2012-4461

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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-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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  New
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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 Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  New
Status in linux-lts-saucy source package in Trusty:
  New
Status in linux-lts-trusty source 

[Kernel-packages] [Bug 1131331] Re: CVE-2012-4542

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux-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-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-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 source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  New
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  New
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-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in 

[Kernel-packages] [Bug 1156759] Re: CVE-2012-6546

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1156757] Re: CVE-2012-6545

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1156757

Title:
  CVE-2012-6545

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1156768] Re: CVE-2012-6548

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1102374] Re: CVE-2013-0190

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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-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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source 

[Kernel-packages] [Bug 1370016] Re: CVE-2012-6657

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1370016

Title:
  CVE-2012-6657

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status 

[Kernel-packages] [Bug 1427399] Re: CVE-2012-6689

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1427399

Title:
  CVE-2012-6689

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status 

[Kernel-packages] [Bug 1156774] Re: CVE-2012-6549

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1123049] Re: CVE-2013-0268

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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-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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source 

[Kernel-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

2015-11-10 Thread Joe Barnett
this is also in the bluetooth (not bluetooth-next) repo:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b
, would it be possible to include in the wily kernel as a SAUCE patch at
this point?

-- 
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/1448566

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448566/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1156784] Re: CVE-2013-1860

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1156784

Title:
  CVE-2013-1860

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty 

[Kernel-packages] [Bug 1158263] Re: CVE-2013-1848

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1158263

Title:
  CVE-2013-1848

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty 

[Kernel-packages] [Bug 1167061] Re: CVE-2013-1928

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1167061

Title:
  CVE-2013-1928

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1188353] Re: CVE-2013-2146

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1188353

Title:
  CVE-2013-2146

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source 

[Kernel-packages] [Bug 1187732] Re: CVE-2013-2141

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1187732

Title:
  CVE-2013-2141

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1170064] Re: CVE-2013-1956

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1170064

Title:
  CVE-2013-1956

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in Trusty:
  

[Kernel-packages] [Bug 1172363] Re: CVE-2013-3076

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1172363

Title:
  CVE-2013-3076

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1172365] Re: CVE-2013-3222

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1172365

Title:
  CVE-2013-3222

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1514976] [NEW] package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2015-11-10 Thread rick kinnear
Public bug reported:

not sure what other information would be useful

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
Date: Tue Nov 10 07:56:50 2015
DpkgTerminalLog: Log started: 2015-11-10  07:54:30
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2015-09-22 (49 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: linux-lts-vivid
Title: package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1514976

Title:
  package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  not sure what other information would be useful

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Tue Nov 10 07:56:50 2015
  DpkgTerminalLog: Log started: 2015-11-10  07:54:30
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-09-22 (49 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: linux-lts-vivid
  Title: package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1514976/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 949905] Re: CVE-2012-1097

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/949905

Title:
  CVE-2012-1097

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  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-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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 

[Kernel-packages] [Bug 952828] Re: CVE-2012-1146

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/952828

Title:
  CVE-2012-1146

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-raring package in Ubuntu:
  Won't Fix
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-backport-maverick source package in Maverick:
  Invalid
Status in linux-lts-backport-natty source package in Maverick:
  Invalid
Status in linux-lts-backport-oneiric source package in Maverick:
  Invalid
Status in linux-lts-backport-maverick source package in Natty:
  Invalid
Status in linux-lts-backport-natty source package in Natty:
  Invalid
Status in linux-lts-backport-oneiric source package in Natty:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Won't Fix
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-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 947997] Re: CVE-2012-1090

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/947997

Title:
  CVE-2012-1090

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta 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-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  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-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  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:
  New
Status in 

[Kernel-packages] [Bug 1143817] Re: CVE-2013-1774

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1143815] Re: CVE-2013-1767

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1143815

Title:
  CVE-2013-1767

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  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-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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source 

[Kernel-packages] [Bug 1134513] Re: CVE-2013-1772

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source 

[Kernel-packages] [Bug 1206200] Re: CVE-2013-1060

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1206200

Title:
  CVE-2013-1060

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-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:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-lts-wily source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in 

[Kernel-packages] [Bug 1213824] Re: CVE-2013-1059

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1213824

Title:
  CVE-2013-1059

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
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:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  New
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 1198294] Re: CVE-2013-2234

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1198294

Title:
  CVE-2013-2234

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty 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-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty 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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  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-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  New
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in 

[Kernel-packages] [Bug 1514233] Re: Ubuntu 15.10 freezes during operation.

2015-11-10 Thread Joseph Salisbury
** 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/1514233

Title:
  Ubuntu 15.10 freezes during operation.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu freezes during video playback operation when window opened
  MAXIMISED.

  The freeze occurs with Firefox 42.0, VideoLAN or Totem Movie Player,
  DOES NOT occur if window playing video is resized to anything but
  maximised.

  It just freezes occasionally since upgrade.
  Upgrade to wild wily.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10

  Uname: Linux 4.2.0-17-generic x86_64

  Architecture: amd64

  UpgradeStatus: Upgraded to wily on 2015-11-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514233/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1172403] Re: CVE-2013-3235

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1172403

Title:
  CVE-2013-3235

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  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 source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  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:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in 

[Kernel-packages] [Bug 1279982] Re: CVE-2013-4736

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1279982

Title:
  CVE-2013-4736

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  

[Kernel-packages] [Bug 1235136] Re: CVE-2013-4387

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1235136

Title:
  CVE-2013-4387

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
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:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  

[Kernel-packages] [Bug 1514233] Re: Ubuntu 15.10 freezes during operation.

2015-11-10 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 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'.

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/v4.3-wily/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1514233

Title:
  Ubuntu 15.10 freezes during operation.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu freezes during video playback operation when window opened
  MAXIMISED.

  The freeze occurs with Firefox 42.0, VideoLAN or Totem Movie Player,
  DOES NOT occur if window playing video is resized to anything but
  maximised.

  It just freezes occasionally since upgrade.
  Upgrade to wild wily.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10

  Uname: Linux 4.2.0-17-generic x86_64

  Architecture: amd64

  UpgradeStatus: Upgraded to wily on 2015-11-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514233/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 898003] Re: usbip source is maintained in kernel tree now

2015-11-10 Thread Mauro
For Trusty, you must compile usbip from sources yourself. I did it a
couple of times in Linux Mint 17 (based on Trusty) and Debian 7. Here is
what I ended up with:

On the Linux server that will share the USB devices or on any Linux client that 
will need to access shared devices on other servers:
- download the kernel source: apt-get install linux-source-3.13.0 (replace with 
your desired kernel version)
- extract the usbip sources from the kernel source tarball (e.g.: 
/usr/src/linux-source-3.13.0.tar.bz2): they should be under 
drivers/staging/usbip (or something like that); for instance, extract them to 
/root/usbip
- find where the file usb.ids from usbutils package is located in your system: 
apt-file search usb.ids (in my case it's at /usr/share/misc/usb.ids)
- enter /root/usbip/userspace to build the userspace tools:
./autogen.sh
./configure --with-usbids-dir=/usr/share/misc
make install
  (replace the usb.ids path as needed)
- if the build fails, you may need some additional libraries; take a look at 
the README file; for instance, I needed to install libtool (apt-get install 
libtool)
- the executable files /usr/local/sbin/usbip and /usr/local/sbin/usbipd will be 
installed, as well as some libraries into /usr/local/lib
- try to run usbip or usbipd to see if they complain about something; if they 
say some library is missing, try to launch them by preceding with a proper 
LD_LIBRARY_PATH setting; for instance, you may need to run usbip in this way:
  LD_LIBRARY_PATH=/usr/local/lib; usbip

Until now, we've compiled the userspace tools required to control usbip; then, 
we need to compile the kernel modules, too. The following is again needed on 
the Linux server that will share the USB devices:
- the kernel headers are required: 
  apt-get install linux-headers-`uname -r`
  cd /usr/src/linux-headers-`uname -r`
  make M=/root/usbip
  (replace the path after M= with the folder where you extracted the usbip 
sources in the previous steps)
- the kernel modules will be installed in the usbip folder; to load them:
  modprobe usbip-core.ko
  modprobe usbip-host.ko

After you've loaded the kernel modules, type:
usbipd -D

Then, you can start to use the usbip tool to list the attached USB
modules and bind them.

If you want to load the kernel modules automatically on system startup:
sudo echo usbip-core >>/etc/modules
sudo echo usbip-host >>/etc/modules

If you want to start the usbipd daemon automatically on system startup, one way 
to achieve this is to edit /etc/rc.local and add the following line before the 
line with "exit 0":
/usr/local/sbin/usbipd -D
(remember the LD_LIBRARY_PATH thing, if you determined it's needed)

Please note that if you plan to use Windows clients, you need to try the
LATEST compiled binaries, otherwise they will fail to work. When I last
used usbip, I had to use some binaries compiled by users posting on the
usbip forum, because the one published on the usbip website were
outdated and did not work. That's another huge problem with this tool, I
think.

Hope this helps someone.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/898003

Title:
  usbip source is maintained in kernel tree now

Status in linux package in Ubuntu:
  Fix Released
Status in usbip package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Fix Released
Status in usbip source package in Utopic:
  Confirmed

Bug description:
  Both the userspace and kernel module parts of usbip are in the linux
  kernel tree now.  The source used in this package is quite old.

  I'm not sure how to best handle the packaging aspects here -- I
  imagine that it would be undesirable for usbip to be built as a side
  effect of the main kernel package build, because then the kernel
  package build would be even slower and usbip is probably not updated
  enough to justify that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898003/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1252419] Re: CVE-2013-4511

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Low

-- 
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/1252419

Title:
  CVE-2013-4511

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
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-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status 

[Kernel-packages] [Bug 1254901] Re: CVE-2013-6282

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1254901

Title:
  CVE-2013-6282

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid

[Kernel-packages] [Bug 1270104] Re: CVE-2013-6123

2015-11-10 Thread Steve Beattie
** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
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/1270104

Title:
  CVE-2013-6123

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Won't Fix
Status in linux-lts-backport-natty package in Ubuntu:
  Won't Fix
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Won't Fix
Status in linux-lts-backport-natty source package in Precise:
  Won't Fix
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Won't Fix
Status in linux-lts-backport-natty source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Won't Fix
Status in linux-lts-backport-natty source package in Raring:
  Won't Fix
Status in linux-lts-backport-maverick source package in Saucy:
  Won't Fix
Status in linux-lts-backport-natty source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Won't Fix
Status in linux-lts-backport-natty source package in Trusty:
  Won't Fix
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in 

  1   2   3   4   5   >