[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 141, failed: 0

2017-06-23 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-24_04-48-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1700213] Re: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1700211 ***
https://bugs.launchpad.net/bugs/1700211

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1700211, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1700211
   package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 09:21:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-19 (124 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago)

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

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


[Kernel-packages] [Bug 1700213] [NEW] package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-23 Thread Prakash
*** This bug is a duplicate of bug 1700211 ***
https://bugs.launchpad.net/bugs/1700211

Public bug reported:

upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.11
ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
Uname: Linux 3.13.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sat Jun 24 09:21:25 2017
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-02-19 (124 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: linux-firmware
Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 09:21:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-19 (124 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago)

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

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


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

2017-06-23 Thread Joseph Salisbury
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/1700207

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを
  '/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました
  (デバイスに空き領域がありません)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  startedo

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  o  1637 F pulseaudio
  Date: Sat Jun 24 12:50:11 2017
  ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
  InstallationDate: Installed on 2016-12-09 (196 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BIOSTAR Group H61MH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: H61MH
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: H61MH
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 19, failed: 1

2017-06-23 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-24_03-31-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-06-23 Thread Joseph Salisbury
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/1700206

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを
  '/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました
  (デバイスに空き領域がありません)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  startedo

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  o  1637 F pulseaudio
  Date: Sat Jun 24 12:50:11 2017
  ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
  InstallationDate: Installed on 2016-12-09 (196 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BIOSTAR Group H61MH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: H61MH
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: H61MH
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1685776] Re: kernel tried to execute NX-protected page - exploit attempt?

2017-06-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  kernel tried to execute NX-protected page - exploit attempt?

Status in linux package in Ubuntu:
  Expired

Bug description:
  I connected the notebook to external monitor, everything worked fine
  for a couple of seconds and then the notebook froze. When I browsed
  syscat logs I have found this:

  kernel tried to execute NX-protected page - exploit attempt?

  Hopefully the ubuntu-bug tool will attach relevant information, so
  here's a snippet from the syscat logs:

  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321576] kernel tried to execute 
NX-protected page - exploit attempt? (uid: 0)
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321633] BUG: unable to handle 
kernel paging request at 8a079fa24e08
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321680] IP: 0x8a079fa24e08
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321703] PGD 56e62c067 
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321703] PUD 9bf168063 
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321722] PMD 99fbe0063 
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321740] PTE 80099fa24163
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321758] 
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321791] Oops: 0011 [#1] SMP
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.321812] Modules linked in: veth 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_
  filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc aufs ccm 
cmac rfcomm bnep arc4 iwlmvm snd_hda_codec_realtek snd_hda_codec_generic 
intel_rapl mac80211 x86_pkg_temp_thermal intel_powerclamp th
  inkpad_acpi snd_hda_intel snd_hda_codec nvram snd_usb_audio snd_hda_core 
snd_usbmidi_lib snd_hwdep uvcvideo snd_seq_midi snd_seq_midi_event snd_rawmidi 
videobuf2_vmalloc coretemp videobuf2_memops videobuf2_v4l2
   kvm_intel videobuf2_core joydev snd_seq kvm snd_pcm iwlwifi videodev 
snd_seq_device irqbypass snd_timer btusb media btrtl input_leds btbcm 
rtsx_pci_ms intel_cstate btintel cfg80211 bluetooth snd memstick serio
  _raw soundcore
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322290]  intel_rapl_perf mac_hid 
mei_me mei shpchp intel_pch_thermal cuse ib_iser rdma_cm iw_cm ib_cm ib_core 
configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_i
  scsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 mult
  ipath linear hid_generic usbhid hid rtsx_pci_sdmmc crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel nouveau i915 pcbc aesni_intel mxm_wmi ttm 
aes_x86_64 i2c_algo_bit crypto_simd glue_helper drm_kms_helper cryp
  td syscopyarea e1000e psmouse sysfillrect sysimgblt fb_sys_fops ptp pps_core 
ahci drm rtsx_pci libahci wmi video fjes
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322753] CPU: 0 PID: 2141 Comm: 
InputThread Not tainted 4.10.0-19-generic #21-Ubuntu
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322814] Hardware name: LENOVO 
20EN0005MS/20EN0005MS, BIOS N1EET65W (1.38 ) 02/09/2017
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322870] task: 8a087119dc00 
task.stack: af24c6ca8000
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322914] RIP: 
0010:0x8a079fa24e08
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322949] RSP: 0018:af24c6caba30 
EFLAGS: 00010206
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.322992] RAX: 8a061c05cdf0 RBX: 
8a0803554400 RCX: c0832fa0
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323048] RDX: 7fff RSI: 
0001 RDI: 8a081bb91000
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323108] RBP: af24c6caba58 R08: 
 R09: 8a0868ef1000
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323164] R10: 8a086c852480 R11: 
8a0868d68808 R12: 8a081bb91000
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323209] R13: 0001 R14: 
7fff R15: 0001
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323255] FS:  
7f69261d1700() GS:8a08a140() knlGS:
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323305] CS:  0010 DS:  ES: 
 CR0: 80050033
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323340] CR2: 8a079fa24e08 CR3: 
000a6adf6000 CR4: 003406f0
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323383] DR0:  DR1: 
 DR2: 
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323425] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Apr 24 14:21:52 mavi-vaadin kernel: [21312.323467] Call Trace:
  Apr 24 14:21:52 

[Kernel-packages] [Bug 1700206] [NEW] package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを '/boot/vmlinuz-4.4.0-81-generic.dpkg-n

2017-06-23 Thread okawa tukio
Public bug reported:

startedo

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-81-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  o  1637 F pulseaudio
Date: Sat Jun 24 12:50:11 2017
ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
InstallationDate: Installed on 2016-12-09 (196 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: BIOSTAR Group H61MH
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
RfKill:
 
SourcePackage: linux
StagingDrivers: r8188eu
Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: H61MH
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 6.0
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: H61MH
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-package staging 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/1700206

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを
  '/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました
  (デバイスに空き領域がありません)

Status in linux package in Ubuntu:
  New

Bug description:
  startedo

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  o  1637 F pulseaudio
  Date: Sat Jun 24 12:50:11 2017
  ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
  InstallationDate: Installed on 2016-12-09 (196 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BIOSTAR Group H61MH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: H61MH
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: H61MH
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1700207] [NEW] package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを '/boot/vmlinuz-4.4.0-81-generic.dpkg-n

2017-06-23 Thread okawa tukio
Public bug reported:

startedo

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-81-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  o  1637 F pulseaudio
Date: Sat Jun 24 12:50:11 2017
ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
InstallationDate: Installed on 2016-12-09 (196 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: BIOSTAR Group H61MH
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
RfKill:
 
SourcePackage: linux
StagingDrivers: r8188eu
Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: None
dmi.board.name: H61MH
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 6.0
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: H61MH
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-package staging 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/1700207

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを
  '/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました
  (デバイスに空き領域がありません)

Status in linux package in Ubuntu:
  New

Bug description:
  startedo

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  o  1637 F pulseaudio
  Date: Sat Jun 24 12:50:11 2017
  ErrorMessage: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  HibernationDevice: RESUME=UUID=359278c4-06cf-4589-afad-5a58d2f86b3b
  InstallationDate: Installed on 2016-12-09 (196 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BIOSTAR Group H61MH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic 
root=/dev/mapper/xubuntu--vg-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 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: './boot/vmlinuz-4.4.0-81-generic' の展開済みデータを 
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new' にコピーできません: 書き込みに失敗しました 
(デバイスに空き領域がありません)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: H61MH
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/05/2011:svnBIOSTARGroup:pnH61MH:pvr6.0:rvnBIOSTARGroup:rnH61MH:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: H61MH
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 19, failed: 2

2017-06-23 Thread Brad Figg
tests ran:  19, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-23_19-26-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699064] Re: linux: 4.4.0-82.105 -proposed tracker

2017-06-23 Thread Po-Hsu Lin
4.4.0-82.105 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  ubuntu_kvm_unit_tests - pku, svm, hyperv_clock failed, not regression
  xfstests - btrfs and xfs test failed, issue seen before, not regression

Issue to note in arm64:
  hwclock - failed to change time, issue seen before, not regression
  ubuntu_qrt_apparmor - sysctl read failed, function not implemented, issue 
seen in 4.4.0-80, not regression, bug 1700127
  ubuntu_zfs_xfs_generic - failed with test 079, issue seen before, not 
regression

Issue to note in i386:
  None

Issue to note in s390x:
  None

Issue to note in s390x (Ubuntu on LPAR):
  aio_dio_bugs - event res -22, issue seen before, not regression
  libhugetlbfs - 11 failures, including one stack_grow_into_huge new failure, 
bug 1700123
  scrashme - failed to build, bug 168924
  ubuntu_blktrace_smoke_test - 1 passed, 3 failed, issue seen in 4.4.0-80, not 
regression
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed, issue seen 
before
  ubuntu_lxc - lxc-test-ubuntu failed to start network, issue seen before
  ubuntu_seccomp - failed to build

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, issue seen before, not regression
  libhugetlbfs - 11 failures, including one stack_grow_into_huge new failure, 
bug 1700123
  scrashme - failed to build, bug 168924
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed, issue seen 
before
  ubuntu_lxc - lxc-test-ubuntu failed to start network, issue seen before
  ubuntu_seccomp - failed to build

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, issue seen before, not regression
  libhugetlbfs - IOError: [Errno 524] Unknown error 524, issue seen before
  scrashme - failed to build, bug 168924
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed, issue seen 
before
  ubuntu_lxc - lxc-test-ubuntu failed to start network, issue seen before
  ubuntu_seccomp - failed to build

4.4.0-82.105 - lowlatency
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  ubuntu_kvm_unit_tests - pku, svm, hyperv_clock failed, not regression
  ubuntu_lxc - passed on 2 nodes failed on 1
  xfstests - btrfs and xfs test failed, issue seen before, not regression

Issue to note in i386:
  monotonic_time - gtod failed, passed after retest

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.4.0-82.105 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1699066
  derivatives: 1699067,1699068,1699069,1699070,1699071
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Joshua R. Poulson
Applications that use jsvc can increase their thread stack space with
-Xss1280k or larger (Red Hat, for example, suggested -Xss2m which is
much larger).

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

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


Re: [Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Arthur Edwards
Interestingly, octave 4.2 comes up successfully under 4.40-81 under Ubuntu
16.04.


On Jun 23, 2017 4:45 PM, "Norbert" <1699...@bugs.launchpad.net> wrote:

> Octave in Trusty is affected too (see bug 1699594).
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1699594).
> https://bugs.launchpad.net/bugs/1699772
>
> Title:
>   linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
>   Regression: many user-space apps crashing
>
> Status in commons-daemon package in Ubuntu:
>   Confirmed
> Status in eclipse package in Ubuntu:
>   Confirmed
> Status in imagej package in Ubuntu:
>   Confirmed
> Status in libreoffice package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Confirmed
> Status in octave package in Ubuntu:
>   Confirmed
> Status in scilab package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)
>
>   linux-image-4.4.0-81-generic appears to contain a regression, probably
>   related to the CVE-2017-1000364 fix backport / patch.
>
>   Using this kernel, the Oracle Java browser plugin always crashes
>   during stack-related actions on initialization. This means, the plugin
>   completely stopped working.
>
>
>   It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to
> CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which
> also contains a fix for CVE-2017-1000364.
>
>
>   uname -a:
>
>   > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
>   UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>
>   I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
>   well as Iceweasel / Firefox/3.5.16 in a chroot.
>
>   Using linux-image-4.4.0-81-generic it crashes in all combinations
>   while with both other kernels it works.
>
>
>   I was not able to obtain any detailed crash information from Firefox
> 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a
> stack trace which shows the relation to stack operations performed by the
> plugin, even without proper debug symbols:
>
>
>   > (gdb) bt full
>   > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from
> /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
>   > No symbol table info available.
>   > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*,
> unsigned char*) ()
>   >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
>   > No symbol table info available.
>   > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from
> /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
>   > No symbol table info available.
>   > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from
> /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
>   > No symbol table info available.
>   > #4  
>
>
>   I first assumed a bug in the Java plugin, but it works fine in Linux
> 4.11.6.
>
>
>   The crash will be triggered by any applet, for example the test applet
> at:
>
>   * https://java.com/en/download/installed8.jsp
>
>
>   I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow
> apparently does not allow me to use apport to report this bug:
>
>   > $ LANG= apport-cli linux-image-4.4.0-81-generic
>   >
>   > *** Collecting problem information
>   >
>   > The collected information can be sent to the developers to improve the
>   > application. This might take a few minutes.
>   > .
>   >
>   > *** Problem in linux-image-4.4.0-81-generic
>   >
>   > The problem cannot be reported:
>   >
>   > This is not an official KDE package. Please remove any third party
> package and try again.
>
>   If someone can tell me how to get apport working for this package, I
>   can use it to collect additional information, but (unfortunately?) the
>   problem should be fairly easy to reproduce...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/commons-daemon/
> +bug/1699772/+subscriptions
>

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

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-06-23 Thread dann frazier
** Description changed:

  Note: Updates are being staged at ppa:dannf/arm64-kdump.
  
  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.
  
  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger
  
  Crash dump should occur, with artifacts collected in /var/crash.
  
  If you want to verify that the dump is usable, install the corresponding
  linux-image--dbgsym package and run:
  
  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.
  
  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.
  
  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:
  
  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).
  
  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.
  
  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).
  
  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)
  
  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.
  
  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:
  
  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -
  
  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.
  
  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.
  
  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my test
  results show no change there. amd64 worked before, and continues to work
  with these changes.
  
  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:
  
  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.
  
  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.
  
  kexec-add-generic-helper-to-add-to-memoryq_regions.patch,
  kexec-add-mem_regions-sorting-implementation.patch,
  kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch,
  kexec-fix-mem_regions_sort.patch:
  These patches only add new functions, which will be used by later patches.
  
  kexec-arch-i386-Add-support-for-KASLR-memory-randomi.patch:
  This is a bug fix or i386 that allows later patches to apply w/o backporting.
  kdump support for i386 is apparently broken for the yakkety kernel (see LP: 
#1699874) so, if this introduces a regression, it won't be detectable.
  (I checked to see if this *fixes* i386 crashdumps - it does not).
  
  Note that, while makedumpfile in >= zesty is new enough to work on arm64, the 
yakkety version does not. kdump-tools falls back to copying the entire vmcore, 
which is what I tested.
  As with zesty, I have tested this update on both i386 and amd64 VMs. i386 
crashes do not currently work in yakkety, and my test results show no change 
there. amd64 worked before, and continues to work with these changes.
+ 
+ = xenial =
+ The patchset needed for xenial is identical to the patchset for yakkety. The 
only additional change is to add arm64 to the list of archs that get a 
/etc/default/grub.d snippet (in yakkety that snippet moved over to 
kdump-tools), and that has negligible regression risk for !arm64.

** Description changed:

  Note: Updates are being staged at ppa:dannf/arm64-kdump.
  
  [Impact]
  It is not possible to collect a 

[Kernel-packages] [Bug 305628] could that be real?

2017-06-23 Thread mfranze
*** This bug is a duplicate of bug 252900 ***
https://bugs.launchpad.net/bugs/252900

Hello!

I've just seen something  really  weird  and I  decided to ask you
whether  that is real  or  not.  Just take a  look http://bit.do/dxbH7

Rushing, Matteo Franze


Sent from Mail for Windows 10

** Attachment added: "9987F75A360A0F12C00A7E12C7C45B26.jpg"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4901826/+files/9987F75A360A0F12C00A7E12C7C45B26.jpg

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

Title:
  package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to
  install/upgrade: impossibile creare il link per la copia di sicurezza
  di `./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova
  versione: Funzione non permessa

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems authorization missing to create a link

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ErrorMessage: impossibile creare il link per la copia di sicurezza di 
`./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova versione: 
Funzione non permessa
  Package: linux-image-2.6.27-7-generic 2.6.27-7.14
  ProcCmdLine: User Name=UUID=420E-19E7 loop=/hostname/disks/home/username.disk 
ro ROOTFLAGS=sync quiet splash
  ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
  SourcePackage: linux
  Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to 
install/upgrade: impossibile creare il link per la copia di sicurezza di 
`./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova versione: 
Funzione non permessa

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

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


[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-06-23 Thread dann frazier
** Description changed:

  Note: Updates are being staged at ppa:dannf/arm64-kdump.
  
  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.
  
  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger
  
  Crash dump should occur, with artifacts collected in /var/crash.
  
  If you want to verify that the dump is usable, install the corresponding
  linux-image--dbgsym package and run:
  
  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.
  
- crash should successfully load, placing you at a "crash>" prompt. At
- that prompt, you can issue the 'bt' command to see a backtrace.
+ crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
+ Note: you need crash from zesty (7.1.8-1ubuntu1) or later.
  
  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:
  
  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).
  
  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.
  
  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).
  
  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)
  
  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.
  
  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:
  
  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -
  
  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.
  
  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.
  
  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my test
  results show no change there. amd64 worked before, and continues to work
  with these changes.
  
  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:
  
  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.
  
  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.
  
  kexec-add-generic-helper-to-add-to-memoryq_regions.patch,
  kexec-add-mem_regions-sorting-implementation.patch,
  kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch,
  kexec-fix-mem_regions_sort.patch:
  These patches only add new functions, which will be used by later patches.
  
  kexec-arch-i386-Add-support-for-KASLR-memory-randomi.patch:
  This is a bug fix or i386 that allows later patches to apply w/o backporting.
  kdump support for i386 is apparently broken for the yakkety kernel (see LP: 
#1699874) so, if this introduces a regression, it won't be detectable.
  (I checked to see if this *fixes* i386 crashdumps - it does not).
  
  Note that, while makedumpfile in >= zesty is new enough to work on arm64, the 
yakkety version does not. kdump-tools falls back to copying the entire vmcore, 
which is what I tested.
  As with zesty, I have tested this update on both i386 and amd64 VMs. i386 
crashes do not currently work in yakkety, and my test results show no change 
there. amd64 worked before, and continues to work with these changes.

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in 

[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Norbert
Octave in Trusty is affected too (see bug 1699594).

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

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: octave (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/1699772

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Norbert
** Also affects: octave (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/1699772

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1511511] Re: USB keyboard stops working after pressing extended key

2017-06-23 Thread dewes
I can confirm that the same happens on Cougar 700k. Also tried on Fedora
25.

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

Title:
  USB keyboard stops working after pressing extended key

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB keyboard Cougar K500 gaming keyboard has some additional extended
  keys, all of them making the keyboard stop responding if pressed under
  linux. The device is recovered only by unplugging the USB and plugging
  it again.

  The keyboard has been tested under Ubuntu 14.04.3 LTS, Ubuntu 15.04
  and Ubuntu 15.10 (the latter running as virtualbox guest). All tests
  failed with exactly the same behaviour.

  USB ID is: "060b:500a Solid Year".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pinfli 1055 F pulseaudio
  Date: Thu Oct 29 19:33:23 2015
  HibernationDevice: RESUME=UUID=f68f4b91-ea68-4e4b-9a10-8ed5bca2efbe
  InstallationDate: Installed on 2015-10-24 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 060b:500a Solid Year 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=523dfd8b-b825-47e3-a116-cb85f901386c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-06-23 Thread Christian Adamski
I'm confirming this issue on a DELL XPS 15 as well. It's still present
with 4.10.0.24.

My workaround is to bot 4.10.0.21

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1699064] Re: linux: 4.4.0-82.105 -proposed tracker

2017-06-23 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 4.4.0-82.105 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1699066
  derivatives: 1699067,1699068,1699069,1699070,1699071
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-06-23 Thread Joseph Salisbury
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/1700185

Title:
  package linux-image-4.10.0-24-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I clicked the Ununtu Software tab, it indicated there was one
  update.  When I clicked the Update command button it stayed selected
  but did not perform an action.  An hour later, it was still selected
  without performing an action.

  Got the error during an apt-get update

  OS:

 Ubuntu 17.04

  System:

 PC:Panasonic Toughbook CF-30FTSAZAM
 Memory:4 Gib
 CPU:   Intel® Core™2 Duo CPU L7500 @ 1.60GHz × 2  64 bit
 Graphics:  Intel® 965GM
 Disk:  152.2 Gb

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vince  1823 F pulseaudio
  Date: Fri Jun 23 16:21:17 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=cfd0cdbd-3f45-43ce-844c-4ed8fc8b337c
  InstallationDate: Installed on 2017-05-25 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-30FTSAZAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-24-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.00L11
  dmi.board.name: CF30-2
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/26/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-30FTSAZAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF30-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-30FTSAZAM
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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


[Kernel-packages] [Bug 1700185] Re: package linux-image-4.10.0-24-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-24-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I clicked the Ununtu Software tab, it indicated there was one
  update.  When I clicked the Update command button it stayed selected
  but did not perform an action.  An hour later, it was still selected
  without performing an action.

  Got the error during an apt-get update

  OS:

 Ubuntu 17.04

  System:

 PC:Panasonic Toughbook CF-30FTSAZAM
 Memory:4 Gib
 CPU:   Intel® Core™2 Duo CPU L7500 @ 1.60GHz × 2  64 bit
 Graphics:  Intel® 965GM
 Disk:  152.2 Gb

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vince  1823 F pulseaudio
  Date: Fri Jun 23 16:21:17 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=cfd0cdbd-3f45-43ce-844c-4ed8fc8b337c
  InstallationDate: Installed on 2017-05-25 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-30FTSAZAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-24-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.00L11
  dmi.board.name: CF30-2
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/26/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-30FTSAZAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF30-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-30FTSAZAM
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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


[Kernel-packages] [Bug 1700185] [NEW] package linux-image-4.10.0-24-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Vincent Grienti
Public bug reported:

When I clicked the Ununtu Software tab, it indicated there was one
update.  When I clicked the Update command button it stayed selected but
did not perform an action.  An hour later, it was still selected without
performing an action.

Got the error during an apt-get update

OS:

   Ubuntu 17.04

System:

   PC:Panasonic Toughbook CF-30FTSAZAM
   Memory:4 Gib
   CPU:   Intel® Core™2 Duo CPU L7500 @ 1.60GHz × 2  64 bit
   Graphics:  Intel® 965GM
   Disk:  152.2 Gb

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-24-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vince  1823 F pulseaudio
Date: Fri Jun 23 16:21:17 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=cfd0cdbd-3f45-43ce-844c-4ed8fc8b337c
InstallationDate: Installed on 2017-05-25 (28 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-30FTSAZAM
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta3-4ubuntu2.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.10.0-24-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.00L11
dmi.board.name: CF30-2
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/26/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-30FTSAZAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF30-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-30FTSAZAM
dmi.product.version: 002
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-24-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I clicked the Ununtu Software tab, it indicated there was one
  update.  When I clicked the Update command button it stayed selected
  but did not perform an action.  An hour later, it was still selected
  without performing an action.

  Got the error during an apt-get update

  OS:

 Ubuntu 17.04

  System:

 PC:Panasonic Toughbook CF-30FTSAZAM
 Memory:4 Gib
 CPU:   Intel® Core™2 Duo CPU L7500 @ 1.60GHz × 2  64 bit
 Graphics:  Intel® 965GM
 Disk:  152.2 Gb

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vince  1823 F pulseaudio
  Date: Fri Jun 23 16:21:17 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=cfd0cdbd-3f45-43ce-844c-4ed8fc8b337c
  InstallationDate: Installed on 2017-05-25 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-30FTSAZAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no

[Kernel-packages] [Bug 1700077] Re: aacraid driver may return uninitialized stack data to userspace

2017-06-23 Thread Seth Forshee
Applied to artful/master-next and unstable/master. Patch sent for zesty:

https://lists.ubuntu.com/archives/kernel-team/2017-June/085128.html

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  aacraid driver may return uninitialized stack data to userspace

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent aacraid backports introduce potential information
  leaks, where some stack allocated memory may be copied to userspace
  without initialization.

  Fix: Clear out the affected memory before using it to ensure that none
  is left uninitialized.

  Test Case: None. Code review should be sufficient to validate the
  changes.

  Regression Potential: Negligible. The patch simply memsets some
  structs to clear them out prior to any other use.

  ---

  aac_send_raw_srb() and aac_get_hba_info() both copy the contents of
  stack variables to userspace when some of this memory may be
  uninitialized. The memory should be zeroed out initially to prevent
  this.

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

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


[Kernel-packages] [Bug 1699035] gonzo (amd64) - tests ran: 64, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_19-54-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699940] DuplicateSignature.txt

2017-06-23 Thread Brian Murray
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1699940/+attachment/4901749/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rolland1530 F pulseaudio
  Date: Thu Jun 22 13:56:40 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=134f2875-6fbc-4054-915d-163b4887627d
  InstallationDate: Installed on 2016-09-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta2-36ubuntu3.11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd05/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1699940] Re: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1699940/+attachment/4901272/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rolland1530 F pulseaudio
  Date: Thu Jun 22 13:56:40 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=134f2875-6fbc-4054-915d-163b4887627d
  InstallationDate: Installed on 2016-09-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic 
root=/dev/mapper/ubuntu--vg-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 2.02~beta2-36ubuntu3.11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd05/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1700154] DuplicateSignature.txt

2017-06-23 Thread Brian Murray
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700154/+attachment/4901747/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Unable to update due to "unmet dependencies". Tried both sudo get-apt
  updates and sudo get-apt -f and then running update again.  Still not
  fixed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   1637 F pulseaudio
  Date: Fri Jun 23 11:33:45 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=268a3159-ba29-4b19-b292-8a7491f8bec2
  InstallationDate: Installed on 2016-07-22 (335 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gateway NE56R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=5a4a4734-28c1-43cd-a912-27bf18ee52fa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Gateway
  dmi.bios.version: V2.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V2.04
  dmi.modalias: 
dmi:bvnGateway:bvrV2.04:bd12/16/2013:svnGateway:pnNE56R:pvrV2.04:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.04:
  dmi.product.name: NE56R
  dmi.product.version: V2.04
  dmi.sys.vendor: Gateway

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

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


[Kernel-packages] [Bug 1700154] Re: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700154/+attachment/4901724/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Unable to update due to "unmet dependencies". Tried both sudo get-apt
  updates and sudo get-apt -f and then running update again.  Still not
  fixed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   1637 F pulseaudio
  Date: Fri Jun 23 11:33:45 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=268a3159-ba29-4b19-b292-8a7491f8bec2
  InstallationDate: Installed on 2016-07-22 (335 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gateway NE56R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=5a4a4734-28c1-43cd-a912-27bf18ee52fa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Gateway
  dmi.bios.version: V2.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V2.04
  dmi.modalias: 
dmi:bvnGateway:bvrV2.04:bd12/16/2013:svnGateway:pnNE56R:pvrV2.04:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.04:
  dmi.product.name: NE56R
  dmi.product.version: V2.04
  dmi.sys.vendor: Gateway

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

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


[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-06-23 Thread dann frazier
** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Confirmed
Status in kexec-tools source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At
  that prompt, you can issue the 'bt' command to see a backtrace.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

  kexec-add-generic-helper-to-add-to-memoryq_regions.patch,
  kexec-add-mem_regions-sorting-implementation.patch,
  kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch,
  kexec-fix-mem_regions_sort.patch:
  These patches only add new functions, which will be used by later patches.

  kexec-arch-i386-Add-support-for-KASLR-memory-randomi.patch:
  This is a bug fix or i386 that allows later patches to apply w/o backporting.
  kdump support for i386 is apparently broken for the yakkety kernel (see LP: 
#1699874) so, if this introduces a regression, it won't be detectable.
  (I checked to see if this *fixes* 

[Kernel-packages] [Bug 1699681] Re: 16.04 , apparmor denies dbus communications

2017-06-23 Thread sles
Looks like we need more fine grained version, but this works:

dbus(send)
 bus=system,

in   profile su {

btw, looks like there is bug in apparmor, because operation is denied even if 
flags=(complain) is set.


** 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/1699681

Title:
  16.04 , apparmor denies dbus communications

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Here is log:

  [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="Hello" mask="send" 
name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? 
terminal=?

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

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


[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 37, failed: 4

2017-06-23 Thread Brad Figg
tests ran:  37, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-23_18-26-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699035] gonzo (amd64) - tests ran: 2, failed: 0

2017-06-23 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_19-01-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Norbert
Also you can check comments on bug 1698919.
The (incomplete) list of affected applications include:
* LPCxpresso (see https://community.nxp.com/thread/453939 )
* RMongo (see https://stackoverflow.com/a/44699417 )
* Ubiquity UniFi (see
https://community.ubnt.com/t5/UniFi-Wireless/UniFi-Controller-failed-after-dist-upgrade/td-p/1967779
)

** Tags added: trusty

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

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Norbert
Scilab is affected too. It uses openjdk-8.
See bug 1699892 for details.
Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in Trusty / 
linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
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/1699772

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes

2017-06-23 Thread Norbert
** Also affects: scilab (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes
+ linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many 
user-space apps crashing

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

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1699892] Re: CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core dumped)"

2017-06-23 Thread Norbert
*** This bug is a duplicate of bug 1699772 ***
https://bugs.launchpad.net/bugs/1699772

** This bug has been marked a duplicate of bug 1699772
   linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: 
many user-space apps crashing

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  New
Status in linux package in Debian:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS 

[Kernel-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

2017-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: scilab (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/1699772

Title:
  linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic
  Regression: many user-space apps crashing

Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1700154] [NEW] package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Eric Canon
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

Public bug reported:

Unable to update due to "unmet dependencies". Tried both sudo get-apt
updates and sudo get-apt -f and then running update again.  Still not
fixed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-81-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eric   1637 F pulseaudio
Date: Fri Jun 23 11:33:45 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=268a3159-ba29-4b19-b292-8a7491f8bec2
InstallationDate: Installed on 2016-07-22 (335 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway NE56R
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=5a4a4734-28c1-43cd-a912-27bf18ee52fa ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
SourcePackage: linux
Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2013
dmi.bios.vendor: Gateway
dmi.bios.version: V2.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EG50_HC_HR
dmi.board.vendor: Gateway
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V2.04
dmi.modalias: 
dmi:bvnGateway:bvrV2.04:bd12/16/2013:svnGateway:pnNE56R:pvrV2.04:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.04:
dmi.product.name: NE56R
dmi.product.version: V2.04
dmi.sys.vendor: Gateway

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Unable to update due to "unmet dependencies". Tried both sudo get-apt
  updates and sudo get-apt -f and then running update again.  Still not
  fixed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   1637 F pulseaudio
  Date: Fri Jun 23 11:33:45 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=268a3159-ba29-4b19-b292-8a7491f8bec2
  InstallationDate: Installed on 2016-07-22 (335 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gateway NE56R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=5a4a4734-28c1-43cd-a912-27bf18ee52fa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Gateway
  dmi.bios.version: V2.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 

[Kernel-packages] [Bug 1700154] Re: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1699108, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1699108
   package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Unable to update due to "unmet dependencies". Tried both sudo get-apt
  updates and sudo get-apt -f and then running update again.  Still not
  fixed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   1637 F pulseaudio
  Date: Fri Jun 23 11:33:45 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=268a3159-ba29-4b19-b292-8a7491f8bec2
  InstallationDate: Installed on 2016-07-22 (335 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gateway NE56R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=5a4a4734-28c1-43cd-a912-27bf18ee52fa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Gateway
  dmi.bios.version: V2.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V2.04
  dmi.modalias: 
dmi:bvnGateway:bvrV2.04:bd12/16/2013:svnGateway:pnNE56R:pvrV2.04:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.04:
  dmi.product.name: NE56R
  dmi.product.version: V2.04
  dmi.sys.vendor: Gateway

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

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


[Kernel-packages] [Bug 1699035] gonzo (i386) - tests ran: 141, failed: 0

2017-06-23 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_17-53-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699064] fozzie (i386) - tests ran: 19, failed: 1

2017-06-23 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-82.105-lowlatency/fozzie__4.4.0-82.105__2017-06-23_17-35-00/results-index.html

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

Title:
  linux: 4.4.0-82.105 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1699066
  derivatives: 1699067,1699068,1699069,1699070,1699071
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-06-23 Thread dann frazier
** Description changed:

  Note: Updates are being staged at ppa:dannf/arm64-kdump.
  
  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.
  
  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger
  
  Crash dump should occur, with artifacts collected in /var/crash.
  
  If you want to verify that the dump is usable, install the corresponding
  linux-image--dbgsym package and run:
  
  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.
  
  crash should successfully load, placing you at a "crash>" prompt. At
  that prompt, you can issue the 'bt' command to see a backtrace.
  
  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:
  
  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).
  
  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.
  
  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).
  
  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)
  
  = kexec-tools =
+ == zesty ==
  For zesty, 10 patches are required to add kdump support.
  
  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:
  
  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
-   The callback function only returns -1 or 0, and the return value of
-   kexec_iomem_for_each_line() will never be used.
+   The callback function only returns -1 or 0, and the return value of
+   kexec_iomem_for_each_line() will never be used.
  * sh, x86
-   The callback function may return (-1 for sh,) 0 or 1, but always returns
-   1 once we have reached the maximum number of entries allowed.
-   Even so the current kexec_iomem_for_each_line() counts them up.
-   This change actually fixes this bug.
+   The callback function may return (-1 for sh,) 0 or 1, but always returns
+   1 once we have reached the maximum number of entries allowed.
+   Even so the current kexec_iomem_for_each_line() counts them up.
+   This change actually fixes this bug.
  -
  
  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.
  
  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.
  
  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my test
- results show no change there. amd64 worked before, and continue to work
+ results show no change there. amd64 worked before, and continues to work
  with these changes.
+ 
+ == yakkety ==
+ Since yakkety is based on an older upstream, 6 additional patches are 
required:
+ 
+ arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
+ This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.
+ 
+ kexec-add-max_size-to-memory_ranges.patch:
+ Adds a new element to struct, to be used by later commits.
+ 
+ kexec-add-generic-helper-to-add-to-memoryq_regions.patch,
+ kexec-add-mem_regions-sorting-implementation.patch,
+ kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch,
+ kexec-fix-mem_regions_sort.patch:
+ These patches only add new functions, which will be used by later patches.
+ 
+ kexec-arch-i386-Add-support-for-KASLR-memory-randomi.patch:
+ This is a bug fix or i386 that allows later patches to apply w/o backporting.
+ kdump support for i386 is apparently broken for the yakkety kernel (see LP: 
#1699874) so, if this introduces a regression, it won't be detectable.
+ (I checked to see if this *fixes* i386 crashdumps - it does not).
+ 
+ Note that, while makedumpfile in >= zesty is new enough to work on arm64, the 
yakkety version does not. kdump-tools falls back to copying the entire vmcore, 
which is what I tested.
+ As with zesty, I have tested this update on both i386 and amd64 VMs. i386 
crashes do not currently work in yakkety, and my test results show no change 
there. amd64 worked before, and continues to work with these changes.

-- 
You received this bug notification because 

[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 10, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-23_17-00-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1692668] Re: stress-ng sockfd stressor kills 4.11 kernels

2017-06-23 Thread Seth Forshee
Just submitted a test run of i386 against the current artful-proposed
kernel. Hopefully they actually run, many of the recent tests have
failed to actually run due to broken package dependencies :-(

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

Title:
  stress-ng sockfd stressor kills 4.11 kernels

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Seen in ADT on i386, though I've also reproduced in an amd64 vm.
  Running the following appears to use up all RAM in the system:

   # stress-ng -v -t 10 --sockfd 4 --ignite-cpu --syslog --verbose
  --verify

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

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


[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-06-23 Thread dann frazier
** Changed in: kexec-tools (Ubuntu Yakkety)
   Status: Confirmed => In Progress

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Confirmed
Status in kexec-tools source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At
  that prompt, you can issue the 'bt' command to see a backtrace.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
The callback function only returns -1 or 0, and the return value of
kexec_iomem_for_each_line() will never be used.
  * sh, x86
The callback function may return (-1 for sh,) 0 or 1, but always returns
1 once we have reached the maximum number of entries allowed.
Even so the current kexec_iomem_for_each_line() counts them up.
This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continue
  to work with these changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+subscriptions

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


[Kernel-packages] [Bug 1699035] Re: linux: 4.8.0-57.62 -proposed tracker

2017-06-23 Thread Stefan Bader
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699028] kernel03 (s390x.zVM) - tests ran: 64, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-25.29-generic/kernel03__4.10.0-25.29__2017-06-23_17-23-00/results-index.html

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699064] amaura (amd64) - tests ran: 1, failed: 0

2017-06-23 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-82.105-lowlatency/amaura__4.4.0-82.105__2017-06-23_17-37-00/results-index.html

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

Title:
  linux: 4.4.0-82.105 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1699066
  derivatives: 1699067,1699068,1699069,1699070,1699071
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699184] Re: linux: 4.11.0-8.13 -proposed tracker

2017-06-23 Thread Po-Hsu Lin
4.11.0-8.13 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  monotonic_time - passed on one node.
  ubuntu_bpf - patch failed to apply, no regression
  ubuntu_fan_smoke_test - temprorary Internet issue, passed after re-test
  ubuntu_kvm_unit_tests - failed item seen before, no regression
  ubuntu_lttng_smoke_test - Kernel tracer not available, bug 1699755
  ubuntu_qrt_apparmor - failed after stackprofile test, bug 1661030
  ubuntu_qrt_kernel_security - test_061_guard_page failed, test case issue, bug 
1699751
  ubuntu_seccomp - TRAP.handler failed, issue seen in 4.11.0-6, not regression
  ubuntu_sysdig_smoke_test - need root permission bug 1700014
  ubuntu_zfs_xfs_generic - broken package dependency for texlive, retested 
without it and passed
  xfstests - broken package dependency for texlive, retested without it and 
failed with 044, 045, 046, 048 and 228

Issue to note in arm64:
  hwclock - failed to change time, issue seen before, no regression
  libhugetlbfs - issue seen before, no regression
  ubuntu_bpf - patch failed to apply, no regression
  ubuntu_kernel_selftests - breakpoint failed to build, bug 1680507
  ubuntu_lttng_smoke_test - bug 1699755
  ubuntu_lxc - download issue, passed after re-test
  ubuntu_qrt_apparmor - failed after running stackpofile test, bug 1661030
  ubuntu_qrt_kernel_security - test_061_guard_page failed, test case issue, bug 
1699751
  ubuntu_zfs_xfs_generic - broken package dependency for texlive, retested 
without it, failed with 079 and 317, no regression

Issue to note in i386:
  libhugetlbfs - issue seen before, no regression

** Changed in: kernel-development-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.11.0-8.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-8.13 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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699035] gonzo (amd64) - tests ran: 141, failed: 0

2017-06-23 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_16-35-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1700014] Re: ubuntu_sysdig_smoke_test failed to start on Artful amd64 system

2017-06-23 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ubuntu_sysdig_smoke_test failed to start on Artful amd64 system

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This test case is complaining:
  == sysdig smoke test to trace dd, cat, read and writes ==
  Try 1 of 10
  error creating the process list. Make sure you have root credentials.

  Complete log:
  http://pastebin.ubuntu.com/24931399/

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

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


[Kernel-packages] [Bug 1699892] Re: CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core dumped)"

2017-06-23 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1699892

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  New
Status in linux package in Debian:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  Lsusb:
   Bus 001 Device 

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

2017-06-23 Thread Joseph Salisbury
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1700123

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

Title:
  stack_grow_into_huge in libhugetlbfs failed on 4.4 / 4.10 s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is one new failure found in the libhugetlbfs test suite on
  s390-zKVM (s2lp6g003) with 4.10.0-25.29

  06/23 05:34:34 DEBUG| utils:0153| [stdout] stack_grow_into_huge
  (1024K: 64): FAIL Child not signalled

  This test did not fail on 4.10.0-23

  Complete log: http://pastebin.ubuntu.com/24933783/

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

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


[Kernel-packages] [Bug 1700052] Re: stress-ng-sockfd failed on Zesty i386

2017-06-23 Thread Colin Ian King
*** This bug is a duplicate of bug 1692668 ***
https://bugs.launchpad.net/bugs/1692668

Fix committed: http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=6ef400f874410a8c414923748f79cf944d06f6af

This fix is now in stress-ng and should therefore be picked up on the
next ADT run. Can you verify that this now works on the ADT tests for
the 4.11 kernel?

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

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

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

** This bug has been marked a duplicate of bug 1692668
   stress-ng sockfd stressor kills 4.11 kernels

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

Title:
  stress-ng-sockfd failed on Zesty i386

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This test has failed on node gonzo with Zesty i386

  But it has passed on node gonzo with Zesty amd64

  Full log: http://pastebin.ubuntu.com/24932093/

  Here is the error log:
   sock PASSED
   sockfd STARTING
   sockfd RETURNED 2
   sockfd FAILED
   stress-ng: debug: [23647] 6 processors online, 6 processors configured
   stress-ng: info: [23647] dispatching hogs: 4 sockfd
   stress-ng: debug: [23647] cache allocate: default cache size: 8192K
   stress-ng: debug: [23647] starting stressors
   stress-ng: debug: [23648] stress-ng-sockfd: started [23648] (instance 0)
   stress-ng: debug: [23649] stress-ng-sockfd: started [23649] (instance 1)
   stress-ng: debug: [23647] 4 stressors spawned
   stress-ng: debug: [23650] stress-ng-sockfd: started [23650] (instance 2)
   stress-ng: debug: [23651] stress-ng-sockfd: started [23651] (instance 3)
   stress-ng: debug: [23649] stress-ng-sockfd: process [23649] using socket 
port 8001
   stress-ng: debug: [23648] stress-ng-sockfd: process [23648] using socket 
port 8000
   stress-ng: debug: [23650] stress-ng-sockfd: process [23650] using socket 
port 8002
   stress-ng: debug: [23651] stress-ng-sockfd: process [23651] using socket 
port 8003
   stress-ng: debug: [23647] process 23648 (stress-ng-sockfd) terminated on 
signal: 9 (Killed)
   stress-ng: debug: [23647] process [23648] terminated
   stress-ng: debug: [23647] process 23649 (stress-ng-sockfd) terminated on 
signal: 9 (Killed)
   stress-ng: debug: [23647] process [23649] terminated
   stress-ng: debug: [23647] process 23650 (stress-ng-sockfd) terminated on 
signal: 13 (Broken pipe)
   stress-ng: debug: [23647] process [23650] terminated
   stress-ng: debug: [23647] process 23651 (stress-ng-sockfd) terminated on 
signal: 13 (Broken pipe)
   stress-ng: debug: [23647] process [23651] terminated
   stress-ng: info: [23647] unsuccessful run completed in 11.72s

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

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


[Kernel-packages] [Bug 1700123] Re: stack_grow_into_huge in libhugetlbfs failed on 4.10 s390 zKVM

2017-06-23 Thread Po-Hsu Lin
This issue can be found on 4.4.0-82, Ubuntu on LPAR (s2lp3) as well.

06/23 06:02:17 DEBUG| utils:0153| [stdout] stack_grow_into_huge (1024K:
64): FAIL Child not signalled

** Summary changed:

- stack_grow_into_huge in libhugetlbfs failed on 4.10 s390 zKVM
+ stack_grow_into_huge in libhugetlbfs failed on 4.4 / 4.10 s390x

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

Title:
  stack_grow_into_huge in libhugetlbfs failed on 4.4 / 4.10 s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is one new failure found in the libhugetlbfs test suite on
  s390-zKVM (s2lp6g003) with 4.10.0-25.29

  06/23 05:34:34 DEBUG| utils:0153| [stdout] stack_grow_into_huge
  (1024K: 64): FAIL Child not signalled

  This test did not fail on 4.10.0-23

  Complete log: http://pastebin.ubuntu.com/24933783/

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

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


[Kernel-packages] [Bug 1692668] Re: stress-ng sockfd stressor kills 4.11 kernels

2017-06-23 Thread Colin Ian King
This fix is now in stress-ng and should therefore be picked up on the
next ADT run.  Seth, can you verify that this now works on the ADT tests
for the 4.11 kernel?

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

Title:
  stress-ng sockfd stressor kills 4.11 kernels

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Seen in ADT on i386, though I've also reproduced in an amd64 vm.
  Running the following appears to use up all RAM in the system:

   # stress-ng -v -t 10 --sockfd 4 --ignite-cpu --syslog --verbose
  --verify

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

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


[Kernel-packages] [Bug 1692668] Re: stress-ng sockfd stressor kills 4.11 kernels

2017-06-23 Thread Colin Ian King
Fix committed: http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=6ef400f874410a8c414923748f79cf944d06f6af

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  stress-ng sockfd stressor kills 4.11 kernels

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Seen in ADT on i386, though I've also reproduced in an amd64 vm.
  Running the following appears to use up all RAM in the system:

   # stress-ng -v -t 10 --sockfd 4 --ignite-cpu --syslog --verbose
  --verify

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

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


[Kernel-packages] [Bug 1699028] kernel03 (s390x.zVM) - tests ran: 4, failed: 2

2017-06-23 Thread Brad Figg
tests ran:   4, failed: 2;
  
http://kernel.ubuntu.com/testing/4.10.0-25.29-generic/kernel03__4.10.0-25.29__2017-06-23_16-11-00/results-index.html

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699035] Re: linux: 4.8.0-57.62 -proposed tracker

2017-06-23 Thread Taihsiang Ho
Skip Certification-testing for limited test time of the recent respin.


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

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 19, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-23_15-40-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699028] Re: linux: 4.10.0-25.29 -proposed tracker

2017-06-23 Thread Taihsiang Ho
Skip Certification-testing for limited test time of the recent respin.

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

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1700026] Re: [17.10 FEAT]: Update kernel .config for POWER8

2017-06-23 Thread Manoj Iyer
Artful (17.10) Ubuntu-4.11.0-8.13 has:

debian.master/config/annotations:CONFIG_POWER8_CPU policy<{'ppc64el': 'y'}>
debian.master/config/config.common.ubuntu:CONFIG_POWER8_CPU=y

debian.master/config/annotations:CONFIG_POWER7_CPU policy<{'ppc64el': 'n'}>
debian.master/config/config.common.ubuntu:# CONFIG_POWER7_CPU is not set

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

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

Title:
  [17.10 FEAT]: Update kernel .config for POWER8

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-19 13:06:06 ==
  Dear Canonical,

  Currently 17.10 kernel is built using POWER7 instructions. It is time
  to change for POWER8, could you please change CONFIG_POWER7_CPU=n and
  CONFIG_POWER8_CPU=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700026/+subscriptions

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


[Kernel-packages] [Bug 1699047] Re: linux: 3.13.0-122.171 -proposed tracker

2017-06-23 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

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

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

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

Title:
  linux: 3.13.0-122.171 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  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

  backports: 1699048
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1700123] [NEW] stack_grow_into_huge in libhugetlbfs failed on 4.10 s390 zKVM

2017-06-23 Thread Po-Hsu Lin
Public bug reported:

There is one new failure found in the libhugetlbfs test suite on
s390-zKVM (s2lp6g003) with 4.10.0-25.29

06/23 05:34:34 DEBUG| utils:0153| [stdout] stack_grow_into_huge (1024K:
64): FAIL Child not signalled

This test did not fail on 4.10.0-23

Complete log: http://pastebin.ubuntu.com/24933783/

** 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/1700123

Title:
  stack_grow_into_huge in libhugetlbfs failed on 4.10 s390 zKVM

Status in linux package in Ubuntu:
  New

Bug description:
  There is one new failure found in the libhugetlbfs test suite on
  s390-zKVM (s2lp6g003) with 4.10.0-25.29

  06/23 05:34:34 DEBUG| utils:0153| [stdout] stack_grow_into_huge
  (1024K: 64): FAIL Child not signalled

  This test did not fail on 4.10.0-23

  Complete log: http://pastebin.ubuntu.com/24933783/

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

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


[Kernel-packages] [Bug 1699028] s2lp6g003 (s390x.zKVM) - tests ran: 15, failed: 3

2017-06-23 Thread Brad Figg
tests ran:  15, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-25.29-generic/s2lp6g003__4.10.0-25.29__2017-06-23_16-02-00/results-index.html

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699064] Re: linux: 4.4.0-82.105 -proposed tracker

2017-06-23 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-82.105
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1699064

Title:
  linux: 4.4.0-82.105 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1699066
  derivatives: 1699067,1699068,1699069,1699070,1699071
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699047] Re: linux: 3.13.0-122.171 -proposed tracker

2017-06-23 Thread Taihsiang Ho
Skip Certification-testing for limited test time of the recent respin.

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

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

Title:
  linux: 3.13.0-122.171 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  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

  backports: 1699048
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699892] Re: CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core dumped)"

2017-06-23 Thread Norbert
** No longer affects: openjdk-8 (Ubuntu)

** Bug watch added: Debian Bug tracker #865672
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865672

** Also affects: linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865672
   Importance: Unknown
   Status: Unknown

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  New
Status in linux package in Debian:
  Unknown

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  

[Kernel-packages] [Bug 1699035] gonzo (i386) - tests ran: 6, failed: 0

2017-06-23 Thread Brad Figg
tests ran:   6, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_15-27-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1692668] Re: stress-ng sockfd stressor kills 4.11 kernels

2017-06-23 Thread Colin Ian King
[  186.684737] Call Trace:
[  186.684941]  dump_stack+0x63/0x8d
[  186.685143]  panic+0xe4/0x22d
[  186.685359]  out_of_memory+0x363/0x4e0
[  186.685559]  __alloc_pages_slowpath+0xd3f/0xe20
[  186.685758]  __alloc_pages_nodemask+0x241/0x280
[  186.685953]  alloc_pages_vma+0xab/0x280
[  186.686145]  __read_swap_cache_async+0x147/0x1f0
[  186.686333]  read_swap_cache_async+0x26/0x60
[  186.686520]  swapin_readahead+0x1b0/0x200
[  186.686755]  ? radix_tree_lookup_slot+0x22/0x50
[  186.687032]  ? find_get_entry+0x1e/0x140
[  186.687301]  do_swap_page+0x27a/0x740
[  186.687584]  ? do_swap_page+0x27a/0x740
[  186.687824]  __handle_mm_fault+0x6a3/0x1010
[  186.688004]  handle_mm_fault+0xf9/0x220
[  186.688177]  __do_page_fault+0x23e/0x4e0
[  186.688351]  trace_do_page_fault+0x37/0xd0
[  186.688522]  do_async_page_fault+0x19/0x70
[  186.688683]  async_page_fault+0x28/0x30
[  186.688842] RIP: 0033:0x7f74a2735b7c
[  186.689007] RSP: 002b:7ffc05fdaf50 EFLAGS: 00010246
[  186.689168] RAX: 0008 RBX: 7ffc05fdb4b0 RCX: 0d68
[  186.689329] RDX: 5649cd4d17b8 RSI: 5649cd4d17b0 RDI: 7ffc05fdb648
[  186.689498] RBP: 7ffc05fdb4a0 R08:  R09: 0008
[  186.689658] R10: 7f74a3972708 R11:  R12: 5649cd4d17b0
[  186.689813] R13: 7ffc05fdbea0 R14:  R15: 0008
[  186.690051] Kernel Offset: 0x200 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[  186.690226] ---[ end Kernel panic - not syncing: Out of memory and no 
killable processes..

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

Title:
  stress-ng sockfd stressor kills 4.11 kernels

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Seen in ADT on i386, though I've also reproduced in an amd64 vm.
  Running the following appears to use up all RAM in the system:

   # stress-ng -v -t 10 --sockfd 4 --ignite-cpu --syslog --verbose
  --verify

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

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


[Kernel-packages] [Bug 1692668] Re: stress-ng sockfd stressor kills 4.11 kernels

2017-06-23 Thread Colin Ian King
[   85.954718] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   85.954939] Call Trace:
[   85.955149]  dump_stack+0x63/0x8d
[   85.955352]  panic+0xe4/0x22d
[   85.95]  out_of_memory+0x363/0x4e0
[   85.955755]  __alloc_pages_slowpath+0xd3f/0xe20
[   85.955952]  __alloc_pages_nodemask+0x241/0x280
[   85.956152]  alloc_pages_current+0x95/0x140
[   85.956353]  new_slab+0x473/0x770
[   85.956540]  ___slab_alloc+0x41c/0x570
[   85.956726]  ? apparmor_file_alloc_security+0x23/0x40
[   85.956915]  ? get_empty_filp+0x5c/0x1c0
[   85.957101]  ? apparmor_file_alloc_security+0x23/0x40
[   85.957285]  __slab_alloc+0x20/0x40
[   85.957462]  ? __slab_alloc+0x20/0x40
[   85.957638]  kmem_cache_alloc_trace+0x1f9/0x240
[   85.957813]  ? get_empty_filp+0x5c/0x1c0
[   85.957986]  apparmor_file_alloc_security+0x23/0x40
[   85.958159]  security_file_alloc+0x33/0x50
[   85.958328]  get_empty_filp+0x9a/0x1c0
[   85.958495]  ? getname_flags+0x4f/0x1f0
[   85.958660]  path_openat+0x40/0x1490
[   85.958822]  ? init_object+0x69/0xa0
[   85.958982]  ? ___slab_alloc+0x1ac/0x570
[   85.959141]  do_filp_open+0x99/0x110
[   85.959298]  ? set_next_entity+0xd9/0x210
[   85.959453]  ? __check_object_size+0xb3/0x190
[   85.959607]  ? __alloc_fd+0x46/0x170
[   85.959757]  do_sys_open+0x130/0x220
[   85.959902]  ? do_sys_open+0x130/0x220
[   85.960048]  SyS_open+0x1e/0x20
[   85.960187]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[   85.960331] RIP: 0033:0x7f16e254dd70
[   85.960473] RSP: 002b:7ffc899232c8 EFLAGS: 0246 ORIG_RAX: 
0002
[   85.960620] RAX: ffda RBX: 000e6d52 RCX: 7f16e254dd70
[   85.960759] RDX:  RSI: 0002 RDI: 5636dfad6b48
[   85.960901] RBP: 7ffc899233f0 R08: d299bf0369a17e00 R09: 0015
[   85.961043] R10: 0075 R11: 0246 R12: 7ffc89923360
[   85.961179] R13: 000c R14: 7ffc899233a0 R15: 0006
[   85.961405] Kernel Offset: 0x3c00 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[   85.961549] ---[ end Kernel panic - not syncing: Out of memory and no 
killable processes...

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

Title:
  stress-ng sockfd stressor kills 4.11 kernels

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Seen in ADT on i386, though I've also reproduced in an amd64 vm.
  Running the following appears to use up all RAM in the system:

   # stress-ng -v -t 10 --sockfd 4 --ignite-cpu --syslog --verbose
  --verify

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

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


[Kernel-packages] [Bug 1698919] Re: CVE-2017-1000364

2017-06-23 Thread Norbert
New kernel in Xenial broke Eclipse (see
https://askubuntu.com/questions/927746/eclipse-crashes-with-linux-
kernel-4-4-0-81-generic ).

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

Title:
  CVE-2017-1000364

Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-joule package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-aws source package in Trusty:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-gke source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-hwe source package in Trusty:
  Invalid
Status in linux-hwe-edge source package in Trusty:
  Invalid
Status in linux-joule source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-flo source package in Xenial:
  Invalid
Status in linux-gke source package in Xenial:
  New
Status in linux-goldfish source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-joule source package in Xenial:
  New
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package in Xenial:
  Invalid
Status in linux-manta source package in Xenial:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New
Status in linux-snapdragon source package in Xenial:
  New
Status in linux-ti-omap4 source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  New
Status in linux-aws source package in Yakkety:
  Invalid
Status in linux-azure source package in Yakkety:
  Invalid
Status in linux-flo source package in Yakkety:
  Invalid
Status in linux-gke source package in Yakkety:
  Invalid
Status in linux-goldfish source package in Yakkety:
  New
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux-hwe-edge source package in Yakkety:
  Invalid
Status in linux-joule source package in Yakkety:
  Invalid
Status in linux-lts-utopic source package in Yakkety:
  Invalid
Status in linux-lts-vivid source package in Yakkety:
  Invalid
Status in linux-lts-wily source package in Yakkety:
  Invalid
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux-mako source package in Yakkety:
  Invalid
Status in linux-manta source package in Yakkety:
  Invalid
Status in linux-raspi2 source package in Yakkety:
  New
Status in linux-snapdragon source package in Yakkety:
  New
Status in linux-ti-omap4 source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  New
Status in linux-aws source package in Zesty:
  Invalid
Status in linux-azure source package in Zesty:
  Invalid
Status in linux-flo source package in Zesty:
  Invalid
Status in linux-gke source package in Zesty:
  Invalid
Status in linux-goldfish source package in Zesty:
  New
Status in linux-hwe source package in Zesty:
  Invalid
Status in linux-hwe-edge source package in Zesty:
  Invalid
Status in linux-joule source package in Zesty:
  Invalid
Status in linux-lts-utopic source package in Zesty:
  Invalid
Status in linux-lts-vivid source package in Zesty:
 

[Kernel-packages] [Bug 1698919] Re: CVE-2017-1000364

2017-06-23 Thread Norbert
as addition to my comment 7 - Trusty is affected too, see Raven's
comment.

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

Title:
  CVE-2017-1000364

Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-joule package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-aws source package in Trusty:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-gke source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-hwe source package in Trusty:
  Invalid
Status in linux-hwe-edge source package in Trusty:
  Invalid
Status in linux-joule source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-flo source package in Xenial:
  Invalid
Status in linux-gke source package in Xenial:
  New
Status in linux-goldfish source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-joule source package in Xenial:
  New
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package in Xenial:
  Invalid
Status in linux-manta source package in Xenial:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New
Status in linux-snapdragon source package in Xenial:
  New
Status in linux-ti-omap4 source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  New
Status in linux-aws source package in Yakkety:
  Invalid
Status in linux-azure source package in Yakkety:
  Invalid
Status in linux-flo source package in Yakkety:
  Invalid
Status in linux-gke source package in Yakkety:
  Invalid
Status in linux-goldfish source package in Yakkety:
  New
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux-hwe-edge source package in Yakkety:
  Invalid
Status in linux-joule source package in Yakkety:
  Invalid
Status in linux-lts-utopic source package in Yakkety:
  Invalid
Status in linux-lts-vivid source package in Yakkety:
  Invalid
Status in linux-lts-wily source package in Yakkety:
  Invalid
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux-mako source package in Yakkety:
  Invalid
Status in linux-manta source package in Yakkety:
  Invalid
Status in linux-raspi2 source package in Yakkety:
  New
Status in linux-snapdragon source package in Yakkety:
  New
Status in linux-ti-omap4 source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  New
Status in linux-aws source package in Zesty:
  Invalid
Status in linux-azure source package in Zesty:
  Invalid
Status in linux-flo source package in Zesty:
  Invalid
Status in linux-gke source package in Zesty:
  Invalid
Status in linux-goldfish source package in Zesty:
  New
Status in linux-hwe source package in Zesty:
  Invalid
Status in linux-hwe-edge source package in Zesty:
  Invalid
Status in linux-joule source package in Zesty:
  Invalid
Status in linux-lts-utopic source package in Zesty:
  Invalid
Status in linux-lts-vivid source package in Zesty:
  Invalid
Status in linux-lts-wily source package in Zesty:

[Kernel-packages] [Bug 1699035] rumford (amd64) - tests ran: 1, failed: 0

2017-06-23 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/rumford__4.8.0-57.62__2017-06-23_15-13-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699892] Re: CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core dumped)"

2017-06-23 Thread Norbert
Bug exists in Trusty - error in linux-image-3.13.0-121-generic.

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  Lsusb:
   Bus 

[Kernel-packages] [Bug 1698919] Re: CVE-2017-1000364

2017-06-23 Thread Norbert
This fix breaks Scilab 5.5.0 on Trusty - see bug 1699892 for details.
Kernel linux-image-3.13.0-121-generic is a problem.

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

Title:
  CVE-2017-1000364

Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-joule package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-aws source package in Trusty:
  Invalid
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-gke source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-hwe source package in Trusty:
  Invalid
Status in linux-hwe-edge source package in Trusty:
  Invalid
Status in linux-joule source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-flo source package in Xenial:
  Invalid
Status in linux-gke source package in Xenial:
  New
Status in linux-goldfish source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-joule source package in Xenial:
  New
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package in Xenial:
  Invalid
Status in linux-manta source package in Xenial:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New
Status in linux-snapdragon source package in Xenial:
  New
Status in linux-ti-omap4 source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  New
Status in linux-aws source package in Yakkety:
  Invalid
Status in linux-azure source package in Yakkety:
  Invalid
Status in linux-flo source package in Yakkety:
  Invalid
Status in linux-gke source package in Yakkety:
  Invalid
Status in linux-goldfish source package in Yakkety:
  New
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux-hwe-edge source package in Yakkety:
  Invalid
Status in linux-joule source package in Yakkety:
  Invalid
Status in linux-lts-utopic source package in Yakkety:
  Invalid
Status in linux-lts-vivid source package in Yakkety:
  Invalid
Status in linux-lts-wily source package in Yakkety:
  Invalid
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux-mako source package in Yakkety:
  Invalid
Status in linux-manta source package in Yakkety:
  Invalid
Status in linux-raspi2 source package in Yakkety:
  New
Status in linux-snapdragon source package in Yakkety:
  New
Status in linux-ti-omap4 source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  New
Status in linux-aws source package in Zesty:
  Invalid
Status in linux-azure source package in Zesty:
  Invalid
Status in linux-flo source package in Zesty:
  Invalid
Status in linux-gke source package in Zesty:
  Invalid
Status in linux-goldfish source package in Zesty:
  New
Status in linux-hwe source package in Zesty:
  Invalid
Status in linux-hwe-edge source package in Zesty:
  Invalid
Status in linux-joule source package in Zesty:
  Invalid
Status in linux-lts-utopic source package in Zesty:
  Invalid
Status in linux-lts-vivid source package in Zesty:
  Invalid

[Kernel-packages] [Bug 1699184] michael (amd64) - tests ran: 22, failed: 3

2017-06-23 Thread Brad Figg
tests ran:  22, failed: 3;
  
http://kernel.ubuntu.com/testing/4.11.0-8.13-generic/michael__4.11.0-8.13__2017-06-23_08-06-00/results-index.html

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

Title:
  linux: 4.11.0-8.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-8.13 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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699892] WifiSyslog.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901614/+files/WifiSyslog.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no 

[Kernel-packages] [Bug 1699892] UdevLog.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901613/+files/UdevLog.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no 

[Kernel-packages] [Bug 1699892] ProcEnviron.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901608/+files/ProcEnviron.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  

[Kernel-packages] [Bug 1699892] ProcInterrupts.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901609/+files/ProcInterrupts.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  

[Kernel-packages] [Bug 1699892] ProcModules.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901610/+files/ProcModules.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  

[Kernel-packages] [Bug 1699892] PulseList.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901611/+files/PulseList.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no 

[Kernel-packages] [Bug 1699892] UdevDb.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1699892/+attachment/4901612/+files/UdevDb.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless 

[Kernel-packages] [Bug 1699892] ProcCpuinfoMinimal.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901607/+files/ProcCpuinfoMinimal.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
 

[Kernel-packages] [Bug 1699892] Lspci.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1699892/+attachment/4901606/+files/Lspci.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless 

[Kernel-packages] [Bug 1699892] BootDmesg.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901603/+files/BootDmesg.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no 

[Kernel-packages] [Bug 1699892] Dependencies.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901605/+files/Dependencies.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  

[Kernel-packages] [Bug 1699892] CurrentDmesg.txt

2017-06-23 Thread Norbert
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1699892/+attachment/4901604/+files/CurrentDmesg.txt

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

Title:
  CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core
  dumped)"

Status in linux package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
  4. Get new kernel with new updates
linux-image-3.13.0-121-generic (in Trusty) /
linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".

  Expected results:
  * Scilab is working normally with new kernel.

  Actual results:
  * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).

  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=347e9507-87b1-431d-b36f-538d190a517f
  InstallationDate: Installed on 2014-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  

[Kernel-packages] [Bug 1699892] Re: linux-image-4.4.0-81-generic (on Xenial) and linux-image-3.13.0-121-generic (on Trusty) cause scilab-5.5.2 to crash with "Segmentation fault (core dumped)"

2017-06-23 Thread Norbert
apport information

** Summary changed:

- linux-image-4.4.0-81-generic cause scilab-5.5.2 to crash with "Segmentation 
fault (core dumped)"
+ linux-image-4.4.0-81-generic (on Xenial) and linux-image-3.13.0-121-generic 
(on Trusty)  cause scilab-5.5.2 to crash with "Segmentation fault (core dumped)"

** Summary changed:

- linux-image-4.4.0-81-generic (on Xenial) and linux-image-3.13.0-121-generic 
(on Trusty)  cause scilab-5.5.2 to crash with "Segmentation fault (core dumped)"
+ CVE-2017-1000364 fix cause Scilab crash with "Segmentation fault (core 
dumped)"

** Description changed:

  Steps to introduce:
- 1. Install Ubuntu 16.04 LTS.
- 2. Install Scilab 5.5.2 (http://www.scilab.org/, sudo apt-get install scilab).
+ 1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
+ 2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all system upgrades (sudo apt-get update; sudo apt-get upgrade)
- 4. Get kernel linux-image-4.4.0-81-generic with new updates.
+ 4. Get new kernel with new updates
+   linux-image-3.13.0-121-generic (in Trusty) /
+   linux-image-4.4.0-81-generic  (in Xenial).
  5a. Try to start Scilab from GUI - it crashes.
  5b. Try to start Scilab from terminal - it reports "Segmentation fault (core 
dumped)".
  
  Expected results:
  * Scilab is working normally with new kernel.
  
  Actual results:
- * Scilab is crashing with new kernel (linux-image-4.4.0-81-generic), but 
works with previous one (linux-image-4.4.0-78-generic).
+ * Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in 
Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one 
(linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in 
Xenial).
  
  Notes:
  * First discovered and documented by ubuntu-fr (see 
https://forum.ubuntu-fr.org/viewtopic.php?id=2011162) and then Philippe Roux on 
Scilab MailingLists 
(http://mailinglists.scilab.org/Scilab-users-scilab-gt-Segmentation-fault-td4036624.html).
  * The problem exists on both 32-bit and 64-bit architectures.
  * Temporary solution is to use previous kernel.
  * The problem may be related to these: new "linux-image-4.4.0-81-generic 
Regression: Oracle Java plugin crashes" (bug 1699772) or old "scilab libraries 
are heavily underlinked, causing segfaults on load" (bug 1299686).
  * SegvReason is "writing unknown VMA".
  * May be related to CVE-2017-1000364 (see bug 1698919).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Jun 22 23:27:11 2017
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay1885 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (427 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  NonfreeKernelModules: wl
  Package: scilab 5.5.2-2ubuntu3
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-81-generic N/A
   linux-backports-modules-4.4.0-81-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial xenial
  Uname: Linux 4.4.0-81-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Tags added: trusty

** Tags added: third-party-packages

** Description changed:

  Steps to introduce:
  1. Install Ubuntu 14.04 LTS or Ubuntu 16.04 LTS.
  2. Install Scilab 5.5.0 or 5.5.2 (sudo apt-get install scilab).
  3. Install all 

[Kernel-packages] [Bug 1699028] Re: linux: 4.10.0-25.29 -proposed tracker

2017-06-23 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   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/1699028

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699035] gonzo (amd64) - tests ran: 19, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-57.62-generic/gonzo__4.8.0-57.62__2017-06-23_14-15-00/results-index.html

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

Title:
  linux: 4.8.0-57.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1699036
  derivatives: 1699037
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1699028] rumford (amd64) - tests ran: 64, failed: 0

2017-06-23 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-25.29-generic/rumford__4.10.0-25.29__2017-06-23_14-22-00/results-index.html

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1700077] Re: aacraid driver may return uninitialized stack data to userspace

2017-06-23 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ Impact: Recent aacraid backports introduce potential information leaks,
+ where some stack allocated memory may be copied to userspace without
+ initialization.
+ 
+ Fix: Clear out the affected memory before using it to ensure that none
+ is left uninitialized.
+ 
+ Test Case: None. Code review should be sufficient to validate the
+ changes.
+ 
+ Regression Potential: Negligible. The patch simply memsets some structs
+ to clear them out prior to any other use.
+ 
+ ---
+ 
  aac_send_raw_srb() and aac_get_hba_info() both copy the contents of
  stack variables to userspace when some of this memory may be
  uninitialized. The memory should be zeroed out initially to prevent
  this.

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

Title:
  aacraid driver may return uninitialized stack data to userspace

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent aacraid backports introduce potential information
  leaks, where some stack allocated memory may be copied to userspace
  without initialization.

  Fix: Clear out the affected memory before using it to ensure that none
  is left uninitialized.

  Test Case: None. Code review should be sufficient to validate the
  changes.

  Regression Potential: Negligible. The patch simply memsets some
  structs to clear them out prior to any other use.

  ---

  aac_send_raw_srb() and aac_get_hba_info() both copy the contents of
  stack variables to userspace when some of this memory may be
  uninitialized. The memory should be zeroed out initially to prevent
  this.

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

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


[Kernel-packages] [Bug 1699755] Re: ubuntu_lttng_smoke_test failed on Artful: Kernel tracer not available

2017-06-23 Thread Colin Ian King
With the correct upstream compat patches we still get issues.

  * Cherry picks to fix build isues with 4.11 and 4.12
- [75833a8] Fix: update mm_vmscan instrumentation for kernel 4.11
- [e52717e] Fix: update btrfs instrumentation for kernel 4.11
- [52a391b] Fix: changes to the vm_op fault cb prototype in
libringbuffer
- [8a9f549] Fix: update scsi instrumentation for kernel 4.11
- [678dd1c] Fix: timers cputime_t arguments replaced by ull in kernel
4.11
- [4c4d77d] Fix: atomic_add_unless() returns true/false rather than
prior value
- [7793231] Fix: kref changes for kernel 4.11
- [673e9a0] Fix: update sched instrumentation for kernel 4.12
- [e2833be] Fix: update ringbuffer for kernel 4.12
- [5807b1a] Fix: update btrfs instrumentation for kernel 4.12
- [d245707] Fix: update block instrumentation for kernel 4.12
- [5d84966] Fix: update ftrace probe for kernel 4.12
- [bc1fb1b] Fix: Build ftrace probe on kernels prior to 4.12

This works fine for 4.11 and passes the regression tests. However with
4.12 we get a DKMS build failure:

WARNING: "lttng_ftrace_destroy_private" 
[/var/lib/dkms/lttng-modules/2.9.0/build/lttng-tracer.ko] undefined!
WARNING: "lttng_ftrace_register" 
[/var/lib/dkms/lttng-modules/2.9.0/build/lttng-tracer.ko] undefined!
WARNING: "lttng_ftrace_unregister" 
[/var/lib/dkms/lttng-modules/2.9.0/build/lttng-tracer.ko] undefined!
WARNING: modpost: Found 1 section mismatch(es).

The reason is because of linux commits:

  ec19b85913486993d7d6f747beed1a711afd47d8
  bca6c8d0480a8aa5c86f8f416db96c71f6b79e29
  b5f081b563a6cdcb85a543df8c851951a8978275
  6e4443199e5354255e8a4c1e8e5cfc8ef064c3ce   

but most specifically:

commit 92a68fa047ca5b8e1991af2d50b23ad9452613cd
Author: Steven Rostedt (VMware) 
Date:   Fri Mar 31 19:21:41 2017 -0400

ftrace: Move the function commands into the tracing directory

As nothing outside the tracing directory uses the function command 
mechanism,
I'm moving the prototypes out of the include/linux/ftrace.h and into the
local kernel/trace/trace.h header. I plan on making them hook to the
trace_array structure which is local to kernel/trace, and I do not want to
expose it to the rest of the kernel. This requires that the command 
functions
must also be local to tracing. But luckily nothing else uses them.

Signed-off-by: Steven Rostedt (VMware) 

lttng seems to expect the symbols from the lttng lttng-ftrace.o, but
these are dependent on the lttng-ftrace being built, which it is not
because of:


commit 5d8496675c9e8ccf169871f4f72022df9677624a
Author: Michael Jeanson 
Date:   Thu May 25 16:56:52 2017 -0400

Fix: update ftrace probe for kernel 4.12

..which effectively disables it:

+  ifeq ($(ftrace),warn)
+$(warning Files $(ftrace_dep) not found. Probe "ftrace" is disabled. Use 
full kernel source tree to enable it.)
+ftrace =
+  endif # $(ftrace),warn

and implies we need the full kernel source to build it. Not so good.
I'll reach out to upstream about this.

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

Title:
  ubuntu_lttng_smoke_test failed on Artful: Kernel tracer not available

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Similar to bug 1677126, ubuntu_lttng_smoke_test failed on Artful too.

   == lttng smoke test list kernel events ==
   Error: Unable to list kernel events: Kernel tracer not available
   Error: Command error
   FAILED (lttng list --kernel)
   FAILED (lttng list --kernel more output expected)

   == lttng smoke test trace open/close system calls ==
   Session test-kernel-session created.
   Traces will be written in /tmp/lttng-kernel-trace-2107-session
   PASSED (lttng create)
   Error: Event open: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   Error: Event openat: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   Error: Event close: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   FAILED (lttng enable-event)
   Session test-kernel-session destroyed

   == lttng smoke test trace context switches ==
   Session test-kernel-session created.
   Traces will be written in /tmp/lttng-kernel-trace-2107-session
   PASSED (lttng create)
   Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)
   FAILED (lttng enable-event)

  
  Complete test result: http://pastebin.ubuntu.com/24924042/

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

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

[Kernel-packages] [Bug 1700077] Re: aacraid driver may return uninitialized stack data to userspace

2017-06-23 Thread Seth Forshee
http://lkml.kernel.org/r/20170623140422.30320-1-seth.fors...@canonical.com

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

Title:
  aacraid driver may return uninitialized stack data to userspace

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent aacraid backports introduce potential information
  leaks, where some stack allocated memory may be copied to userspace
  without initialization.

  Fix: Clear out the affected memory before using it to ensure that none
  is left uninitialized.

  Test Case: None. Code review should be sufficient to validate the
  changes.

  Regression Potential: Negligible. The patch simply memsets some
  structs to clear them out prior to any other use.

  ---

  aac_send_raw_srb() and aac_get_hba_info() both copy the contents of
  stack variables to userspace when some of this memory may be
  uninitialized. The memory should be zeroed out initially to prevent
  this.

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

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


[Kernel-packages] [Bug 1699028] rumford (amd64) - tests ran: 2, failed: 0

2017-06-23 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-25.29-generic/rumford__4.10.0-25.29__2017-06-23_13-48-00/results-index.html

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

Title:
  linux: 4.10.0-25.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1699029,1699030
  derivatives: 1699032
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


  1   2   3   >