[Group.of.nepali.translators] [Bug 1759003] Re: cloud-init fails for minimal images (can't find locale-gen)

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.515

---
livecd-rootfs (2.515) bionic; urgency=medium

  * Set the default locale to C.UTF-8 in all server and cloud images.
   (LP: #1751051, #1759003)

 -- Michael Hudson-Doyle   Tue, 27 Mar 2018
09:59:02 +1300

** Changed in: livecd-rootfs (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759003

Title:
  cloud-init fails for minimal images (can't find locale-gen)

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New

Bug description:
  Opening initially as a cloud-images bug to ensure that the lack of
  'locale-gen' is desired.  If so, then this should go to cloud-init to
  dtrt for minimal images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1759003/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1754076] Re: i2c-thunderx: erroneous error message "unhandled state: 0"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-13.14

---
linux (4.15.0-13.14) bionic; urgency=medium

  * linux: 4.15.0-13.14 -proposed tracker (LP: #1756408)

  * devpts: handle bind-mounts (LP: #1755857)
- SAUCE: devpts: hoist out check for DEVPTS_SUPER_MAGIC
- SAUCE: devpts: resolve devpts bind-mounts
- SAUCE: devpts: comment devpts_mntget()
- SAUCE: selftests: add devpts selftests

  * [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules (LP: #1756103)
- d-i: add hisi_sas_v3_hw to scsi-modules

  * [Bionic][ARM64] enable ROCE and HNS3 driver support for hip08 SoC
(LP: #1756097)
- RDMA/hns: Refactor eq code for hip06
- RDMA/hns: Add eq support of hip08
- RDMA/hns: Add detailed comments for mb() call
- RDMA/hns: Add rq inline data support for hip08 RoCE
- RDMA/hns: Update the usage of sr_max and rr_max field
- RDMA/hns: Set access flags of hip08 RoCE
- RDMA/hns: Filter for zero length of sge in hip08 kernel mode
- RDMA/hns: Fix QP state judgement before sending work requests
- RDMA/hns: Assign dest_qp when deregistering mr
- RDMA/hns: Fix endian problems around imm_data and rkey
- RDMA/hns: Assign the correct value for tx_cqn
- RDMA/hns: Create gsi qp in hip08
- RDMA/hns: Add gsi qp support for modifying qp in hip08
- RDMA/hns: Fill sq wqe context of ud type in hip08
- RDMA/hns: Assign zero for pkey_index of wc in hip08
- RDMA/hns: Update the verbs of polling for completion
- RDMA/hns: Set the guid for hip08 RoCE device
- net: hns3: Refactor of the reset interrupt handling logic
- net: hns3: Add reset service task for handling reset requests
- net: hns3: Refactors the requested reset & pending reset handling code
- net: hns3: Add HNS3 VF IMP(Integrated Management Proc) cmd interface
- net: hns3: Add mailbox support to VF driver
- net: hns3: Add HNS3 VF HCL(Hardware Compatibility Layer) Support
- net: hns3: Add HNS3 VF driver to kernel build framework
- net: hns3: Unified HNS3 {VF|PF} Ethernet Driver for hip08 SoC
- net: hns3: Add mailbox support to PF driver
- net: hns3: Change PF to add ring-vect binding & resetQ to mailbox
- net: hns3: Add mailbox interrupt handling to PF driver
- net: hns3: add support to query tqps number
- net: hns3: add support to modify tqps number
- net: hns3: change the returned tqp number by ethtool -x
- net: hns3: free the ring_data structrue when change tqps
- net: hns3: get rss_size_max from configuration but not hardcode
- net: hns3: add a mask initialization for mac_vlan table
- net: hns3: add vlan offload config command
- net: hns3: add ethtool related offload command
- net: hns3: add handling vlan tag offload in bd
- net: hns3: cleanup mac auto-negotiation state query
- net: hns3: fix for getting auto-negotiation state in hclge_get_autoneg
- net: hns3: add support for set_pauseparam
- net: hns3: add support to update flow control settings after autoneg
- net: hns3: add Asym Pause support to phy default features
- net: hns3: add support for querying advertised pause frame by ethtool ethx
- net: hns3: Increase the default depth of bucket for TM shaper
- net: hns3: change TM sched mode to TC-based mode when SRIOV enabled
- net: hns3: hns3_get_channels() can be static
- net: hns3: Add ethtool interface for vlan filter
- net: hns3: Disable VFs change rxvlan offload status
- net: hns3: Unify the strings display of packet statistics
- net: hns3: Fix spelling errors
- net: hns3: Remove repeat statistic of rx_errors
- net: hns3: Modify the update period of packet statistics
- net: hns3: Mask the packet statistics query when NIC is down
- net: hns3: Fix an error of total drop packet statistics
- net: hns3: Fix a loop index error of tqp statistics query
- net: hns3: Fix an error macro definition of HNS3_TQP_STAT
- net: hns3: Remove a useless member of struct hns3_stats
- net: hns3: Add packet statistics of netdev
- net: hns3: Fix a response data read error of tqp statistics query
- net: hns3: fix for updating fc_mode_last_time
- net: hns3: fix for setting MTU
- net: hns3: fix for changing MTU
- net: hns3: add MTU initialization for hardware
- net: hns3: fix for not setting pause parameters
- net: hns3: remove redundant semicolon
- net: hns3: Add more packet size statisctics
- Revert "net: hns3: Add packet statistics of netdev"
- net: hns3: report the function type the same line with 
hns3_nic_get_stats64
- net: hns3: add ethtool_ops.get_channels support for VF
- net: hns3: remove TSO config command from VF driver
- net: hns3: add ethtool_ops.get_coalesce support to PF
- net: hns3: add ethtool_ops.set_coalesce support to PF
- net: hns3: refactor interrupt coalescing init function
- net: hns3: refactor GL update function
- net: hns3: remove unused 

[Group.of.nepali.translators] [Bug 1758699] Re: [CVE] JavaScript in a book can access local files using XMLHttpRequest

[Simon Quigley]

Marc Deslauriers pointed out to me over IRC that Trusty and Xenial are
also vulnerable to CVE-2018-7889.

So Trusty and Xenial need to receive patches for CVE-2016-10187 and
CVE-2018-7889 while Artful just needs the patch for CVE-2018-7889.

I think it makes sense to mark the separate bug I filed for
CVE-2018-7889 a duplicate of this one.

I'll update my PPA and test with this new information, and I'll report
back.

Thanks!

** Description changed:

- The E-book viewer in calibre before 2.75 allows remote attackers to read
- arbitrary files via a crafted epub file with JavaScript.
+ For CVE-2016-10187:
+ The E-book viewer in calibre before 2.75 allows remote attackers to read 
arbitrary files via a crafted epub file with JavaScript.
+ 
+ For CVE-2018-7889:
+ gui2/viewer/bookmarkmanager.py in Calibre 3.18 calls cPickle.load on imported 
bookmark data, which allows remote attackers to execute arbitrary code via a 
crafted .pickle file, as demonstrated by Python code that contains an os.system 
call.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7889

** Also affects: calibre (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1758699

Title:
  [CVE] JavaScript in a book can access local files using XMLHttpRequest

Status in calibre package in Ubuntu:
  Fix Released
Status in calibre source package in Trusty:
  In Progress
Status in calibre source package in Xenial:
  In Progress
Status in calibre source package in Artful:
  New

Bug description:
  For CVE-2016-10187:
  The E-book viewer in calibre before 2.75 allows remote attackers to read 
arbitrary files via a crafted epub file with JavaScript.

  For CVE-2018-7889:
  gui2/viewer/bookmarkmanager.py in Calibre 3.18 calls cPickle.load on imported 
bookmark data, which allows remote attackers to execute arbitrary code via a 
crafted .pickle file, as demonstrated by Python code that contains an os.system 
call.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759069] [NEW] [CVE] Arbitrary command injection via DVI filename injection when printing to PDF

[Simon Quigley]

Public bug reported:

Command injection in Evince via filename when printing to PDF is
possible. This also affects Atril, which is a fork of Evince.

Here's the patch in Atril: https://github.com/mate-
desktop/atril/commit/4650fb05e46e144be986a11a666a47add39b3799

** Affects: atril (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: atril (Ubuntu Xenial)
 Importance: Medium
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: atril (Ubuntu Artful)
 Importance: Medium
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Also affects: atril (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: atril (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: atril (Ubuntu)
   Status: New => Fix Released

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

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

** Changed in: atril (Ubuntu Xenial)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: atril (Ubuntu Artful)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000159

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759069

Title:
  [CVE] Arbitrary command injection via DVI filename injection when
  printing to PDF

Status in atril package in Ubuntu:
  Fix Released
Status in atril source package in Xenial:
  In Progress
Status in atril source package in Artful:
  In Progress

Bug description:
  Command injection in Evince via filename when printing to PDF is
  possible. This also affects Atril, which is a fork of Evince.

  Here's the patch in Atril: https://github.com/mate-
  desktop/atril/commit/4650fb05e46e144be986a11a666a47add39b3799

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1698180] Re: [CVE] Send Later with Delay bypasses OpenPGP

[Launchpad Bug Tracker]

This bug was fixed in the package kdepim - 4:4.13.3-0ubuntu0.2

---
kdepim (4:4.13.3-0ubuntu0.2) trusty-security; urgency=medium

  * SECURITY UPDATE: Send Later with Delay bypasses OpenPGP (LP: #1698180):
- fix-CVE-2017-9604.patch
- CVE-2017-9604

 -- Simon Quigley   Sun, 25 Mar 2018 11:02:11 -0500

** Changed in: kdepim (Ubuntu Trusty)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1698180

Title:
  [CVE] Send Later with Delay bypasses OpenPGP

Status in kdepim package in Ubuntu:
  Invalid
Status in kf5-messagelib package in Ubuntu:
  Fix Released
Status in kmail package in Ubuntu:
  Fix Released
Status in kdepim source package in Trusty:
  Fix Released
Status in kdepim source package in Xenial:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

  Title:  KMail: Send Later with Delay bypasses OpenPGP
  Risk Rating:Medium
  CVE:CVE-2017-9604
  Versions:   kmail, messagelib < 5.5.2
  Date:   15 June 2017

  
  Overview
  
  KMail’s Send Later with Delay function bypasses OpenPGP signing and
  encryption, causing the message to be sent unsigned and in plain-text.

  Solution
  
  Update to kmail, messagelib >= 5.5.2 (Released as part of KDE Applications 
17.04.2)

  Or apply the following patches:
   kmail: 
https://commits.kde.org/kmail/78c5552be2f00a4ac25bd77ca39386522fca70a8
  messagelib: 
https://commits.kde.org/messagelib/c54706e990bbd6498e7b1597ec7900bc809e8197

  Credits
  ===
  Thanks to Daniel Aleksandersen for the report and to Laurent Montel for the 
fix.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1698180] Re: [CVE] Send Later with Delay bypasses OpenPGP

[Launchpad Bug Tracker]

This bug was fixed in the package kdepim - 4:15.12.3-0ubuntu1.1

---
kdepim (4:15.12.3-0ubuntu1.1) xenial-security; urgency=medium

  * SECURITY UPDATE: Send Later with Delay bypasses OpenPGP (LP: #1698180):
- fix-CVE-2017-9604.patch
- CVE-2017-9604

 -- Simon Quigley   Sun, 25 Mar 2018 07:38:25 -0500

** Changed in: kdepim (Ubuntu Xenial)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1698180

Title:
  [CVE] Send Later with Delay bypasses OpenPGP

Status in kdepim package in Ubuntu:
  Invalid
Status in kf5-messagelib package in Ubuntu:
  Fix Released
Status in kmail package in Ubuntu:
  Fix Released
Status in kdepim source package in Trusty:
  Fix Released
Status in kdepim source package in Xenial:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

  Title:  KMail: Send Later with Delay bypasses OpenPGP
  Risk Rating:Medium
  CVE:CVE-2017-9604
  Versions:   kmail, messagelib < 5.5.2
  Date:   15 June 2017

  
  Overview
  
  KMail’s Send Later with Delay function bypasses OpenPGP signing and
  encryption, causing the message to be sent unsigned and in plain-text.

  Solution
  
  Update to kmail, messagelib >= 5.5.2 (Released as part of KDE Applications 
17.04.2)

  Or apply the following patches:
   kmail: 
https://commits.kde.org/kmail/78c5552be2f00a4ac25bd77ca39386522fca70a8
  messagelib: 
https://commits.kde.org/messagelib/c54706e990bbd6498e7b1597ec7900bc809e8197

  Credits
  ===
  Thanks to Daniel Aleksandersen for the report and to Laurent Montel for the 
fix.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759003] Re: cloud-init fails for minimal images (can't find locale-gen)

[Michael Hudson-Doyle]

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759003

Title:
  cloud-init fails for minimal images (can't find locale-gen)

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  In Progress
Status in livecd-rootfs source package in Xenial:
  New

Bug description:
  Opening initially as a cloud-images bug to ensure that the lack of
  'locale-gen' is desired.  If so, then this should go to cloud-init to
  dtrt for minimal images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1759003/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Steve Langasek]

This is not an SRU-appropriate change and should not have been accepted
into artful.  Please revert this ASAP for artful.  Marking 'wontfix' for
xenial.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755769] Re: linux-azure-edge: 4.15.0-1003.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755769

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

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755762
  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/1755769/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1757223] Re: ubuntu-cpc: Don't build minimized artifacts that won't boot with linux-kvm

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.408.28

---
livecd-rootfs (2.408.28) xenial; urgency=medium

  * ubuntu-cpc: When performing a minimized build, don't generate artifacts
that won't boot with the linux-kvm kernel (LP: #1757223).

 -- Daniel Watkins   Tue, 20 Mar 2018
12:42:25 -0400

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1757223

Title:
  ubuntu-cpc: Don't build minimized artifacts that won't boot with
  linux-kvm

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released

Bug description:
  Currently, the ubuntu-cpc hooks execute for all builds, minimized or
  not.  As minimized images use the linux-kvm kernel, we shouldn't
  produce images for non-KVM platforms.  The hooks that need skipping
  are the ones that produce the VMDK, OVA and Vagrant box.

  Given that livecd-rootfs own the definition of minimized images, it
  should also own defining which images should be produced when a
  minimized build runs.

  [Impact]

  * Increased build time for minimized images
  * Publication of minimized cloud images that cannot possibly boot

  [Test Case]

  Run a minimized livefs build; the .vmdk, .ova and .box files should
  not be produced.  Run a regular livefs build, the .vmdk, .ova and .box
  files should be produced.

  [Regression Potential]

  The changes required are adding conditional "exit 0"s to the hooks in
  question, which aren't used by any other hooks.  The only potential
  regression would be either (a) syntax issues that would manifest
  obviously in a complete failure to build (and therefore cause the Test
  Case to fail), or (b) accidental exclusion of these image types for
  non-minimized builds, which is covered in the Test Case section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1757223/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1725921] Re: [regression] Combobox menus have gray text on gray background

[Łukasz Zemczak]

Hello Eldar, or anyone else affected,

Accepted ubuntu-themes into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/14.04+16.04.20180326-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Invalid

** Changed in: ubuntu-themes (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1725921

Title:
  [regression] Combobox menus have gray text on gray background

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Committed
Status in ubuntu-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Regression: After a recent update, combobox menus have gray text on
  gray background making them almost unreadable.

  [Test Case]

  1. Open GIMP and start a new file.
  2. At the bottom of the window click on the 'px' combo box.
  3. Verify the menu that appears has readable text (light grey text on a dark 
grey background).

  [Regression Potential]

  Very low. The fix changes the theme for "gtk-combobox-popup-menu"
  only. So theoretically it should not be possible for the fix to affect
  anything other than combobox menus.

  [Other Info]

  The regression happened in updates to 18.04, 17.10 and 16.04 around
  late 2017 - January 2018.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746666] Re: lspci fails with 'Error reading sysfs label: Operation not permitted'

[Launchpad Bug Tracker]

This bug was fixed in the package pciutils - 1:3.3.1-1.1ubuntu1.2

---
pciutils (1:3.3.1-1.1ubuntu1.2) xenial; urgency=medium

  * 
debian/patches/08-Sysfs-Read-failures-of-optional-attributes-are-not-f.patch:
Cherry-pick from upstream to support machines in which we have read
failures of optional attributes. (LP: #174)

 -- Chris J Arges   Wed, 14 Mar 2018 15:57:44
-0500

** Changed in: pciutils (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/174

Title:
  lspci fails with 'Error reading sysfs label: Operation not permitted'

Status in dellserver:
  Fix Committed
Status in pciutils package in Ubuntu:
  Fix Released
Status in pciutils source package in Xenial:
  Fix Released

Bug description:
  Description:
  On a 4 socket server, when #lspci is run, it fails with output:
  lspci: Error reading /sys/bus/pci/devices/:9a:00.0/label: Operation not 
permitted

  How Reproducible:
  Always

  Version
  pciutils-3.3.1-1.1ubuntu1.1

  Steps:
  1. Install Ubuntu-Server-16.04.3
  2. Observe #lspci

  Additional Info:
  * Upstream master branch from pciutils works fine in this setup. 
(https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/)

  * v3.4.0 also works fine in this setup.

  * v3.3.1 fails.

  * Going through code quickly, looks like one of the required patches is :
  
https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/+/ef6c9ec3a45992d9e7ef4716d444252baf2013e1

  Not sure what other patches might be required for fixing this.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755212] Re: linux-euclid: -proposed tracker

[Stefan Bader]

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

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

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

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

** Changed in: linux-euclid (Ubuntu Xenial)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755212

Title:
  linux-euclid:  -proposed tracker

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

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
  -- swm properties --
  kernel-stable-master-bug: 1755208
  phase: Packaging

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755213] Re: linux-raspi2: 4.4.0-1086.94 -proposed tracker

[Stefan Bader]

No derivative specific changes.

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755213

Title:
  linux-raspi2: 4.4.0-1086.94 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755208
  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/1755213/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755215] Re: linux-snapdragon: 4.4.0-1088.93 -proposed tracker

[Stefan Bader]

No derivative specific changes.

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755215

Title:
  linux-snapdragon: 4.4.0-1088.93 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755208
  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/1755215/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04 KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Invalid
Status in kexec-tools source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > 

[Group.of.nepali.translators] [Bug 1755767] Re: linux-hwe: 4.13.0-38.43~16.04.1 -proposed tracker

[Brad Figg]

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755767

Title:
  linux-hwe: 4.13.0-38.43~16.04.1 -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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755762
  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/1755767/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755771] Re: linux-gcp: 4.13.0-1012.16 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755771

Title:
  linux-gcp: 4.13.0-1012.16 -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 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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755762
  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/1755771/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.6

---
makedumpfile (1:1.5.9-5ubuntu0.6) xenial; urgency=medium

  * d/kernel-postinst-generate-initrd : Add scsi_dh_* modules if in
use so the system can dump a crash when root is on multipath
(LP: #1635597) (Closes: 862411)

  * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's
only used by ppc64el, it's not required to be conditionally added.
(LP: #1658733)

 -- Thadeu Lima de Souza Cascardo   Tue, 29 Aug
2017 16:56:04 -0300

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1635597

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Zesty:
  Won't Fix

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] 

[Group.of.nepali.translators] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.6

---
makedumpfile (1:1.5.9-5ubuntu0.6) xenial; urgency=medium

  * d/kernel-postinst-generate-initrd : Add scsi_dh_* modules if in
use so the system can dump a crash when root is on multipath
(LP: #1635597) (Closes: 862411)

  * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's
only used by ppc64el, it's not required to be conditionally added.
(LP: #1658733)

 -- Thadeu Lima de Souza Cascardo   Tue, 29 Aug
2017 16:56:04 -0300

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04 KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Invalid
Status in kexec-tools source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  

[Group.of.nepali.translators] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

[Timo Aaltonen]

shouldn't this apply to bionic too?

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Xenial:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.1-2ubuntu0.1

---
makedumpfile (1:1.6.1-2ubuntu0.1) artful; urgency=medium

  * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's
only used by ppc64el, it's not required to be conditionally added.
(LP: #1658733)
  * Set crashkernel for ppc64el to load at 128M instead of 32M. That allows
larger kernels to boot. (LP: #1728115)

 -- Thadeu Lima de Souza Cascardo   Tue, 07 Nov
2017 12:23:33 +

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04 KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Invalid
Status in kexec-tools source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins 

[Group.of.nepali.translators] [Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.16.04.2

---
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium

  * Really point to 5.1.34 source to download

virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) xenial; urgency=medium

  * New upstream release
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9
  * Update license key and text.

 -- Gianfranco Costamagna   Thu, 15 Mar 2018
12:26:08 +0100

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736116

Title:
  [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  [Impact]
  * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
  * VM not able to start, 3d not working
  [Test Case]
  * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic

  [Regression Potential]
  * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
  No regressions when we moved 5.0.18 to 5.0.40

  The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
  and with a lot of security issues, we should try to get the move in
  Xenial, to make vbox continue working.

  5.2 can't build there, because of a lot of qtbase issues, so sticking
  with 5.1 is the only viable solution we found over the last 4 months

  For this reason, we need a new kbuild too

  [Other Info]
  This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.17.10.1

---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium

  * New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
14:49:24 +0100

** Changed in: virtualbox (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736116

Title:
  [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  [Impact]
  * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
  * VM not able to start, 3d not working
  [Test Case]
  * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic

  [Regression Potential]
  * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
  No regressions when we moved 5.0.18 to 5.0.40

  The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
  and with a lot of security issues, we should try to get the move in
  Xenial, to make vbox continue working.

  5.2 can't build there, because of a lot of qtbase issues, so sticking
  with 5.1 is the only viable solution we found over the last 4 months

  For this reason, we need a new kbuild too

  [Other Info]
  This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.16.04.2

---
virtualbox (5.1.34-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium

  * New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Apply 69989 to fix GL issue.
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
13:27:46 +0100

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736116

Title:
  [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  [Impact]
  * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
  * VM not able to start, 3d not working
  [Test Case]
  * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic

  [Regression Potential]
  * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
  No regressions when we moved 5.0.18 to 5.0.40

  The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
  and with a lot of security issues, we should try to get the move in
  Xenial, to make vbox continue working.

  5.2 can't build there, because of a lot of qtbase issues, so sticking
  with 5.1 is the only viable solution we found over the last 4 months

  For this reason, we need a new kbuild too

  [Other Info]
  This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746316] Re: [SRU] VirtualBox needs Security Patches

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.17.10.2

---
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.2) artful; urgency=medium

  * Really point to 5.1.34 source to download

virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium

  * New upstream release
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9
  * Update license key and text.

 -- Gianfranco Costamagna   Thu, 15 Mar 2018
12:26:08 +0100

** Changed in: virtualbox-guest-additions-iso (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746316

Title:
  [SRU] VirtualBox needs Security Patches

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in kbuild source package in Artful:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746316] Re: [SRU] VirtualBox needs Security Patches

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.16.04.2

---
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium

  * Really point to 5.1.34 source to download

virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) xenial; urgency=medium

  * New upstream release
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9
  * Update license key and text.

 -- Gianfranco Costamagna   Thu, 15 Mar 2018
12:26:08 +0100

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746316

Title:
  [SRU] VirtualBox needs Security Patches

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in kbuild source package in Artful:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746316] Re: [SRU] VirtualBox needs Security Patches

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.16.04.2

---
virtualbox (5.1.34-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium

  * New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Apply 69989 to fix GL issue.
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
13:27:46 +0100

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746316

Title:
  [SRU] VirtualBox needs Security Patches

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in kbuild source package in Artful:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.17.10.2

---
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.2) artful; urgency=medium

  * Really point to 5.1.34 source to download

virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium

  * New upstream release
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9
  * Update license key and text.

 -- Gianfranco Costamagna   Thu, 15 Mar 2018
12:26:08 +0100

** Changed in: virtualbox-guest-additions-iso (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736116

Title:
  [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  [Impact]
  * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
  * VM not able to start, 3d not working
  [Test Case]
  * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic

  [Regression Potential]
  * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
  No regressions when we moved 5.0.18 to 5.0.40

  The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
  and with a lot of security issues, we should try to get the move in
  Xenial, to make vbox continue working.

  5.2 can't build there, because of a lot of qtbase issues, so sticking
  with 5.1 is the only viable solution we found over the last 4 months

  For this reason, we need a new kbuild too

  [Other Info]
  This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746316] Re: [SRU] VirtualBox needs Security Patches

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.17.10.1

---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium

  * New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
14:49:24 +0100

** Changed in: virtualbox (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746316

Title:
  [SRU] VirtualBox needs Security Patches

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in kbuild source package in Artful:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746316] Re: [SRU] VirtualBox needs Security Patches

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.17.10.2

---
virtualbox (5.1.34-dfsg-0ubuntu1.17.10.2) artful; urgency=medium

  * New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Apply 69989 to fix GL issue.
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
13:27:46 +0100

** Changed in: virtualbox (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: virtualbox-ext-pack (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746316

Title:
  [SRU] VirtualBox needs Security Patches

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in kbuild source package in Artful:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.17.10.2

---
virtualbox (5.1.34-dfsg-0ubuntu1.17.10.2) artful; urgency=medium

  * New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel >= 4.13
  * Apply 69989 to fix GL issue.
  * Lower compat level to 9

 -- Gianfranco Costamagna   Fri, 02 Feb 2018
13:27:46 +0100

** Changed in: virtualbox (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: virtualbox-ext-pack (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736116

Title:
  [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

Status in kbuild package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in kbuild source package in Xenial:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released
Status in virtualbox source package in Artful:
  Fix Released
Status in virtualbox-ext-pack source package in Artful:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Artful:
  Fix Released

Bug description:
  [Impact]
  * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
  * VM not able to start, 3d not working
  [Test Case]
  * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic

  [Regression Potential]
  * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
  No regressions when we moved 5.0.18 to 5.0.40

  The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
  and with a lot of security issues, we should try to get the move in
  Xenial, to make vbox continue working.

  5.2 can't build there, because of a lot of qtbase issues, so sticking
  with 5.1 is the only viable solution we found over the last 4 months

  For this reason, we need a new kbuild too

  [Other Info]
  This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755767] Re: linux-hwe: 4.13.0-38.43~16.04.1 -proposed tracker

[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.13.0-38.43~16.04.1/xenial-4.13-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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755767

Title:
  linux-hwe: 4.13.0-38.43~16.04.1 -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:
  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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755762
  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/1755767/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1741807] Re: NVIDIA Spectre attack fixes

[Mathew Hodson]

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: nvidia
 Assignee: jerahmia gaither (bearahmia) => (unassigned)

** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715

** Project changed: nvidia => ubuntu-translations

** No longer affects: ubuntu-translations

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1741807

Title:
  NVIDIA Spectre attack fixes

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Zesty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Artful:
  Fix Released

Bug description:
  According to http://nvidia.custhelp.com/app/answers/detail/a_id/4611
  the NVIDIA driver needs to be updated to 384.111 to fix the Spectre
  vulnerabilities in the NVIDIA kernel modules (along with the upcoming
  Kernel security patches).

  I think this update should be pushed ASAP to all support Ubuntu
  releases as a security update.

  It seems so far only CVE-2017-5753 (variant 1) has been addressed and
  a future NVIDIA update will also address CVE-2017-5715 (variant 2)

  Please note there is also a updated version 390.12 for the R390 branch
  in case that is also provided somewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1741807/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp