[Group.of.nepali.translators] [Bug 1731146] [NEW] SRU of LXD 2.0.11 (upstream bugfix release)

[Stéphane Graber]

Public bug reported:

LXD upstream released LXD 2.0.11 as a bugfix release with following changelog:
- It's now possible to interrupt image downloads
- Added a new security.idmap.base config key
  (overrides the base uid/gid of the container)
- Added support for delta image downloads
- Implemented instance types as a proxy for resource limits
- The user-agent string was expanded to include OS and kernel information
- The client library and related code is now kept in sync with master
- The command line client has been ported to the new client library

- client: Add CancelTarget to RemoteOperation
- client: Add CreateContainerFromImage function
- client: Added insecureSkipVerify flag the ConnectionArgs struct
- client: Add extra exec option to block on I/O
- client: Add GetServerResources()
- client: Add GetStoragePoolResources()
- client: Add image_create_aliases backward compat
- client: Add RenameStoragePoolVolume()
- client: Allow canceling image download from LXDs
- client: Allow specifying base http client
- client: Cleanup code duplication in image download code
- client: Commonize error handling
- client: Don't live migrate stopped containers
- client: Drop experimental tag from new client
- client: Fail if source isn't listening on network
- client: Fix crash in operation handler
- client: Fix crash when missing cookiejar
- client: Fix handling of public LXD remote
- client: Fix image copy
- client: Fix non-interactive exec hangs
- client: Fix potential race in event handler setup
- client: Fix race condition in operation handling
- client: Implement container and snapshot copy
- client: Implement push and relay container copy
- client: Implement remote operations
- client: Improve error on image copy
- client: Improve migration relay code
- client: Keep track of protocol
- client: Make it possible to retrieve HTTP client
- client: Make the authentication Interactor configurable
- client: Move CopyImage to the target server
- client: Only set file headers if value is provided
- client: Properly handle remote disconnections
- client: Reduce request logging to Debug
- client: Simplify ConnectPublicLXD logic
- client: Support for macaroons-based authentication
- client: Sync with master branch
- client: Use RemoteOperation for CopyImage
- config: Add support for CookieJar
- config: Try to be clever about ":" in snapshots
- doc: Add a note about blkio limits
- doc: Add section on macvlan vs bridge
- doc: Add SUPPORT.md
- doc: Document instance types
- doc: Document that squashfs images can also be used
- doc: Document the exec control API
- doc: Extend/rework security-related documentation.
- doc: Fix lxd.log location in issue template
- doc: Fix spaces, commas, quotes, brackets where needed
- doc: Initial documentation of container env
- doc: Refresh the issue template
- doc: Seriously rework the content of the README
- doc: Sort container config keys
- doc: Sort server.md config keys
- doc: Update containers.md
- extra/lxc-to-lxd: Fix bad test
- extra/lxc-to-lxd: Ignore capabilities dropped by default
- extra/lxc-to-lxd: Ignore sysfs/proc mounts
- extra/lxc-to-lxd: Properly handle lxc.seccomp
- i18n: Update Japanese translation (for stable-2.0)
- lxc: Add plumbing for operation cancelation
- lxc: Cross-platform HOME handling
- lxc: Fix help to provide sample that actually works
- lxc: Fix import crash when adding properties
- lxc: Fix race in progress reporter
- lxc: Properly record alias source on copy
- lxc: Re-introduce remote protocol migration
- lxc: Respect HOME if set
- lxc/config: Removal of multiple devices at once
- lxc/copy: Report progress data
- lxc/delete: Fix lxc delete --force description
- lxc/exec: Fix signal handler for Windows
- lxc/exec: Fix Windows port
- lxc/file: Fix file push/pull with names containing spaces.
- lxc/file: Read file perms from Windows FS
- lxc/file: Use shared.HostPath for push/pull
- lxc/image: Always use long fingerprint in exported filenames
- lxc/image: Expose the "cached" flag
- lxc/image: Fix aliases with simplestreams remotes
- lxc/image: Fix "lxc image copy" not recording the source
- lxc/image: Fix regression in exported filename
- lxc/image: Improve filter handling
- lxc/image: Make "lxc image copy" fast again
- lxc/image: Update image aliases when they already exist
- lxc/image: Use shared.HostPath for import/export
- lxc/init: Fix failure to launch containers with random names
- lxc/list: Error if --columns and --fast are used together
- lxc/move: Use force on delete
- lxc/publish: Fix fingerprint printing
- lxc/remote: Don't require a cert for public remotes

[Group.of.nepali.translators] [Bug 1693340] Re: SRU of LXD 2.0.10 (upstream bugfix release)

[Stéphane Graber]

** Changed in: lxd (Ubuntu Trusty)
   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/1693340

Title:
  SRU of LXD 2.0.10 (upstream bugfix release)

Status in lxd package in Ubuntu:
  Invalid
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

Bug description:
  LXD upstream released LXD 2.0.10 as a bugfix release with following changelog:
  - client: Backported the new client library and ported some of the
internal commands over to it
  - lxc: Add a manpage command
  - lxc: Allow --version to be passed with any command
  - lxc: Reworked all help messages in the client to work with help2man
  - lxd: AppArmor namespacing is now also enabled for privileged containers

  - build: Add debug logging
  - client: Fix profile list
  - client: Remove unneeded condition
  - doc: Add instructions to grow ZFS loop
  - doc: Add note about escaping btrfs qgroups
  - doc: Add note about restricting access to kernel ring buffer
  - doc: Extract containers documentation to containers.md
  - doc: Extract profiles documentation to profiles.md
  - doc: Extract server documentation to server.md
  - doc: Fix badly named example device
  - doc: Fix broken table
  - doc: Note that LXD assumes full control over the pool
  - doc: Update configuration.md with links to other documents
  - doc: Update README.md for new API client
  - extra/lxc-to-lxd: Don't crash on missing mount file
  - extra/lxc-to-lxd: Typo in description of --move-rootfs
  - extra/vagrant: Trailing whitespace
  - global: Fix error handling in all filepath.Walk calls
  - global: Fix a number of typos
  - global: Forward user-agent and other headers on redirect
  - global: Replace file Chmod() with os.Chmod()
  - global: Use containerGetParentAndSnapshotName()
  - global: Use RunCommand everywhere
  - lxc: Don't include spaces in translated strings
  - lxc: Improve batch mode
  - lxc: Make help/usage a bit more consistent
  - lxc: Move common functions/types to utils.go
  - lxc: Properly clear transfer stats on error
  - lxc: Rework for better manpages
  - lxc/config: Add new config handling code
  - lxc/config: Always use "simplestreams" for images:
  - lxc/config: Fix path handling
  - lxc/config: Fix SaveConfig's DeepCopy call
  - lxc/copy: Improve error handling
  - lxc/copy: Return the source error too
  - lxc/copy: Simplify
  - lxc/copy: Wait asynchronously
  - lxc/image: Show the alias description
  - lxc/image: Trailing whitespace
  - lxc/init: Drop unnecessary else statement
  - lxc/list: Document list format options
  - lxc/list: Fix regression in json output
  - lxc/list: Move common data extraction to a helper function
  - lxc/profile: Properly implement "profile unset"
  - lxc/publish: Wait for the conainer to be running
  - lxc/remote: Show the fingerprint as string not hex
  - lxc/utils: Implement progress tracking for operations
  - lxd: Drop use of logger.Log when not needed
  - lxd/apparmor: Fix AppArmor stack handling with nesting
  - lxd/containers: Add containerGetParentAndSnapshotName()
  - lxd/containers: Added soft limit in initLXD()
  - lxd/containers: Added soft memory limit even when hard is selected
  - lxd/containers: Add extra validation for unix-block/unix-char
  - lxd/containers: Add function to detect root disk device
  - lxd/containers: Allow for stable host interface names
  - lxd/containers: Clarify uid/gid error
  - lxd/containers: Cleanup root device validation
  - lxd/containers: Disable IPv6 on host side veth when bridged
  - lxd/containers: Don't ignore snapshot deletion failures
  - lxd/containers: Don't parse id ranges as int32
  - lxd/containers: Don't report migration success on failure
  - lxd/containers: Don't use FindProcess, just pass exec.Cmd
  - lxd/containers: Find current max snapshot value
  - lxd/containers: Fix bad root device detection code
  - lxd/containers: Fix base image tracking
  - lxd/containers: Fix concurent read/write to s.conns in exec
  - lxd/containers: Fix error handling on FileRemove
  - lxd/containers: Fix handling of devices with minor>255
  - lxd/containers: Fix override of Devices during copy
  - lxd/containers: Fix soft limit logic to use float64
  - lxd/containers: Initialize idmap on demand
  - lxd/containers: Kill forkexec on abnormal websocket closure
  - lxd/containers: Path may only be used by one disk
  - lxd/containers: Properly invalidate the idmap cache
  - lxd/containers: Properly revert memory limits on failure
  

[Group.of.nepali.translators] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: oem-priority/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/1107935

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+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 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

** Changed in: linux (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Artful)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Zesty)
   Status: New => Won't Fix

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

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

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

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

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

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

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

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  New
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  In Progress

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729573/+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 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Łukasz Zemczak]

** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  New

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1107935] Re: Support for WPA Enterprise wireless networks

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu0.16.04.4

---
network-manager-applet (1.2.6-0ubuntu0.16.04.4) xenial; urgency=medium

  * debian/patches/git_fix_wrong_status_for_wireless_toggle.patch:
* Fix failing to load / use nma gir bindings. LP: #1107935

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 15:04:49
+

** Changed in: network-manager-applet (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/1107935

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+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 1107935] Re: Support for WPA Enterprise wireless networks

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 2.21.63.5

---
ubiquity (2.21.63.5) xenial; urgency=medium

  * Cherry-pick support for WPA2 Enterprise. LP: #1107935
  * Automatic update of included source packages: console-setup
1.108ubuntu15.4.

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 17:45:29
+

** Changed in: ubiquity (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/1107935

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+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 1726809] Re: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.90-0ubuntu0.17.04.2

---
nvidia-graphics-drivers-384 (384.90-0ubuntu0.17.04.2) zesty-proposed; 
urgency=medium

  * debian/rules,
debian/templates/nvidia-graphics-drivers.links.in,
debian/templates/nvidia-graphics-drivers.links32.in:
- Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone   Mon, 30 Oct 2017
17:32:58 +0100

** Changed in: nvidia-graphics-drivers-384 (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/1726809

Title:
  Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

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

Bug description:
  SRU Request:

  [Impact]
  Vulkan support is broken because the packages ship a mix of GLVND and non 
GLVND GL and EGL libraries.

  [Test Case]
  1) Enable the -proposed repository, install the new nvidia-384 package, and 
reboot.

  2) Install the utilities to check that the correct libraries can be
  found:

  sudo apt install vulkan-utils mesa-utils-extra

  3) Run and attach the output of the following commands (which should
  execute with no errors):

  vulkaninfo

  es2_info

  [Regression Potential]
  Low, as the libraries are the same that are installed by the upstream NVIDIA 
installer when the non-GLVND parameter is used.

  
  The Vulkan nvidia_icd.json included with the nvidia-384 package has the wrong 
"library_path" set, meaning that no Vulkan apps can run. For example, running 
"vulkaninfo" gives the following:

  ERROR: [loader] Code 0 : loader_scanned_icd_add: Attempt to retrieve either 
'vkGetInstanceProcAddr' or 'vk_icdGetInstanceProcAddr' from ICD libGL.so.1 
failed.
  Cannot create Vulkan instance.
  /build/vulkan-8TJjRa/vulkan-1.0.61.1+dfsg1/demos/vulkaninfo.c:698: failed 
with VK_ERROR_INCOMPATIBLE_DRIVER

  Furthermore, none of our (Feral Interactive) Vulkan games are able to
  run when this driver package is installed.

  The library path is set to "libGL.so.1", however since this package
  includes the GLVND version of the NVIDIA driver, that library is not a
  valid Vulkan ICD (it is the GLVND dispatch library). The correct ICD
  library path when using GLVND is "libGLX_nvidia.so.0" (this is what
  you get when you install the driver manually with NVIDIA's installer).

  This is seen with nvidia-384_384.90-0ubuntu0.17.04.1_amd64.

  The nvidia-384 package from the graphics-drivers PPA (version
  384.90-0ubuntu0~gpu17.04.1) does not have this problem. However, as of
  today, the version from the main repository seems to be getting
  installed as an update in preference to the PPA version, which causes
  breakage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1726809/+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 1726809] Re: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.90-0ubuntu3.17.10.1

---
nvidia-graphics-drivers-384 (384.90-0ubuntu3.17.10.1) artful-proposed; 
urgency=medium

  * debian/rules,
debian/templates/nvidia-graphics-drivers.links.in,
debian/templates/nvidia-graphics-drivers.links32.in:
- Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone   Mon, 30 Oct 2017
16:01:58 +0100

** Changed in: nvidia-graphics-drivers-384 (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/1726809

Title:
  Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

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

Bug description:
  SRU Request:

  [Impact]
  Vulkan support is broken because the packages ship a mix of GLVND and non 
GLVND GL and EGL libraries.

  [Test Case]
  1) Enable the -proposed repository, install the new nvidia-384 package, and 
reboot.

  2) Install the utilities to check that the correct libraries can be
  found:

  sudo apt install vulkan-utils mesa-utils-extra

  3) Run and attach the output of the following commands (which should
  execute with no errors):

  vulkaninfo

  es2_info

  [Regression Potential]
  Low, as the libraries are the same that are installed by the upstream NVIDIA 
installer when the non-GLVND parameter is used.

  
  The Vulkan nvidia_icd.json included with the nvidia-384 package has the wrong 
"library_path" set, meaning that no Vulkan apps can run. For example, running 
"vulkaninfo" gives the following:

  ERROR: [loader] Code 0 : loader_scanned_icd_add: Attempt to retrieve either 
'vkGetInstanceProcAddr' or 'vk_icdGetInstanceProcAddr' from ICD libGL.so.1 
failed.
  Cannot create Vulkan instance.
  /build/vulkan-8TJjRa/vulkan-1.0.61.1+dfsg1/demos/vulkaninfo.c:698: failed 
with VK_ERROR_INCOMPATIBLE_DRIVER

  Furthermore, none of our (Feral Interactive) Vulkan games are able to
  run when this driver package is installed.

  The library path is set to "libGL.so.1", however since this package
  includes the GLVND version of the NVIDIA driver, that library is not a
  valid Vulkan ICD (it is the GLVND dispatch library). The correct ICD
  library path when using GLVND is "libGLX_nvidia.so.0" (this is what
  you get when you install the driver manually with NVIDIA's installer).

  This is seen with nvidia-384_384.90-0ubuntu0.17.04.1_amd64.

  The nvidia-384 package from the graphics-drivers PPA (version
  384.90-0ubuntu0~gpu17.04.1) does not have this problem. However, as of
  today, the version from the main repository seems to be getting
  installed as an update in preference to the PPA version, which causes
  breakage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1726809/+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 1712921] Re: enabling networkd appears to eat up entropy

[Mathieu Trudel-Lapierre]

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

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

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

** Also affects: openssh (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

** Also affects: systemd (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

** Also affects: nplan (Ubuntu Bionic)
   Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: In Progress

** Also affects: openssh (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: nplan (Ubuntu Zesty)
   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/1712921

Title:
  enabling networkd appears to eat up entropy

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

Bug description:
  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+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 1703798] Re: [SRU] 2.27.6

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.28.5

---
snapd (2.28.5) xenial; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: cleanup broken nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- overlord/ifacestate: refresh udev backend on startup
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- snap-confine: add support for handling /dev/nvidia-modeset
- interfaces/network-control: remove incorrect rules for tun

snapd (2.28.4) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces/opengl: don't udev tag nvidia devices and use snap-
  confine instead
- debian: fix replaces/breaks for snap-xdg-open (thanks to apw!)

snapd (2.28.3) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces/lxd: lxd slot implementation can also be an app
  snap

snapd (2.28.2) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces: fix udev rules for tun
- release,cmd,dirs: Redo the distro checks to take into account
  distribution families

snapd (2.28.1) xenial; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: update apparmor rules for fedora based basesnaps
- snapstate: rename refresh hook to post-refresh for consistency

snapd (2.28) xenial; urgency=medium

  * New upstream release, LP: #1714984
- hooks: rename refresh to after-refresh
- snap-confine: bind mount /usr/lib/snapd relative to snap-confine
- cmd,dirs: treat "liri" the same way as "arch"
- snap-confine: fix base snaps on core
- hooks: substitute env vars when executing hooks
- interfaces: updates for default, browser-support, desktop, opengl,
  upower and stub-resolv.conf
- cmd,dirs: treat manjaro the same as arch
- systemd: do not run auto-import and repair services on classic
- packaging/fedora: Ensure vendor/ is empty for builds and fix spec
  to build current master
- many: fix TestSetConfNumber missing an Unlock and other fragility
  improvements
- osutil: adjust StreamCommand tests for golang 1.9
- daemon: allow polkit authorisation to install/remove snaps
- tests: make TestCmdWatch more robust
- debian: improve package description
- interfaces: add netlink kobject uevent to hardware observe
- debian: update trusted account-keys check on 14.04 packaging
- interfaces/network-{control,observe}: allow receiving
  kobject_uevent() messages
- tests: fix lxd test for external backend
- snap-confine,snap-update-ns: add -no-pie to fix FTBFS on
  go1.7,ppc64
- corecfg: mock "systemctl" in all corecfg tests
- tests: fix unit tests on Ubuntu 14.04
- debian: add missing flags when building static snap-exec
- many: end-to-end support for the bare base snap
- overlord/snapstate: SetRootDir from SetUpTest, not in just some
  tests
- store: have an ad-hoc method on cfg to get its list of uris for
  tests
- daemon: let client decide whether to allow interactive auth via
  polkit
- client,daemon,snap,store: add license field
- overlord/snapstate: rename HasCurrent to IsInstalled, remove
  superfluous/misleading check from All
- cmd/snap: SetRootDir from SetUpTest, not in just some individual
  tests.
- systemd: rename snap-repair.{service,timer} to snapd.snap-
  repair.{service,timer}
- snap-seccomp: remove use of x/net/bpf from tests
- httputil: more naive per go version way to recreate a default
  transport for tls reconfig
- cmd/snap-seccomp/main_test.go: add one more syscall for arm64
- interfaces/opengl: use == to compare, not =
- cmd/snap-seccomp/main_test.go: add syscalls for armhf and arm64
- cmd/snap-repair: track and use a lower bound for the time for
  TLS checks
- interfaces: expose bluez interface on classic OS
- snap-seccomp: add in-kernel bpf tests
- overlord: always try to get a serial, lazily on classic
- tests: add nmcli regression test
- tests: deal with __PNR_chown on aarch64 to fix FTBFS on arm64
- tests: add autopilot-introspection interface test
- vendor: fix artifact from manually editing vendor/vendor.json
- tests: rename complexion to test-snapd-complexion
- interfaces: add desktop and desktop-legacy
  interfaces/desktop: add new 'desktop' interface for modern DEs
  interfaces/builtin/desktop_test.go: use modern testing techniques
  interfaces/wayland: allow read on /etc/drirc for Plasma desktop
  interfaces/desktop-legacy: add new 'legacy' interface (currently
  for a11y and input)
- tests: fix race in snap userd test
- devices/iio: add read/write for missing sysfs entries
- spread: don't set HTTPS?_PROXY for linode
- cmd/snap-repair: check signatures of repairs from Next
- env: set XDG_DATA_DIRS for wayland et.al.
- interfaces/{default,account-control}: 

[Group.of.nepali.translators] [Bug 1703798] Re: [SRU] 2.27.6

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.28.5+17.04

---
snapd (2.28.5+17.04) zesty; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: cleanup broken nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- overlord/ifacestate: refresh udev backend on startup
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- snap-confine: add support for handling /dev/nvidia-modeset
- interfaces/network-control: remove incorrect rules for tun

 -- Michael Vogt   Fri, 13 Oct 2017 23:25:46
+0200

** Changed in: snapd (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: snapd (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/1703798

Title:
  [SRU] 2.27.6

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Trusty:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in snapd source package in Zesty:
  Fix Released
Status in snapd source package in Artful:
  Fix Released

Bug description:
  This is a new version of snapd.

  The changelog for 2.27.5 is available here
  
https://github.com/snapcore/snapd/blob/2.27.5/packaging/ubuntu-16.04/changelog,
  the raw git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.27.5 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new 2.27.5 release that we want SRU into
  xenial. The new process described in
  https://wiki.ubuntu.com/SnapdUpdates was used and we have done
  integration-tests on the snappy images, autopkgtests on classic and
  unit tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1703798/+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 1714984] Re: [SRU] 2.28

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.28.5+17.04

---
snapd (2.28.5+17.04) zesty; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: cleanup broken nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- overlord/ifacestate: refresh udev backend on startup
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- snap-confine: add support for handling /dev/nvidia-modeset
- interfaces/network-control: remove incorrect rules for tun

 -- Michael Vogt   Fri, 13 Oct 2017 23:25:46
+0200

** Changed in: snapd (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: snapd (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/1714984

Title:
  [SRU] 2.28

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Trusty:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in snapd source package in Zesty:
  Fix Released
Status in snapd source package in Artful:
  Fix Released

Bug description:
  This is a new version of snapd.

  The changelog for 2.28.1 is available here
  
https://github.com/snapcore/snapd/blob/2.28.1/packaging/ubuntu-16.04/changelog,
  the raw git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.28.1 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new 2.28.1 release that we want SRU into
  xenial. The new process described in
  https://wiki.ubuntu.com/SnapdUpdates was used and we have done
  integration-tests on the snappy images, autopkgtests on classic and
  unit tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1714984/+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 1714984] Re: [SRU] 2.28

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.28.5

---
snapd (2.28.5) xenial; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: cleanup broken nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- overlord/ifacestate: refresh udev backend on startup
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- snap-confine: add support for handling /dev/nvidia-modeset
- interfaces/network-control: remove incorrect rules for tun

snapd (2.28.4) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces/opengl: don't udev tag nvidia devices and use snap-
  confine instead
- debian: fix replaces/breaks for snap-xdg-open (thanks to apw!)

snapd (2.28.3) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces/lxd: lxd slot implementation can also be an app
  snap

snapd (2.28.2) xenial; urgency=medium

  * New upstream release, LP: #1714984
- interfaces: fix udev rules for tun
- release,cmd,dirs: Redo the distro checks to take into account
  distribution families

snapd (2.28.1) xenial; urgency=medium

  * New upstream release, LP: #1714984
- snap-confine: update apparmor rules for fedora based basesnaps
- snapstate: rename refresh hook to post-refresh for consistency

snapd (2.28) xenial; urgency=medium

  * New upstream release, LP: #1714984
- hooks: rename refresh to after-refresh
- snap-confine: bind mount /usr/lib/snapd relative to snap-confine
- cmd,dirs: treat "liri" the same way as "arch"
- snap-confine: fix base snaps on core
- hooks: substitute env vars when executing hooks
- interfaces: updates for default, browser-support, desktop, opengl,
  upower and stub-resolv.conf
- cmd,dirs: treat manjaro the same as arch
- systemd: do not run auto-import and repair services on classic
- packaging/fedora: Ensure vendor/ is empty for builds and fix spec
  to build current master
- many: fix TestSetConfNumber missing an Unlock and other fragility
  improvements
- osutil: adjust StreamCommand tests for golang 1.9
- daemon: allow polkit authorisation to install/remove snaps
- tests: make TestCmdWatch more robust
- debian: improve package description
- interfaces: add netlink kobject uevent to hardware observe
- debian: update trusted account-keys check on 14.04 packaging
- interfaces/network-{control,observe}: allow receiving
  kobject_uevent() messages
- tests: fix lxd test for external backend
- snap-confine,snap-update-ns: add -no-pie to fix FTBFS on
  go1.7,ppc64
- corecfg: mock "systemctl" in all corecfg tests
- tests: fix unit tests on Ubuntu 14.04
- debian: add missing flags when building static snap-exec
- many: end-to-end support for the bare base snap
- overlord/snapstate: SetRootDir from SetUpTest, not in just some
  tests
- store: have an ad-hoc method on cfg to get its list of uris for
  tests
- daemon: let client decide whether to allow interactive auth via
  polkit
- client,daemon,snap,store: add license field
- overlord/snapstate: rename HasCurrent to IsInstalled, remove
  superfluous/misleading check from All
- cmd/snap: SetRootDir from SetUpTest, not in just some individual
  tests.
- systemd: rename snap-repair.{service,timer} to snapd.snap-
  repair.{service,timer}
- snap-seccomp: remove use of x/net/bpf from tests
- httputil: more naive per go version way to recreate a default
  transport for tls reconfig
- cmd/snap-seccomp/main_test.go: add one more syscall for arm64
- interfaces/opengl: use == to compare, not =
- cmd/snap-seccomp/main_test.go: add syscalls for armhf and arm64
- cmd/snap-repair: track and use a lower bound for the time for
  TLS checks
- interfaces: expose bluez interface on classic OS
- snap-seccomp: add in-kernel bpf tests
- overlord: always try to get a serial, lazily on classic
- tests: add nmcli regression test
- tests: deal with __PNR_chown on aarch64 to fix FTBFS on arm64
- tests: add autopilot-introspection interface test
- vendor: fix artifact from manually editing vendor/vendor.json
- tests: rename complexion to test-snapd-complexion
- interfaces: add desktop and desktop-legacy
  interfaces/desktop: add new 'desktop' interface for modern DEs
  interfaces/builtin/desktop_test.go: use modern testing techniques
  interfaces/wayland: allow read on /etc/drirc for Plasma desktop
  interfaces/desktop-legacy: add new 'legacy' interface (currently
  for a11y and input)
- tests: fix race in snap userd test
- devices/iio: add read/write for missing sysfs entries
- spread: don't set HTTPS?_PROXY for linode
- cmd/snap-repair: check signatures of repairs from Next
- env: set XDG_DATA_DIRS for wayland et.al.
- interfaces/{default,account-control}: 

[Group.of.nepali.translators] [Bug 1684295] Re: sssd fails with 'Exiting the SSSD. Could not restart critical service [tpad].

[ChristianEhrhardt]

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

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

** Changed in: sssd (Ubuntu Xenial)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: sssd (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  sssd fails with 'Exiting the SSSD.  Could not restart critical service
  [tpad].

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Xenial:
  In Progress

Bug description:
  [Impact]
  In this particular configuration, when ldap_rfc2307_fallback_to_local_users 
is set to true in /etc/sss/sssd.conf and a local user is a member of an ldap 
group and does not exist in the directory (other scenarios are possible), the 
sssd_be process segfaults and logins might be prevented.

  The original scenario is a bit more complex and involves setting up an
  Active Directory server, but with the help from the bug reporter
  (thanks @pam-s!) we managed to narrow it down to this simple test
  case.

  [Test Case]

  # Install the packages. When prompted, choose any password for the ldap admin
  $ sudo apt update; sudo apt install sssd slapd

  # create the sssd config
  $ sudo tee /etc/sssd/sssd.conf 

[Group.of.nepali.translators] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Timo Aaltonen]

** Bug watch added: freedesktop.org Bugzilla #101691
   https://bugs.freedesktop.org/show_bug.cgi?id=101691

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=101691
   Importance: Unknown
   Status: Unknown

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

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 1719671] Re: [SRU] include recent version containing fips and livepatch

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-advantage-tools -
10ubuntu0.16.04.1

---
ubuntu-advantage-tools (10ubuntu0.16.04.1) xenial; urgency=medium

  * Backport version 10 to xenial.
  * Backports from upstream version 13 (LP: #1719671):
- support older python3 versions in the test suite
- d/control, d/rules: run tests at package build time
- default FIPS tests to the x86_64 architecture
- add FIPS test for unsupported architecture

 -- Andreas Hasenack   Sun, 05 Nov 2017 18:37:47
-0200

** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
   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/1719671

Title:
  [SRU] include recent version containing fips and livepatch

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released

Bug description:
  This bug has some history that may be confusing from the comments.
  Basically it started out as a Feature Freeze Exception, that's why we
  had build logs, git logs and unit test runs attached.

  Also, the "rename" that is mentioned elsewhere did not happen with
  this package: the ubuntu-advantage name was kept, no new aliases were
  added. This will happen in a later SRU, with a later version of the
  package.

  PPA with test packages:
  https://launchpad.net/~ahasenack/+archive/ubuntu/ua-
  tools-1719671-take1

  [IMPACT]
  Most recent version of ubuntu-advantage-tool on github includes fips and 
livepatch enablement. The fips enablement will allow customers to easily 
install and configure Canonical's FIPS certified modules on xenial, whereas 
livepatch allows xenial and trusty customers to patch the running kernel 
without a reboot.

  This SRU will cover both new features.

  In addition to the new features themselves, a new "status" command was
  added that will give a short summary about the available modules and
  their status, at a glance.

  Note: FIPS certified modules are only available for xenial. Livepatch
  is supported on xenial and trusty. The tool will refuse to enable
  either service on an unsupported ubuntu release.

  Without this updated package, customers of those services have to
  enable them manually by following a series of steps.

  [FIPS DESCRIPTION]
  When "ubuntu-advantage enable-fips " is issued from commandline,

   - configure the private PPA where the FIPS modules are located
   - install the FIPS modules from this PPA to the local machine from where the 
script is run
   - configure the bootloader to enable fips

  Upon successful completion of these steps, the customer then gets a message 
stating to reboot
  the machine to complete the fips enablement process.

  Without the script, customers must perform the steps manually.

  [LIVEPATCH DESCRIPTION]
  Livepatch allows customers to apply kernel patches to a running system 
without rebooting it.

  The current instructions live in http://ubuntu.com/livepatch and boil down to:
  - install snapd if it's not installed already. On trusty this means a new 
kernel as well.
  - install the canonical-livepatch snap
  - obtain a livepatch token from Canonical
  - run the enable command with the given token

  The ubuntu-advantage-tools package simplifies this process by just
  requesting the token and performing all the other steps on behalf of
  the user. It also conveniently checks the running kernel and instructs
  the user to reboot into a newer kernel if needed to finish the
  installation (this is the case when running trusty).

  [FIX]

  Add fips and livepatch support to the ubuntu-adadvantage-tools
  package. See debdiff below.

  [LIVEPATCH TESTCASES]

  TRUSTY
  0. Install the new ubuntu-advantage-tools package to add livepatch support.

  1. Collect status before enabling livepatch

  type on commandline:
  ubuntu-advantage status

  expect:
  livepatch: disabled

  esm: disabled (not available)

  fips: disabled (not available)

  2. Enable livepatch

  visit https://ubuntu.com/livepatch and obtain a token

  type on commandline,
  sudo ubuntu-advantage enable-livepatch 

  You may be required to install a newer kernel. In that case, expect the
  following output:
   Installing missing dependency snapd... OK
   Installing the canonical-livepatch snap.
   This may take a few minutes depending on your bandwidth.
   canonical-livepatch 7.24 from 'canonical' installed

   Your currently running kernel (3.13.0-133-generic) is too old to
   support snaps. Version 4.4.0 or higher is needed.

   Please reboot your system into 

[Group.of.nepali.translators] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

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

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

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

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 1719671] Re: [SRU] include recent version containing fips and livepatch

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-advantage-tools -
10ubuntu0.17.10.1

---
ubuntu-advantage-tools (10ubuntu0.17.10.1) artful; urgency=medium

  * Backports from upstream version 13 (LP: #1719671):
- support older python3 versions in the test suite
- d/control, d/rules: run tests at package build time
- default FIPS tests to the x86_64 architecture
- add FIPS test for unsupported architecture

 -- Andreas Hasenack   Sun, 05 Nov 2017 18:45:21
-0200

** Changed in: ubuntu-advantage-tools (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/1719671

Title:
  [SRU] include recent version containing fips and livepatch

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released

Bug description:
  This bug has some history that may be confusing from the comments.
  Basically it started out as a Feature Freeze Exception, that's why we
  had build logs, git logs and unit test runs attached.

  Also, the "rename" that is mentioned elsewhere did not happen with
  this package: the ubuntu-advantage name was kept, no new aliases were
  added. This will happen in a later SRU, with a later version of the
  package.

  PPA with test packages:
  https://launchpad.net/~ahasenack/+archive/ubuntu/ua-
  tools-1719671-take1

  [IMPACT]
  Most recent version of ubuntu-advantage-tool on github includes fips and 
livepatch enablement. The fips enablement will allow customers to easily 
install and configure Canonical's FIPS certified modules on xenial, whereas 
livepatch allows xenial and trusty customers to patch the running kernel 
without a reboot.

  This SRU will cover both new features.

  In addition to the new features themselves, a new "status" command was
  added that will give a short summary about the available modules and
  their status, at a glance.

  Note: FIPS certified modules are only available for xenial. Livepatch
  is supported on xenial and trusty. The tool will refuse to enable
  either service on an unsupported ubuntu release.

  Without this updated package, customers of those services have to
  enable them manually by following a series of steps.

  [FIPS DESCRIPTION]
  When "ubuntu-advantage enable-fips " is issued from commandline,

   - configure the private PPA where the FIPS modules are located
   - install the FIPS modules from this PPA to the local machine from where the 
script is run
   - configure the bootloader to enable fips

  Upon successful completion of these steps, the customer then gets a message 
stating to reboot
  the machine to complete the fips enablement process.

  Without the script, customers must perform the steps manually.

  [LIVEPATCH DESCRIPTION]
  Livepatch allows customers to apply kernel patches to a running system 
without rebooting it.

  The current instructions live in http://ubuntu.com/livepatch and boil down to:
  - install snapd if it's not installed already. On trusty this means a new 
kernel as well.
  - install the canonical-livepatch snap
  - obtain a livepatch token from Canonical
  - run the enable command with the given token

  The ubuntu-advantage-tools package simplifies this process by just
  requesting the token and performing all the other steps on behalf of
  the user. It also conveniently checks the running kernel and instructs
  the user to reboot into a newer kernel if needed to finish the
  installation (this is the case when running trusty).

  [FIX]

  Add fips and livepatch support to the ubuntu-adadvantage-tools
  package. See debdiff below.

  [LIVEPATCH TESTCASES]

  TRUSTY
  0. Install the new ubuntu-advantage-tools package to add livepatch support.

  1. Collect status before enabling livepatch

  type on commandline:
  ubuntu-advantage status

  expect:
  livepatch: disabled

  esm: disabled (not available)

  fips: disabled (not available)

  2. Enable livepatch

  visit https://ubuntu.com/livepatch and obtain a token

  type on commandline,
  sudo ubuntu-advantage enable-livepatch 

  You may be required to install a newer kernel. In that case, expect the
  following output:
   Installing missing dependency snapd... OK
   Installing the canonical-livepatch snap.
   This may take a few minutes depending on your bandwidth.
   canonical-livepatch 7.24 from 'canonical' installed

   Your currently running kernel (3.13.0-133-generic) is too old to
   support snaps. Version 4.4.0 or higher is needed.

   Please reboot your system into a supported kernel version
   and 

[Group.of.nepali.translators] [Bug 1724867] Re: langford 0.0.20130228-5 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Chris J Arges]

Hello Seth, or anyone else affected,

Accepted langford into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/langford/0.0.20130228-5ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: langford (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

Title:
  langford 0.0.20130228-5 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in langford package in Ubuntu:
  Fix Released
Status in langford source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/langford/20171018_120558_d9a48@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/langford/20171018_121613_d9a48@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/langford/20171018_121338_d9a48@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/langford/20171018_120515_d9a48@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langford/+bug/1724867/+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 1510570] Re: Bluetooth LE pairing fail

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+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 1565060] Re: defaults file is ignored

[Chris J Arges]

Hello ben, or anyone else affected,

Accepted bind9 into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-10.1ubuntu5.3
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

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

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

** Tags added: verification-needed verification-needed-zesty

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

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

Title:
  defaults file is ignored

Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  Fix Committed
Status in bind9 source package in Yakkety:
  Won't Fix
Status in bind9 source package in Zesty:
  Fix Committed
Status in bind9 package in Debian:
  Fix Committed

Bug description:
  [Impact]

  Server start up options set in /etc/default/bind9 via the OPTIONS
  variable are ignored.

  The fix is to have the systemd service file source that file and use
  the given OPTIONS value. This is already being done in Ubuntu Artful
  and higher. The fix here is the same.

  [Test Case]

  # install bind9
  $ sudo apt install bind9

  # start it up
  $ sudo service bind9 start

  # inspect the command line of the process:
  $ ps fxaw|grep named|grep -v grep
396 ?Ssl0:00 /usr/sbin/named -f -u bind

  # edit /etc/default/bind9 and include "-4" to the OPTIONS value so it looks 
like this:
  # startup options for the server
  OPTIONS="-4 -u bind"

  # restart bind9
  sudo service bind9 restart

  # inspect the process command line again. Only the fixed version of the 
package will include the newly added "-4" parameter:
  $ ps fxaw|grep named|grep -v grep
  17891 ?Ssl0:00 /usr/sbin/named -f -4 -u bind

  
  [Regression Potential] 
  Administrators who have for some reason altered the defaults file with an 
incorrect value for OPTIONS might be surprised after this update, since now 
that file is actually parsed and if it's indeed incorrect, the service may fail 
to start.

  [Other Info]
  None at this time.

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