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

2018-01-03 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1083.88/snapdragon-4.4-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/1737927

Title:
  linux-snapdragon: 4.4.0-1083.88 -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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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:
  Fix Released
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: 1737916
  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/1737927/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

2018-01-03 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: New => 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/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1737923] Re: linux-kvm: 4.4.0-1014.19 -proposed tracker

2018-01-03 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1737923

Title:
  linux-kvm: 4.4.0-1014.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1737916
  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/1737923/+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 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

2018-01-03 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1737920

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1737916
  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/1737920/+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 1737925] Re: linux-raspi2: 4.4.0-1081.89 -proposed tracker

2018-01-03 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1737925

Title:
  linux-raspi2: 4.4.0-1081.89 -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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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:
  Fix Released
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: 1737916
  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/1737925/+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 1613900] Re: Unable to use 'Any' availability zone when spawning instance

2018-01-03 Thread Corey Bryant
** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

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

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: horizon (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: horizon (Ubuntu)
   Status: In Progress => Invalid

** Changed in: cloud-archive
   Status: In Progress => Invalid

** Changed in: cloud-archive/mitaka
 Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: horizon (Ubuntu Xenial)
 Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: cloud-archive/mitaka
 Assignee: Shane Peters (shaner) => (unassigned)

** Changed in: cloud-archive/mitaka
 Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: cloud-archive
 Assignee: Shane Peters (shaner) => (unassigned)

** Changed in: horizon (Ubuntu)
 Assignee: Shane Peters (shaner) => (unassigned)

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

Title:
  Unable to use 'Any' availability zone when spawning instance

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Xenial:
  Triaged

Bug description:
  While using Mitaka, we found that by default, using js backend, it is
  not possible to choose 'any' availability zone. The issue is not fixed
  in master branch.

  For python implementation the logic is:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L390

  The JS implementation miss the logic if number of AZs is >1
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L321

  Also, JS implementation looks ugly if you have lot of subnets per
  network...

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1613900/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.1-0ubuntu2.15

---
apport (2.20.1-0ubuntu2.15) xenial-security; urgency=medium

  * REGRESSION UPDATE: Fix regression that caused a Traceback in the
container support (LP: #1733366)
- data/apport: add a second os.path.exists check to ensure we do not
  receive a Traceback in is_container_id() and add an exception handler in
  case either name space can not be found.

 -- Brian Murray   Wed, 13 Dec 2017 10:54:26 -0800

** Changed in: apport (Ubuntu Artful)
   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/1733366

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2

  ---

  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:

  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.4-0ubuntu4.10

---
apport (2.20.4-0ubuntu4.10) zesty-security; urgency=medium

  * REGRESSION UPDATE: Fix regression that caused a Traceback in the
container support (LP: #1733366)
- data/apport: add a second os.path.exists check to ensure we do not
  receive a Traceback in is_container_id() and add an exception handler in
  case either name space can not be found.

 -- Brian Murray   Wed, 13 Dec 2017 10:51:39 -0800

** Changed in: apport (Ubuntu Zesty)
   Status: Confirmed => Fix Released

** Changed in: apport (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/1733366

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2

  ---

  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:

  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 235-3ubuntu3

---
systemd (235-3ubuntu3) bionic; urgency=medium

  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
(LP: #1734410)

 -- Dimitri John Ledkov   Tue, 12 Dec 2017 13:25:32
+

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => 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/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:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  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 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 235-3ubuntu3

---
systemd (235-3ubuntu3) bionic; urgency=medium

  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
(LP: #1734410)

 -- Dimitri John Ledkov   Tue, 12 Dec 2017 13:25:32
+

** Changed in: systemd (Ubuntu Bionic)
   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/1734410

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1737570] Re: Add support for RequiredForOnline in networkd

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 235-3ubuntu3

---
systemd (235-3ubuntu3) bionic; urgency=medium

  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
(LP: #1734410)

 -- Dimitri John Ledkov   Tue, 12 Dec 2017 13:25:32
+

** Changed in: systemd (Ubuntu Bionic)
   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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno

2018-01-03 Thread Seth Forshee
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Amitkumar Karwar (amitkarwar)

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

Title:
  Connection issue in Bluetooth SPP mode between a Dell Edge Gateway
  3000 and an HC-05 BT module attached to Arduino Uno

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Connection issue in Bluetooth SPP mode between a Dell Edge
  Gateway 3000 and an HC-05 BT module attached to Arduino Uno

  Fix: Updated firmware from Redpine containing a fix for the issue.

  Regression Potential: Below stress tests are conducted to ensure there is no 
regression with updated firmware
  BT mouse + BT keyboard
  BT mouse + BLE keyboard
  BT keyboard + BLE mouse
  BLE keyboard + BLE mouse
  BT mouse or keyboard + Wifi connected
  BT mouse + BT keyboard + WiFi connected
  BLE mouse + BLE keyboard + WiFi Connected
  BT mouse + BLE keyboard + Wifi connected
  BLE mouse + BT keyboard + Wifi connected
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + 
BLE scan
  BT file transfer from mobile + WiFi connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738773/+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 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly

2018-01-03 Thread Dimitri John Ledkov
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu2~16.04.1

---
libseccomp (2.3.1-2.1ubuntu2~16.04.1) xenial; urgency=medium

  * Backport libseccomp 2.3.1 to xenial LP: #1682102
- Improved s390x support
- Improved support for v4.5+ kernels

 -- Dimitri John Ledkov  Fri, 06 Oct 2017 14:47:39
+0100

** Changed in: libseccomp (Ubuntu Xenial)
   Status: Triaged => Fix Released

** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1679691

Title:
  libseccomp fix - s390: handle multiplexed syscalls correctly

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in libseccomp package in Ubuntu:
  Invalid
Status in libseccomp source package in Xenial:
  Fix Released
Status in libseccomp source package in Artful:
  Invalid

Bug description:
  Within Xenial version 2.2.3 of seccomp is included.
  With Yaketty version 2.3.1 is available and fixed this problem.

  Even Docker is working on a SNAP solution, please provide the fix to
  16.04.

  
  With following patches this can be applied to 2.2.3 in support of the 16.04 
LTS Release
  16.04

  Here the upstream git commits for the patches:

  0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch
  1d63fad4a064b80e0b921b16ed419f3342337ed4
   
  0001-all-block-negative-syscall-numbers-from-the-filter.patch
  51c46f80c1edee863bbc4eb21b03decc44e69a45 

  0001-api-limit-errno-values-to-MAX_ERRNO.patch
  0d287caf43792239b107ee3215b32b8bc901f9c3 

  0001-db-fix-a-minor-style-problem.patch
  61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 

  0001-db-make-the-individual-db-filter-ops-private.patch
  a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16

  0001-db-store-the-rules-used-to-build-the-filter.patch
  f16f405f61ecdbad202257b61004b85fce64d75c 

  0001-arch-make-use-of-function-tables-instead-of-switch-s.patch
  57df79c166b26d5044e7e27099e6e69671e727dd 

  0001-db-introduce-transaction-support.patch
  9be1538a4ac0e45047a3f1b79691505c3d11ca31 

  0001-arch-move-the-low-level-filter-rule-addition-code-in.patch
  996e445a74823c735757413fda809e1ed0afc7d4 

  0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch
  5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 

  0001-arch-basic-support-for-multiplexed-and-direct-socket.patch
  d32c3bfa4b07add90dcd04292eb4ba278dd103ba 

  0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch
  983835f3e0fd000a42c8beaea9d7fbe72665 

  0001-tests-add-a-test-for-the-different-types-of-socket-s.patch
  099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 

  0001-api-add-a-seccomp_version-API-call.patch
  58a7c20d4c2defc1c984c5c7391ecc60093f85fa 

  0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch
  8ed78c3859f476d302995b43d6739f3341f5b37d 

  0001-s390-handle-multiplexed-syscalls-correctly.patch
  47516603828396f85107ea3e2a254958c2bc3ff5 

  0001-arch-fix-the-multiplexed-ipc-syscalls.patch
  3a89bd144885f54aff86f2e275859a1483992edd

  With the following additional commit all tests pass with "make check"

  0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch
  0d8504bc192e0989494df06efc4b186a9f02e20a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+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 1738797] Re: linux-oem: 4.13.0-1013.14 -proposed tracker

2018-01-03 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-oem: 4.13.0-1013.14 -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 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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1738791
  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/1738797/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu3.1

---
ntp (1:4.2.8p10+dfsg-5ubuntu3.1) artful; urgency=medium

  * debian/apparmor-profile: add attach_disconnected which is needed in some
cases to let ntp report its log messages (LP: #1727202).

 -- Christian Ehrhardt   Mon, 18 Dec
2017 13:19:36 +0100

** Changed in: ntp (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/1727202

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Invalid
Status in ntp source package in Zesty:
  Invalid
Status in ntp source package in Artful:
  Fix Released
Status in ntp source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu2.4

---
unattended-upgrades (0.93.1ubuntu2.4) zesty; urgency=medium

  * unattended-upgrade: Do not reboot during a dry-run. (LP: #1269177)

 -- Brian Murray   Tue, 19 Dec 2017 14:46:42 -0800

** Changed in: unattended-upgrades (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: unattended-upgrades (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/1269177

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Zesty:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  An Ubuntu system will unexpectedly reboot if reboot-required exists and you 
run unattended-upgrades in dry-run mode.

  Test Case
  -
  1) modify /etc/apt/apt.conf.d/50unattended-upgrades so that Automatic-Reboot 
is true
  2) Ensure all updates are installed
  3) sudo touch /var/run/reboot-required
  4) run 'sudo unattended-upgrades --dry-run'
  5) watch the system reboot

  With the version of unattended-upgrades from -proposed the system will
  not reboot.

  Regression Potential
  
  This checks to see if the --dry-run switch is passed to unattended-upgrades 
before calling the reboot function. I guess it would be a regression to people 
who expect the system to reboot but that seems like a very strange corner case.

  Original Description
  
  Much to my surprise, when I did a dry-run test of unattended-upgrades my 
server was forcibly rebooted. I must have had the file 
'/var/run/reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages:
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.9

---
unattended-upgrades (0.90ubuntu0.9) xenial; urgency=medium

  * unattended-upgrade: Do not reboot during a dry-run. (LP: #1269177)

 -- Brian Murray   Tue, 19 Dec 2017 14:51:05 -0800

** Changed in: unattended-upgrades (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/1269177

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Zesty:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  An Ubuntu system will unexpectedly reboot if reboot-required exists and you 
run unattended-upgrades in dry-run mode.

  Test Case
  -
  1) modify /etc/apt/apt.conf.d/50unattended-upgrades so that Automatic-Reboot 
is true
  2) Ensure all updates are installed
  3) sudo touch /var/run/reboot-required
  4) run 'sudo unattended-upgrades --dry-run'
  5) watch the system reboot

  With the version of unattended-upgrades from -proposed the system will
  not reboot.

  Regression Potential
  
  This checks to see if the --dry-run switch is passed to unattended-upgrades 
before calling the reboot function. I guess it would be a regression to people 
who expect the system to reboot but that seems like a very strange corner case.

  Original Description
  
  Much to my surprise, when I did a dry-run test of unattended-upgrades my 
server was forcibly rebooted. I must have had the file 
'/var/run/reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages:
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 1734856] Re: Can't boot VM with more than 16 disks (slof buffer issue)

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package slof - 20151103+dfsg-1ubuntu1.1

---
slof (20151103+dfsg-1ubuntu1.1) xenial; urgency=medium

  * Fix boot with more than 16 disks (LP: #1734856)
- d/p/0001-boot-do-not-concatenate-bootdev.patch
- d/p/0002-boot-use-a-temporary-bootdev-buf.patch

 -- Christian Ehrhardt   Mon, 18 Dec
2017 14:12:32 +0100

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

** Changed in: slof (Ubuntu Zesty)
   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/1734856

Title:
  Can't boot VM with more than 16 disks (slof buffer issue)

Status in SLOF - Slimline Open Firmware:
  New
Status in The Ubuntu-power-systems project:
  Incomplete
Status in slof package in Ubuntu:
  Fix Released
Status in slof source package in Xenial:
  Fix Released
Status in slof source package in Zesty:
  Fix Released
Status in slof source package in Artful:
  Fix Released
Status in slof source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Booting a KVM guest with many disks considered as potential boot device 
 fails on ppc64le

   * In detail this was an overflow, so now the processing of devices is 
 changed to use dynamic allocation which works with higher numbers of 
 devices.

  [Test Case]

   * Comment #12 has the full final testcase, not writing all that up 
 here again.

  [Regression Potential]

   * It is a change of disk processing in the slof loader for ppc64el
 - that means on one hand only ppc64el will be affected by an issue
 - OTOH there might be a disk combination not part of my or upstreams or 
   IBMs testing that might now fail with the new code (unlikely)
 - Given that the change is upstream and was provided by IBM which I 
   consider the authority on that code I think it is safe to be 
   considered.

  [Other Info]
   
   * n/a

  
  


  == Comment: #0 - RAHUL CHANDRAKAR  - 2017-11-28 03:40:37 
==
  ---Problem Description---
  Can't boot VM with more than 16 disks.
  It is an issue with qemu/SLOF (Bug: https://github.com/qemu/SLOF/issues/3) 
and it was fixed by Nikunj Amritlal Dadhnia.  He has made a patch available and 
it has been tested by PowerVC team.

  We need this fix in Ubuntu 16.04 and later releases.

  Machine Type = 8348-21C (P8 Habanero)

  ---Steps to Reproduce---
   Steps to recreate:
  1. Create a VM
  2. Attach 50 disks
  3. Shutdown from OS
  4. Start again and let it boot

  ---uname output---
  Linux neo160.blr.stglabs.ibm.com 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 
18:29:11 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ---Debugger---
  A debugger is not configured

  Patch posted and awaiting response...

  http://patchwork.ozlabs.org/patch/842011/

To manage notifications about this bug go to:
https://bugs.launchpad.net/slof/+bug/1734856/+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 1734207] Re: Multiple PSKs with dyndns left/rightids doesn't work

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package strongswan - 5.3.5-1ubuntu3.5

---
strongswan (5.3.5-1ubuntu3.5) xenial; urgency=medium

  * d/p/ikev1-First-do-PSK-lookups-lp1734207.patch ensure evaluation
with resolvable hostnames selects the right PSK (LP: #1734207).

 -- Christian Ehrhardt   Mon, 18 Dec
2017 11:22:24 +0100

** Changed in: strongswan (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/1734207

Title:
  Multiple PSKs with dyndns left/rightids doesn't work

Status in strongswan package in Ubuntu:
  Fix Released
Status in strongswan source package in Xenial:
  Fix Released
Status in strongswan source package in Zesty:
  Fix Released
Status in strongswan source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * charon unnecessarily selects a wrong PSK in some cases:
 * A site-to-site connection using resolvable hostnames (e.g., DynDNS) as 
identities in /etc/ipsec.secrets and a Roadwarrior connection (using %any as 
remote peer identity)
 * Multiple site-to-site connections using resolvable hostnames as 
identities

   * Fix is a backport from upstream in since 5.5.2

  [Test Case]

   * There are detailed steps on how to configure for this case on 
 https://wiki.strongswan.org/issues/2223

  [Regression Potential]

   * It is known (see discussion in upstream bug) that this can slightly 
 increase the connection setup as it adds a dns query. But un-breaking 
 the covered use cases was considered worth to do so upstream, and so 
 should we.

   * By changing the IKEv1 PSK codepath is the only changed path, so this is 
 the area where unexpected regressions could occur. None of the testing 
 found some so far and since upstream didn't change it for a while it 
 seems safe to me.

  [Other Info]
   
* n/a

  ---

  See: https://wiki.strongswan.org/issues/2223

  There is a chance to get an backport into xenial?

  It's fixed in the upstream version 5.5.2

  # apt-cache policy strongswan
  strongswan:
    Installed: 5.3.5-1ubuntu3.4
    Candidate: 5.3.5-1ubuntu3.4

  # lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1734207/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.2

---
mesa (17.2.4-0ubuntu1~16.04.2) xenial; urgency=medium

  * control: Relax build-dep on libclc-dev

 -- Timo Aaltonen   Wed, 22 Nov 2017 16:25:17 +0200

** Changed in: xorg-server-hwe-16.04 (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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-5.0 - 1:5.0-3~16.04.1

---
llvm-toolchain-5.0 (1:5.0-3~16.04.1) xenial; urgency=medium

  * Backport to xenial. (LP: #1716203)
- Don't build the Fuzzer library on powerpc.
- set BINUTILS_GOLD_ARCHS to match 4.0, dropping arm64 and s390x

 -- Timo Aaltonen   Tue, 10 Oct 2017 18:09:29 +0300

** Changed in: mesa (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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package wayland-protocols - 1.10-1~16.04.1

---
wayland-protocols (1.10-1~16.04.1) xenial; urgency=medium

  * Backport to xenial. (LP: #1716203)
- use debhelper 9

 -- Timo Aaltonen   Tue, 19 Sep 2017 12:48:31 +0300

** Changed in: llvm-toolchain-5.0 (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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libclc - 0.2.0+git20170330-3~16.04.1

---
libclc (0.2.0+git20170330-3~16.04.1) xenial; urgency=medium

  * Backport to xenial. (LP: #1716203)
- don't use debhelper 10

 -- Timo Aaltonen   Mon, 13 Nov 2017 19:11:36 +0200

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

** Changed in: wayland-protocols (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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.2

---
mesa (17.2.4-0ubuntu1~16.04.2) xenial; urgency=medium

  * control: Relax build-dep on libclc-dev

 -- Timo Aaltonen   Wed, 22 Nov 2017 16:25:17 +0200

** Changed in: mesa (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/1720890

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1727390] Re: New bugfix release 17.2.4

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.2

---
mesa (17.2.4-0ubuntu1~16.04.2) xenial; urgency=medium

  * control: Relax build-dep on libclc-dev

 -- Timo Aaltonen   Wed, 22 Nov 2017 16:25:17 +0200

** Changed in: mesa (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/1727390

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libdrm - 2.4.83-1~16.04.1

---
libdrm (2.4.83-1~16.04.1) xenial; urgency=medium

  * Backport to xenial. (LP: #1716203)
- use dh9

 -- Timo Aaltonen   Tue, 10 Oct 2017 17:28:59 +0300

** Changed in: libdrm (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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

2018-01-03 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.2

---
mesa (17.2.4-0ubuntu1~16.04.2) xenial; urgency=medium

  * control: Relax build-dep on libclc-dev

 -- Timo Aaltonen   Wed, 22 Nov 2017 16:25:17 +0200

** Changed in: mesa (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/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Timo Aaltonen
** Changed in: vulkan (Ubuntu)
   Status: New => 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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

2018-01-03 Thread Timo Aaltonen
** Also affects: vulkan (Ubuntu)
   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/1716203

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  New
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1737916] Re: linux: 4.4.0-105.128 -proposed tracker

2018-01-03 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1737916

Title:
  linux: 4.4.0-105.128 -proposed tracker

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

  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737916/+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 1737925] Re: linux-raspi2: 4.4.0-1081.89 -proposed tracker

2018-01-03 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1081.89/raspi2-4.4-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/1737925

Title:
  linux-raspi2: 4.4.0-1081.89 -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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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:
  Fix Released
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: 1737916
  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/1737925/+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