[Group.of.nepali.translators] [Bug 1663891] Re: Security uploads for cacti (trusty and xenial)

[Mathew Hodson]

** Information type changed from Public to Public Security

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

** Changed in: cacti (Ubuntu Trusty)
   Importance: Undecided => High

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

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

** Tags removed: security

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

Title:
  Security uploads for cacti (trusty and xenial)

Status in cacti package in Ubuntu:
  Fix Released
Status in cacti source package in Trusty:
  New
Status in cacti source package in Xenial:
  New

Bug description:
  Since the last uploads in security upload in Trusty and the last
  upload in Xenial, multiple CVE's have been reported against cacti.

  Please upload the attached debdiff's to fix all open issues in Trusty
  and Xenial. Because the state in Debian's LTS Wheezy is similar to
  Trusty, I applied all the changes since the last common change-set.
  For Xenial, I based the changes on Jessie's stable uploads.

  To be perfectly clear, I did verify that all the patches apply cleanly
  (and build cleanly on debomatic, although that doesn't say much for a
  php package), but I haven't verified functionality as I could bring
  myself to do that for Ubuntu (I already did that too often for the
  Debian packages). But because this all is php and the patches are
  already exposed in Debian for an extremely long time, I don't see much
  risk (please judge yourself though).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1663891/+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 1660506] Re: SRU of LXD 2.0.9 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxd - 2.0.9-0ubuntu1~16.04.1

---
lxd (2.0.9-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.9) (LP: #1660506)
- Exec sessions being killed by a signal will now report the signal
  number as part of their exit code.
- VLAN device types are now properly reported in the API and client.
- The client will now show the date an image was last used at.
- The client will now let you delete multiple images at once.
- LXD is now using Weblate for its translations.

- client: Add a done signal to Monitor API
- client: Better handle http errors
- client: Commonize update methods
- doc: Add Documentation on Network Configuration via cloud-init
- doc: Added reference to godoc to README.md
- doc: Update README.md for CI and Weblate status
- extra/lxc-to-lxd: Add more unsupported config keys
- extra/lxc-to-lxd: All properties must be strings
- extra/lxc-to-lxd: Copy the rootfs by default, don't move it
- extra/lxc-to-lxd: Show nicer error on missing python3-lxc
- extra/lxc-to-lxd: Switch to using a config whitelist
- global: Fix typos
- global: "gofmt -s" run
- lxc: Better handle timestamps
- lxc: Make help messages more consistent
- lxc: Properly check yaml errors
- lxc/init: Fix example
- lxc/init: Properly replace args list
- lxc/launch: Just use init.go's flags()
- lxc/list: Sort IPv4 and IPv6 addresses
- lxc/remote: Update help
- lxd-bridge: Add ip6tables filter rules
- lxd-bridge: DHCP happens over UDP only
- lxd-bridge: Make IPv4 firewalling optional (default is enabled)
- lxd/containers: Add basic logging to container creation
- lxd/containers: Allow passing in-memory buffers to a FileResponse
- lxd/containers: Also call setgroups when attaching to the container
- lxd/containers: Avoid race condition in network fill function
- lxd/containers: Blacklist lxc.syslog and lxc.ephemeral in raw.lxc
- lxd/containers: Detect background tasks to allow clean exit
- lxd/containers: Do mounts in the right order
- lxd/containers: Don't attempt to read xattrs from symlinks
- lxd/containers: Don't block resolution on non-existing paths
- lxd/containers: Don't record last_state.power twice
- lxd/containers: Exec() return attached PID && take bool arg
- lxd/containers: Fix container state recording
- lxd/containers: Fix device hotplug with major/minor set
- lxd/containers: Fix file push error handling
- lxd/containers: Fix generated seccomp profile
- lxd/containers: Fix logging for file_manip commands
- lxd/containers: Improve error handling and reporting during export
- lxd/containers: Return a clear error when replacing a directory
- lxd/daemon: Common codepath for http client
- lxd/daemon: Don't set InsecureSkipVerify on daemon's tls config
- lxd/daemon: Log daemon version
- lxd/daemon: Make directories with stricter permissions
- lxd/daemon: Make LXD_DIR with +x for group and everyone
- lxd/daemon: Only mark ready once containers are up
- lxd/daemon: Properly validate daemon keys on unset
- lxd/daemon: Use our custom http server when updating HTTPS address too
- lxd/db: Drop unused code from db.go
- lxd/images: Close race condition in image download
- lxd/images: Track speed during network transfers
- lxd/main: Move activateifneeded to own file
- lxd/main: Move callhook to own file
- lxd/main: Move daemon to own file
- lxd/main: Move forkexec to own file
- lxd/main: Move forkgetnet to own file
- lxd/main: Move forkmigrate to own file
- lxd/main: Move forkstart to own file
- lxd/main: Move init to own file
- lxd/main: Move migratedumpsuccess to own file
- lxd/main: Move netcat to own file
- lxd/main: Move ready to own file
- lxd/main: Move shutdown to own file
- lxd/main: Move waitready to own file
- lxd/main: Rename nsexec.go to main_nsexec.go
- lxd/migrate: Use the generated snapshot list
- lxd/patches: Mark all patches as applied on create
- lxd/profiles: Fix unusued variable
- lxd/storage: btrfs: Don't assume a path is a subvolume
- lxd/storage: Change ContainerStart to take the name and path to start
- lxd/storage: Rework EEXISTS detection on create
- lxd/storage: zfs: Simplify device tracking logic
- Makefile: Rework "make dist" to be more reliable
- shared: add GetPollRevents()
- shared: Add WebsocketExecMirror()
- shared: Centralize all cert fingerprint generation
- shared: Convert TransferProgress to ReadCloser
- shared: ExecReaderToChannel() use sync.Once
- shared: Give Architecture handling its own package
- shared: Give IO progress tracker its own package
- shared: Give simplestreams client its own package
- shared: Give version handling its own package
- shared: Implement write 

[Group.of.nepali.translators] [Bug 1660844] Re: SRU of LXC 2.0.7 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.7-0ubuntu1~16.04.1

---
lxc (2.0.7-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.7) (LP: #1660844)
- attach: Close lsm label file descriptor
- attach: Non-functional changes
- attach: Simplify lsm_openat()
- caps: Add lxc_cap_is_set()
- conf: attach: Save errno across call to close
- conf: Clearly report to either use drop or keep
- conf: criu: Add make_anonymous_mount_file()
- conf: Fix suggest_default_idmap()
- configure: Add --enable-gnutls option
- configure: Check for memfd_create()
- configure: Check whether gettid() is declared
- configure: Do not allow variable length arrays
- configure: Remove -Werror=vla
- configure: Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
- conf: Non-functional changes
- conf: Remove thread-unsafe strsignal + improve log
- init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
- log: Add lxc_unix_epoch_to_utc()
- log: Annotate lxc_unix_epoch_to_utc()
- log: Drop all timezone conversion functions
- log: Make sure that date is correctly formatted
- log: Use lxc_unix_epoch_to_utc()
- log: Use N/A if getpid() != gettid() when threaded
- log: Use thread-safe localtime_r()
- lvm: Suppress warnings about leaked files
- lxccontainer: Log failure to send sig to init pid
- monitor: Add more logging
- monitor: Close mainloop on exit if we opened it
- monitor: Improve log + set log level to DEBUG
- monitor: Log which pipe fd is currently used
- monitor: Make lxc-monitord async signal safe
- monitor: Non-functional changes
- python3-lxc: Fix api_test.py on s390x
- start: Check for CAP_SETGID before setgroups()
- start: Fix execute and improve setgroups() calls
- state: Use async signal safe fun in lxc_wait()
- templates: lxc-debian: Don't read from /usr/lib/systemd on the host
- templates: lxc-debian: Fix getty service startup
- templates: lxc-debian: Fix typo with dpkg --print-foreign-architectures
- templates: lxc-debian: Handle ppc hostarch -> powerpc
- templates: lxc-opensuse: Change openSUSE default release to Leap 42.2
- templates: lxc-opensuse: Remove libgcc_s1
- templates: lxc-opensuse: Remove poweroff.target -> sigpwr.target copy
- templates: lxc-opensuse: Set to be unconfined by AppArmor
- templates: lxc-opensuse: Update for Leap 42.2
- tests; Don't cause test failures on cleanup errors
- tests: Skip unpriv tests on broken overlay module
- tools: Improve logging
- tools: lxc-start: Remove c->is_defined(c) check
- tools: lxc-start: Set configfile after load_config
- tools: Only check for O_RDONLY
- tree-wide: Random macro cleanups
- tree-wide: Remove any variable length arrays
- tree-wide: Sic semper assertis!
- utils: Add macro __LXC_NUMSTRLEN
- utils: Add uid, gid, group convenience wrappers

  * Cherry-pick upstream bugfix:
- 0002-Make-lxc-start-ephemeral-Python-3.2-compatible.patch

  * Resolve lintian warnings
- Drop un-needed overrides
- Fix typos in debian/control

 -- Stéphane Graber   Tue, 31 Jan 2017 18:37:52
-0500

** Changed in: lxc (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/1660844

Title:
  SRU of LXC 2.0.7 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.7 as a bugfix release with following changelog:
   - attach: Close lsm label file descriptor
   - attach: Non-functional changes
   - attach: Simplify lsm_openat()
   - caps: Add lxc_cap_is_set()
   - conf: attach: Save errno across call to close
   - conf: Clearly report to either use drop or keep
   - conf: criu: Add make_anonymous_mount_file()
   - conf: Fix suggest_default_idmap()
   - configure: Add --enable-gnutls option
   - configure: Check for memfd_create()
   - configure: Check whether gettid() is declared
   - configure: Do not allow variable length arrays
   - configure: Remove -Werror=vla
   - configure: Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
   - conf: Non-functional changes
   - conf: Remove thread-unsafe strsignal + improve log
   - init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
   - log: Add lxc_unix_epoch_to_utc()
   - log: Annotate lxc_unix_epoch_to_utc()
   - log: Drop all timezone conversion functions
   - log: Make sure that date is correctly formatted
   - log: Use lxc_unix_epoch_to_utc()
   - log: Use N/A if getpid() != gettid() when 

[Group.of.nepali.translators] [Bug 1660850] Re: SRU of LXCFS 2.0.6 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxcfs - 2.0.6-0ubuntu1~16.04.1

---
lxcfs (2.0.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1660850):
- Fix swap values with nested cgroups
- tests: Fix run on ppc64el
- Fix wrong scanning of memory.stat

  * Sync packaging with Zesty/Debian.

 -- Stéphane Graber   Tue, 31 Jan 2017 18:47:20
-0500

** Changed in: lxcfs (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/1660850

Title:
  SRU of LXCFS 2.0.6 (upstream bugfix release)

Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxcfs source package in Trusty:
  Triaged
Status in lxcfs source package in Xenial:
  Fix Released
Status in lxcfs source package in Yakkety:
  Fix Released

Bug description:
  LXCFS upstream released LXCFS 2.0.6 as a bugfix release with following 
changelog:
   - Fix swap values with nested cgroups
   - tests: Fix run on ppc64el
   - Fix wrong scanning of memory.stat

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Zesty and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1660850/+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 1660850] Re: SRU of LXCFS 2.0.6 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxcfs - 2.0.6-0ubuntu1~16.10.1

---
lxcfs (2.0.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1660850):
- Fix swap values with nested cgroups
- tests: Fix run on ppc64el
- Fix wrong scanning of memory.stat

  * Sync packaging with Zesty/Debian.

 -- Stéphane Graber   Tue, 31 Jan 2017 18:50:16
-0500

** Changed in: lxcfs (Ubuntu Yakkety)
   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/1660850

Title:
  SRU of LXCFS 2.0.6 (upstream bugfix release)

Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxcfs source package in Trusty:
  Triaged
Status in lxcfs source package in Xenial:
  Fix Released
Status in lxcfs source package in Yakkety:
  Fix Released

Bug description:
  LXCFS upstream released LXCFS 2.0.6 as a bugfix release with following 
changelog:
   - Fix swap values with nested cgroups
   - tests: Fix run on ppc64el
   - Fix wrong scanning of memory.stat

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Zesty and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1660850/+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 1664107] Re: cacti-0.8.8f not compatible with rrdtool-1.5.5 in 16.04

[Paul Gevers]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. I added a specific Xenial line for this bug and I am
closing the general bug because the bug has been fixed in the latest
development version of Ubuntu.

This is may be a significant bug in Ubuntu. If you need a fix for the
bug in previous versions of Ubuntu, please perform as much as possible
of the SRU Procedure [1] to bring the need to a developer's attention.

If I remember correctly, the fix is trivial, just add a one or two-liner
to support recognition of 1.5, no further code change required. I am
even wondering if apart from the configure screen, this is an issue at
all. Could you please show how "cacti do not work with rrdtool"?

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

** Changed in: cacti (Ubuntu)
   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/1664107

Title:
  cacti-0.8.8f not compatible with rrdtool-1.5.5 in 16.04

Status in cacti package in Ubuntu:
  Fix Released
Status in cacti source package in Xenial:
  New

Bug description:
  Cacti-0.8.8f do not work with rrdtool-1.5.5 in ubuntu 16.04. Need to
  upgrade to cacti-0.8.8g or downgrade to rrdtool-1.4.x to work
  properly.

  bug:0002567: RRDTool 1.5.x Support

  http://www.cacti.net/changelog.php

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1664107/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+17.04.20170213-0ubuntu1

---
unity-control-center (15.04.0+17.04.20170213-0ubuntu1) zesty; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
the password. There's a codepath for directly setting the password
when the user is setting their own, but this doesn't set the AS mode
back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Mon, 13 Feb
2017 10:04:53 +

** Changed in: unity-control-center (Ubuntu)
   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/1630156

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Confirmed
Status in unity-control-center source package in Xenial:
  In Progress
Status in lightdm source package in Yakkety:
  Confirmed
Status in unity-control-center source package in Yakkety:
  In Progress

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")
  3. Check that the user is in the nopasswdlogin group
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Check that the user is *not* in the nopasswdlogin group.

  The key problem is: it won't remove user from nopasswdlogin in step 4.
  At step 5, you are left in the group.

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1639507] Re: unity-control-center in installed software is listed with wrong icon and title

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+17.04.20170213-0ubuntu1

---
unity-control-center (15.04.0+17.04.20170213-0ubuntu1) zesty; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
the password. There's a codepath for directly setting the password
when the user is setting their own, but this doesn't set the AS mode
back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Mon, 13 Feb
2017 10:04:53 +

** Changed in: unity-control-center (Ubuntu Zesty)
   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/1639507

Title:
  unity-control-center in installed software is listed with wrong icon
  and title

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Triaged
Status in unity-control-center source package in Yakkety:
  Triaged
Status in unity-control-center source package in Zesty:
  Fix Released

Bug description:
  In Ubuntu Software under Installed programs the listing for 
gnome-control-center package has title "Wacom Tablet" and tablet icon.
  This is dangerously confusing, as average user can easily remove control 
center without knowing it.
  I propose disabling gnome-control-center removal from Ubuntu Software by 
moving it to "System Applications" section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1639507/+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 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments

[Manoj Iyer]

** Summary changed:

- [SRU] kexec: arm64: Increase the upper limit for RAM segments
+ kexec: arm64: Increase the upper limit for RAM segments

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

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

** Changed in: kexec-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: kexec-tools (Ubuntu Yakkety)
 Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: kexec-tools (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: kexec-tools (Ubuntu)
   Status: New => In Progress

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

Title:
  kexec: arm64: Increase the upper limit for RAM segments

Status in kexec-tools package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in kexec-tools source package in Yakkety:
  In Progress
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [Impact]
  Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem.

  On a newer UEFI based Qualcomm target the number of system ram regions
  retrieved from /proc/iomem  are ~40. Currently KEXEC_SEGMENT_MAX is
  set to 16, which represents the kexec segments passed to kexec_load
  syscall, like kernel image, initrd image etc. The patch increases the
  value to 64. This enables kexec to see all the "System RAM" as
  recorded in /proc/iomem.

  [Test Case]
  == System RAM reported by /proc/iomem ==
  ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM"
  0020-0020 : System RAM
  0082-0307 : System RAM
  0308-0308 : System RAM
  0309-031f : System RAM
  0320-033f : System RAM
  0341-0589 : System RAM
  058a-058a : System RAM
  058b-058b : System RAM
  058c-0597 : System RAM
  0598-05987fff : System RAM
  05988000-0598bfff : System RAM
  0598c000-05a0 : System RAM
  05a1-05aa : System RAM
  05ab-05ca0fff : System RAM
  05ca1000-08ca : System RAM
  08cb-08cf : System RAM
  08d0-08ed : System RAM
  08ee-08ee0fff : System RAM
  08ee1000-08ee3fff : System RAM
  08ee4000-08ee : System RAM
  08ef-092a : System RAM
  092b-092d : System RAM
  092e-09422fff : System RAM
  09423000-0949 : System RAM
  094a-0957 : System RAM
  0958-0958cfff : System RAM
  0958d000-098c : System RAM
  098d-098d0fff : System RAM
  098d1000-098dbfff : System RAM
  098dc000-0e8b : System RAM
  0e8c-0e8e : System RAM
  0e8f-0fff : System RAM
  1080-17fe : System RAM
  1c02-1c7f : System RAM
  1c80-1c80 : System RAM
  1c81-7efb : System RAM
  7efc-7efd : System RAM
  7efe-7efe : System RAM
  7eff-7eff : System RAM
  7f00-17 : System RAM
  ubuntu@ubuntu:~$

  == BEFORE PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM
  get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM
  get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM
  get_memory_ranges_iomem_cb: 0309 - 031f : System RAM
  get_memory_ranges_iomem_cb: 0320 - 033f : System RAM
  get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM
  get_memory_ranges_iomem_cb: 058a - 058a : System RAM
  get_memory_ranges_iomem_cb: 058b - 058b : System RAM
  get_memory_ranges_iomem_cb: 058c - 0597 : System RAM
  get_memory_ranges_iomem_cb: 0598 - 05987fff : System RAM
  get_memory_ranges_iomem_cb: 05988000 - 0598bfff : System RAM
  get_memory_ranges_iomem_cb: 0598c000 - 05a0 : System RAM
  get_memory_ranges_iomem_cb: 05a1 - 05aa : System RAM
  get_memory_ranges_iomem_cb: 05ab - 05ca0fff : System RAM
  get_memory_ranges_iomem_cb: 05ca1000 - 08ca : System RAM
  get_memory_ranges_iomem_cb: 08cb - 08cf : System RAM

  ==AFTER PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM

[Group.of.nepali.translators] [Bug 1662491] Re: gce-compute-image-packages dropped udev rules that were present in gce-utils

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20160930-0ubuntu4

---
gce-compute-image-packages (20160930-0ubuntu4) zesty; urgency=medium

  * Reintroduce udev rules that configure GCE-specific behaviour.
(LP: #1662491)

 -- Daniel Watkins   Mon, 06 Feb 2017
16:22:37 +

** Changed in: gce-compute-image-packages (Ubuntu Zesty)
   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/1662491

Title:
  gce-compute-image-packages dropped udev rules that were present in
  gce-utils

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  New
Status in gce-compute-image-packages source package in Xenial:
  New
Status in gce-compute-image-packages source package in Yakkety:
  New
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  The udev rules were tuning the performance for GCE's specific
  environment, so users are seeing a substantial performance hit in some
  cases.

  [Test Case]

  /sys/block/sda/queue/scheduler should show noop as the selected
  scheduler.

  [Regression Potential]

  There is limited regression potential, as the rules have been
  recommended for use by GCE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1662491/+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 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[Launchpad Bug Tracker]

This bug was fixed in the package bind9 - 1:9.9.5.dfsg-3ubuntu0.12

---
bind9 (1:9.9.5.dfsg-3ubuntu0.12) trusty; urgency=medium

  * Backport (70_precise_mtime.diff) 18b87b2a58d422fe4d3073540bf89b5a812ed2e5
to trusty. LP: #1553176

 -- LaMont Jones   Fri, 03 Feb 2017 13:13:21 -0700

** Changed in: bind9 (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/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

Status in BIND:
  Fix Released
Status in MAAS:
  Fix Released
Status in MAAS 1.9 series:
  In Progress
Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Trusty:
  Fix Released
Status in bind9 source package in Xenial:
  Fix Released

Bug description:
  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.

  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check
  is only done to a granularity of seconds, changing the zone file twice
  in the same second can cause BIND to decide that it need not reload
  the zone, even though it is out of date.

  [Impact]

   * If a zone file is changed (generally by automated processes) more
  than once in a second, bind9 happily thinks it has already loaded the
  zone.  A trivial demonstration of the bug can be seen at
  paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
  same test with the fixed code.  Making this a test case is somewhat
  problematic in that it needs to make sure that they happen inside of
  the same second.

   * MAAS is exactly the sort of use case that hits this bug.

   * The upload changes BIND's utility function to actual use the
  st_mtim.tv_nsec instead of '0'.

  [Test Case]

   * See the pastebin above.  (Change a zone file and reload it, and
  then do it again less than a second later.)

  [Regression Potential]

   * Ignoring the whole "rebuilds sometimes break things", the most
  likely regression would be one where something was either relying on
  BIND not reloading the dozone (unlikely), or otherwise relying on the
  modify time on a zone file to some arbitrary value.

  [Other Info]

    This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial
  March 2016.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+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 1662708] Re: [REGRESSION][4.4.0-62] Wifi connection drops after some time.

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => 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/1662708

Title:
  [REGRESSION][4.4.0-62] Wifi connection drops after some time.

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

Bug description:
  There is a regression on x250 laptops using the iwlwifi wireless
  driver.  The regression was introduce between 4.4.0-59 and 4.4.0-62.

  Wifi hardware:
  03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 
[8086:095b] (rev 99)

  No commits stick out between those versions, so a bisect is being
  performed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662708/+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 1624164] Re: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo

[Seth Forshee]

The kbl_dmc firmware had been added in xenial at one point but was
removed because it caused a regression. Since the firmware is optional
we can make it so that the module won't cause this message to be
generated when regenerating the initramfs. Therefore I'll mark this as
"won't fix" for linux-firmware and add a linux task.

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for
  module i915_bpo

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Won't Fix

Bug description:
  Also: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin
  for module i915_bpo

  Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for
  module i915_bpo

  Ubuntu 16.04 Xenial

  Packages:

  ii  linux-firmware1.157.3   all   Firmware 
for Linux kernel drivers
  ii  linux-image-generic   4.4.0.36.38   amd64 Generic 
Linux kernel image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624164/+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 1662551] Re: ibmvscsis: Add SGL LIMIT

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-February/082445.html

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: Incomplete

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

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

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

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

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi)

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

Title:
  ibmvscsis: Add SGL LIMIT

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

Bug description:
  ---Problem Description---
  Provide an internal LIO SGL Limit, since the driver is already establishing 
and setting max transfer size on transport layer of 1MB to client. We should 
keep consistency and provide that limit to LIO.
   
  Upstream submission was made. Awaiting acceptance to provide commit id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662551/+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 1641532] Re: machine-types trusty and utopic are not unique (depend on the qemu version)

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.8+dfsg-2ubuntu1

---
qemu (1:2.8+dfsg-2ubuntu1) zesty; urgency=medium

  * Merge with Debian; remaining changes:
- add qemu-kvm init script and defaults file
  (d/qemu-system-common.qemu-kvm.*)
- d/rules, d/qemu-kvm-init: add and install script loading kvm
  modules and handling /etc/default/qemu-kvm
- qemu-system-common.preinst: add kvm group if needed
- Enable nesting by default on intel.
  - set default module option
  - re-load kvm_intel.ko if it was loaded without nested=1
  - d/p/ubuntu/expose-vmx_qemu64cpu.patch: enable nested kvm by
default in qemu64 cpu type.
- Enable svm by default for qemu64 on amd
- d/p/ubuntu/define-ubuntu-machine-types.patch: define distro machine
  types to ease future live vm migration.
- Make qemu-system-common depend on qemu-block-extra
- Make qemu-utils depend on qemu-block-extra
- s390x support
  - Create qemu-system-s390x package
  - Include s390-ccw.img firmware
- qemu-system-common.postinst:
  - change acl placed by udev, and add udevadm trigger.
  - d/control-in: change dependencies for fix of wrong acl for newly
created device node on ubuntu
- have qemu-system-arm suggest: qemu-efi; this should be a stronger
  relationship, but qemu-efi is still in universe right now.
- d/qemu-kvm-init, d/kvm.powerpc, d/control-in: check SMT on ppc64el
- Several changes were applied but missing in the changelog so far
  - d/qemu-system-ppc.links provide usr/bin/qemu-system-ppc64le symlink
  - arch aware kvm wrapper
  - update VCS links
  - no more skip disable libiscsi on Ubuntu
  - let qemu-utils recommend sharutils
  - disable x32 architecture
  * Dropped Changes:
- Several changes were applied but missing in the changelog so far
  but are no more needed
  - no pie for relocatable LD calls, with toolchain defaulting to
pie (fixed upstream)
  - enable libnuma-dev (now in Debian)
  - transition for moved init scripts (can be dropped after LTS
containing >=2.5 which is Xenial)
  - --enable-seccomp related whitespace change (had no effect)
- apport hook for qemu source package (In Debian)
- add upstart script (d/qemu-system-common.qemu-kvm.upstart)
- d/qemu-system-x86.maintscript: transition off of
  /etc/init.d/qemu-system-x86 (can be dropped after Xenial)
- Enable pie by default, on ubuntu/s390x. (Is the default since
  >=Xenial, no cloud archive backport <=Xenial to consider)
- no pie for relocatable LD calls (fixed upstream in commit
  7ecf44a5)
- CVEs: CVE-2016-5403, CVE-2016-6351, CVE-2016-6490 (now Upstream)
- Revert fix for CVE-2016-5403, causes regression see USN-3047-2.
  (Improved fix included by upstream)
- Enable GPU Passthru for ppc64le (is upstream in qemu 2.7)
- Fixed wrong migration blocker when vhost is used (is upstream in
  qemu 2.8)
  * Added Changes:
- d/rules, d/control-in: avoid people editing d/control by warning
  header and non writable permissions
- fixed moving trusty machine type definition which made it
  ambiguous (LP: #1641532)
  - d/qemu-system-x86.NEWS describe the issue
- Enable seccomp for ppc64el (LP: #1644639)
- Enable numa support for s390x
- d/qemu-system-common.qemu-kvm.init: fix lintian error type
  init.d-script-missing-dependency-on-remote_fs
- d/qemu-system-common.postinst: fix lintian error type
  command-with-path-in-maintainer-script
- Transition qemu-kvm to a systemd unit
- Disable glusterfs (Universe dependency)
- d/qemu-kvm-init, d/kvm.powerpc ppc64el SMT check avoid unwanted output
- d/qemu-kvm-init, d/kvm.powerpc ppc64el SMT check keep output local so
  that it shows up where the user expects (sytemctl status, kvm stdout)
- d/qemu-kvm-init ppc64el warn on expected second level kvm-hv load failure
- add arch aware kvm wrapper for s390x
- d/p/ubuntu/ctrl-a-b-fix-fb5e19d2.patch: char: fix ctrl-a b not working
- Enable DDW in Yakkety machine type because "Enable GPU Passthru for
  ppc64le" was released as part of qemu 2.6 (can be dropped at 18.10,
  merged in d/p/ubuntu/define-ubuntu-machine-types.patch)

 -- Christian Ehrhardt   Mon, 16 Jan
2017 16:27:11 +0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5403

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6351

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6490

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

Title:
  machine-types trusty and utopic are not unique