[Group.of.nepali.translators] [Bug 1632538] Re: Using generate_service_certificate and undercloud_public_vip in undercloud.conf breaks nova

[Juan Antonio Osorio Robles]

Emilien, this wasn't a tripleo issue by itself; but an issue with a
library version. This has been fixed already.

** Changed in: tripleo
   Status: Triaged => 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/1632538

Title:
  Using generate_service_certificate and undercloud_public_vip in
  undercloud.conf breaks nova

Status in OpenStack Compute (nova):
  Incomplete
Status in OpenStack Compute (nova) newton series:
  Incomplete
Status in tripleo:
  Invalid
Status in python-rfc3986 package in Ubuntu:
  Fix Released
Status in python-rfc3986 source package in Xenial:
  Fix Committed
Status in python-rfc3986 source package in Yakkety:
  Fix Committed
Status in python-rfc3986 source package in Zesty:
  Fix Released

Bug description:
  Enabling SSL on the Undercloud using generate_service_certificate
  results in all Nova services on the undercloud (api, cert, compute,
  conductor, scheduler), all failing with errors similar to the
  following:

  2016-10-11 22:28:27.327 66082 CRITICAL nova 
[req-b5f37af3-96fc-42e2-aaa6-52815aca07fe - - - - -] ConfigFileValueError: 
Value for option url is not valid: invalid URI: 
'https://rdo-ci-fx2-06-s5.v103.rdoci.lab.eng.rdu.redhat.com:13696'
  2016-10-11 22:28:27.327 66082 ERROR nova Traceback (most recent call last):
  2016-10-11 22:28:27.327 66082 ERROR nova   File "/usr/bin/nova-cert", line 
10, in 
  2016-10-11 22:28:27.327 66082 ERROR nova sys.exit(main())
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/cmd/cert.py", line 49, in main
  2016-10-11 22:28:27.327 66082 ERROR nova service.wait()
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/service.py", line 415, in wait
  2016-10-11 22:28:27.327 66082 ERROR nova _launcher.wait()
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_service/service.py", line 328, in wait
  2016-10-11 22:28:27.327 66082 ERROR nova status, signo = 
self._wait_for_exit_or_signal()
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_service/service.py", line 303, in 
_wait_for_exit_or_signal
  2016-10-11 22:28:27.327 66082 ERROR nova self.conf.log_opt_values(LOG, 
logging.DEBUG)
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2630, in 
log_opt_values
  2016-10-11 22:28:27.327 66082 ERROR nova _sanitize(opt, 
getattr(group_attr, opt_name)))
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 3061, in __getattr__
  2016-10-11 22:28:27.327 66082 ERROR nova return self._conf._get(name, 
self._group)
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2672, in _get
  2016-10-11 22:28:27.327 66082 ERROR nova value = self._do_get(name, 
group, namespace)
  2016-10-11 22:28:27.327 66082 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2715, in _do_get
  2016-10-11 22:28:27.327 66082 ERROR nova % (opt.name, str(ve)))
  2016-10-11 22:28:27.327 66082 ERROR nova ConfigFileValueError: Value for 
option url is not valid: invalid URI: 
'https://rdo-ci-fx2-06-s5.v103.rdoci.lab.eng.rdu.redhat.com:13696'
  2016-10-11 22:28:27.327 66082 ERROR nova 

  I believe the failure happens inside the [neutron] section of
  /etc/nova/nova.conf.

  This does not look related to the scheme (https) being used as the
  result of enabling SSL because doing a one-off test with the
  openstack-nova-conductor service after changing the schema to http
  results in the same startup failure.

  Another one-off test substituting an IP address instead of a FQDN
  inside of nova.conf with the openstack-nova-conductor service as
  before results in openstack-nova-conductor starting properly but
  eventually failing with a connection-related failure due to the one-
  off data used (an IP address of 1.2.3.4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1632538/+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 1525605] Re: package repo (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/repo', which is also in package phablet-tools 1.1+15.10.20150925.2

[Jeremy Bicha]

** Also affects: phablet-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: phablet-tools (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: phablet-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  package repo (not installed) failed to install/upgrade: trying to
  overwrite '/usr/bin/repo', which is also in package phablet-tools
  1.1+15.10.20150925.2-0ubuntu1

Status in Phablet Tools:
  Confirmed
Status in phablet-tools package in Ubuntu:
  Fix Released
Status in phablet-tools source package in Xenial:
  Triaged

Bug description:
  bought mom a new kindle, fifty bux, b/c she can't have mine, the old
  one, leaning port, i'm about to install cyanogenmod, or at least i
  hope i can,

  idk

  #messagebox

  #ruby #python

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: repo (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sat Dec 12 22:26:18 2015
  DuplicateSignature: package:repo:(not installed):trying to overwrite 
'/usr/bin/repo', which is also in package phablet-tools 
1.1+15.10.20150925.2-0ubuntu1
  ErrorMessage: trying to overwrite '/usr/bin/repo', which is also in package 
phablet-tools 1.1+15.10.20150925.2-0ubuntu1
  InstallationDate: Installed on 2015-12-12 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: repo
  Title: package repo (not installed) failed to install/upgrade: trying to 
overwrite '/usr/bin/repo', which is also in package phablet-tools 
1.1+15.10.20150925.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/phablet-tools/+bug/1525605/+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 1620979] Re: Hotkey doesn't work on HP x360

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Fix Released

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

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

Title:
  Hotkey doesn't work on HP x360

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  When pinctrl-cherryview probing gpio device it clear interrupt mask and 
status, and in the later procedures the interrupt mask isn't set back 
correctly, leads to hotkeys fail.

  [Fix]
  Upstream fixes this in 4.8-rc3 by not clearing interrupt masks:

  commit bcb48cca23ec9852739e4a464307fa29515bbe48
  Author: Mika Westerberg 
  Date:   Mon Aug 22 14:42:52 2016 +0300

  pinctrl: cherryview: Do not mask all interrupts in probe

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1620979/+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 1616813] Re: Please add support for alps touchpad.

[Anthony Wong]

** Changed in: hwe-next
   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/1616813

Title:
  Please add support for alps touchpad.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Hi,

  We need to support alps touchpad. Please considering SRU.
  The following ko needs to be used:
  1. hid-generic.ko
  3. hid-alps.ko

  This driver is backported from mainline v4.8-rc3 to linux 4.4 in
  xenial.

  Yours,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616813/+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 1515503] Re: Need support for some buggy Synaptics RMI4 device

[Anthony Wong]

** Changed in: hwe-next
   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/1515503

Title:
  Need support for some buggy Synaptics RMI4 device

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some RMI4 touchpad doesn't work properly even the probing returns no
  error. Further investigation shows the interrupt doesn't increase at
  all. There's already a public bug and the patch is already upstreamed:

  https://bugs.freedesktop.org/show_bug.cgi?id=91102

  [Fix]

  There's a fix contains in v4.3-rc1 and has already been tested:

  commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba
  Author: Andrew Duggan 
  AuthorDate: Thu Jul 16 17:14:00 2015 -0700
  Commit: Jiri Kosina 
  CommitDate: Fri Jul 17 11:29:53 2015 +0200

  HID: rmi: Set F01 interrupt enable register when not set

  Note:
So far the platform we encounter with this issue use GPIO interrupt, so it 
also needs 3.19.0-32 or Wily kernel to work too.

  [Test]

  1. Boot with v4.3-rc1 -> pass
  2. Boot with patched Vivid kernel -> pass
  3. Boot with patched Wily kernel -> pass

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1515503/+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 1632578] Re: Add support for KabeLake i219-LOM chips

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  Add support for KabeLake i219-LOM chips

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  There's a commit add device ids to support new i219 Lan-on-
  motherboard:

  commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
  e1000e: Initial support for KabeLake

  [Impact]

  Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
  [8086:15d8]. This patch only add device ids so no further regressions
  are expected.

  [Test]

  Though the commit log says it's "Initial support", but it's been
  successfully tested on multiple platforms and no further issues are
  spotted, so at the moment no further patches are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1632578/+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 1589006] Re: Failed unmounting Mount unit for nvidia support in snappy

[Mathew Hodson]

** No longer affects: nvidia-graphics-drivers-352 (Ubuntu)

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

Title:
  Failed unmounting Mount unit for nvidia support in snappy

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released

Bug description:
  Hello after upgrade nvidia drivers(proposed repo) on my laptop..i can
  not login successful (loop at login). I try CTRL+ALT+F1 and purge
  nvidia-361..but this occurs :

  Job for var-lib-snapd-lib-gl.mount failed. See "systemctl status var-
  lib-snapd-lib-gl.mount" and "journalctl -xe" for details.

  ..after type:

  $ journalct -xe

  -- Unit var-lib-snapd-lib-gl.mount has begun shutting down.
  jun 04 00:26:17 Unity-X550JF umount[4139]: umount: /var/lib/snapd/lib/gl: 
target is busy
  jun 04 00:26:17 Unity-X550JF umount[4139]: (In some cases useful info 
about processes that
  jun 04 00:26:17 Unity-X550JF umount[4139]:  use the device is found 
by lsof(8) or fuser(1).)
  jun 04 00:26:17 Unity-X550JF systemd[1]: var-lib-snapd-lib-gl.mount: Mount 
process exited, code=exited status=32
  jun 04 00:26:17 Unity-X550JF systemd[1]: Failed unmounting Mount unit for 
nvidia support in snappy.
  -- Subject: Unit var-lib-snapd-lib-gl.mount has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit var-lib-snapd-lib-gl.mount has finished shutting down.
  jun 04 00:26:17 Unity-X550JF sudo[4094]: pam_unix(sudo:session): session 
closed for user root

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589006/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu13

---
systemd (229-4ubuntu13) xenial; urgency=medium

  [ Martin Pitt ]
  * Backport graphical-session{,-pre}.target user units, for future usage from
snaps. (LP: #1640293)
  * debian/rules: Clean up *.busname units. They are useless in 16.04 as they
will always be "condition failed" as kdbus has never existed. But they add
ordering constraints which make it impossible to start
systemd-networkd.service during early boot, which is an upcoming
requirement for cloud-init. (Part of LP: #1636912)
  * Drop systemd-networkd's "After=dbus.service" ordering so that it can start
during early boot (for cloud-init.service). It will auto-connect to D-Bus
once it becomes available later, and transient (from DHCP) hostname and
timezone setting do not work in 16.04 anyway. (LP: #1636912)

  [ Dan Streetman ]
  * rules: introduce disk/by-id (wwid and model_serial) symlinks
for NVMe drives (LP: #1642903)

 -- Martin Pitt   Thu, 24 Nov 2016 12:41:23
+0100

** Changed in: systemd (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/1636912

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  New

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd 

[Group.of.nepali.translators] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-9ubuntu2

---
systemd (231-9ubuntu2) yakkety; urgency=medium

  [ Dan Streetman ]
  * rules: introduce disk/by-id (model_serial) symlinks for NVMe drives
(LP: #1642903)

  [ Martin Pitt ]
  * Drop systemd-networkd's "After=dbus.service" ordering, so that it can
start during early boot (for cloud-init.service). It will auto-connect to
D-Bus once it becomes available later, and transient (from DHCP) hostname
and timezone setting do not work in 16.10 anyway. (LP: #1636912)

 -- Martin Pitt   Thu, 24 Nov 2016 13:21:05
+0100

** Changed in: systemd (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/1642903

Title:
  introduce disk/by-id (model_serial) symlinks for NVMe drives

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

Bug description:
  [Impact]

  NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
  SERIAL symlinks.

  [Test Case]

  On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
  with the patch, it will contain link(s) named by the drive serial
  number. This should be the *only* change in `ls -l /dev/disk/*/*`.

  On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
  identical (aside from dates, of course) before and after the upgrade
  to the -proposed version.

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or  clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This patch is already included upstream and in zesty systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-9ubuntu2

---
systemd (231-9ubuntu2) yakkety; urgency=medium

  [ Dan Streetman ]
  * rules: introduce disk/by-id (model_serial) symlinks for NVMe drives
(LP: #1642903)

  [ Martin Pitt ]
  * Drop systemd-networkd's "After=dbus.service" ordering, so that it can
start during early boot (for cloud-init.service). It will auto-connect to
D-Bus once it becomes available later, and transient (from DHCP) hostname
and timezone setting do not work in 16.10 anyway. (LP: #1636912)

 -- Martin Pitt   Thu, 24 Nov 2016 13:21:05
+0100

** Changed in: systemd (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/1636912

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  New

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  

[Group.of.nepali.translators] [Bug 1640293] Re: Backport graphical-session{, -pre}.target to xenial

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu13

---
systemd (229-4ubuntu13) xenial; urgency=medium

  [ Martin Pitt ]
  * Backport graphical-session{,-pre}.target user units, for future usage from
snaps. (LP: #1640293)
  * debian/rules: Clean up *.busname units. They are useless in 16.04 as they
will always be "condition failed" as kdbus has never existed. But they add
ordering constraints which make it impossible to start
systemd-networkd.service during early boot, which is an upcoming
requirement for cloud-init. (Part of LP: #1636912)
  * Drop systemd-networkd's "After=dbus.service" ordering so that it can start
during early boot (for cloud-init.service). It will auto-connect to D-Bus
once it becomes available later, and transient (from DHCP) hostname and
timezone setting do not work in 16.04 anyway. (LP: #1636912)

  [ Dan Streetman ]
  * rules: introduce disk/by-id (wwid and model_serial) symlinks
for NVMe drives (LP: #1642903)

 -- Martin Pitt   Thu, 24 Nov 2016 12:41:23
+0100

** Changed in: systemd (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/1640293

Title:
  Backport graphical-session{,-pre}.target to xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  Ted Gould and Dimitri Ledkov requested that the graphical-
  session{,-pre}.target user units introduced in yakkety should be
  backported to xenial, so that snapd units can use them.

  At the moment they will *not* be used by default by any desktop
  session in xenial, so they will stay inert. The net effect is solely
  to ship those two new unit files.

  TEST CASE: Verify that these two new units exist in the -proposed
  version:

/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target

  and that they are *not* running (systemctl --user status graphical-
  session{,-pre}.target)

  REGRESSION POTENTIAL: Practically zero.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1640293/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu13

---
systemd (229-4ubuntu13) xenial; urgency=medium

  [ Martin Pitt ]
  * Backport graphical-session{,-pre}.target user units, for future usage from
snaps. (LP: #1640293)
  * debian/rules: Clean up *.busname units. They are useless in 16.04 as they
will always be "condition failed" as kdbus has never existed. But they add
ordering constraints which make it impossible to start
systemd-networkd.service during early boot, which is an upcoming
requirement for cloud-init. (Part of LP: #1636912)
  * Drop systemd-networkd's "After=dbus.service" ordering so that it can start
during early boot (for cloud-init.service). It will auto-connect to D-Bus
once it becomes available later, and transient (from DHCP) hostname and
timezone setting do not work in 16.04 anyway. (LP: #1636912)

  [ Dan Streetman ]
  * rules: introduce disk/by-id (wwid and model_serial) symlinks
for NVMe drives (LP: #1642903)

 -- Martin Pitt   Thu, 24 Nov 2016 12:41:23
+0100

** Changed in: systemd (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/1642903

Title:
  introduce disk/by-id (model_serial) symlinks for NVMe drives

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

Bug description:
  [Impact]

  NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
  SERIAL symlinks.

  [Test Case]

  On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
  with the patch, it will contain link(s) named by the drive serial
  number. This should be the *only* change in `ls -l /dev/disk/*/*`.

  On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
  identical (aside from dates, of course) before and after the upgrade
  to the -proposed version.

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or  clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This patch is already included upstream and in zesty systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1647376] Re: docker should not de-configure pre-existing bridge interfaces

[Launchpad Bug Tracker]

This bug was fixed in the package docker.io - 1.12.3-0ubuntu4

---
docker.io (1.12.3-0ubuntu4) zesty; urgency=medium

  * Explicity depend on the version of runc that was built with seccomp
support.

 -- Michael Hudson-Doyle   Mon, 12 Dec 2016
11:15:01 +1300

** Changed in: docker.io (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  docker should not de-configure pre-existing bridge interfaces

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in docker.io source package in Yakkety:
  New

Bug description:
  Since moving to docker 1.12, management of networks to be used by
  docker images is done via "docker network (create/rm)". Currently
  docker assumes (for the bridge driver at least) that it has to do full
  setup/cleanup of the associated bridge interface. This is fatal for
  those cases where an existing bridge interface is used to declare the
  network to docker.

  This is fixed in docker 1.13 by the attached patch (this is a backport
  from docker upstream, it applies to yakkety and xenial but has to drop
  one more hunk in zesty).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1647376/+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 1603581] Re: Azure Linux Agent (WALA) 2.1.5 Released

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.1.5-0ubuntu4~14.04.0

---
walinuxagent (2.1.5-0ubuntu4~14.04.0) trusty; urgency=medium

  * Backport to trusty (LP: #1603581)

  [ Steve Langasek ]
  * Drop systemctl reference from ephemeral-disk-warning.conf, this command
doesn't exist in trusty.

 -- Jose Luis Vazquez Gonzalez (Jose Vazquez)
  Thu, 01 Dec 2016 11:41:07 +0100

** Changed in: walinuxagent (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/1603581

Title:
  Azure Linux Agent (WALA) 2.1.5 Released

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released

Bug description:
  [Original Description]

  As discussed in an email, the Linux Agent (WALA) version 2.1.5 has now
  been signed off and is in Master now.

  Please find the details below of some of items built into this release :
  https://github.com/Azure/WALinuxAgent/releases

  We would like you to take this version and test it within your images,
  please can you file any bugs in Github, as this is monitored by our
  dev team.

  If you have any questions please reach out to me directly or raise it
  through Github.

  [SRU TEMPLATE]

  [Impact]

  Version 2.1.5 introduced goal state processing extension, multi-nic
  improvements & several bug fixes:
  https://github.com/Azure/WALinuxAgent/releases

  [Test case 1]: Upgrade testing
  1.) Launch instance on Azure
  2.) Upgrade walinuxagent from -proposed
  3.) Confirm that "waagent" is running, check /var/log/waagent.log
  4.) Reboot, repeat step 3
  5.) Capture instance and provsion new instances; repeat step 3

  [Test Case 2]: New instance
  1.) Build new cloud image from -proposed
  2.) Boot instance
  3.) Confirm that instance provisioned

  More on the test plan:
  https://wiki.ubuntu.com/walinuxagentUpdates

  [Upstream Testing]
  The Canonical Cloud Image team has been working with Microsoft to ensure that 
this package is well tested. Validation will be performed by both Microsoft and 
the Canonical Cloud Image team.

  [Regression Potential]
  Currently, WALinuxAgent uses Python 2. With the 2.1.x branch, WALinuxAgent 
started using Python 3.

  This version has been in use on yakkety since release, so it is known
  to work. Azure consider Ubuntu to be a flagship platform, so will be
  active in addressing any regressions that are found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1603581/+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 1610210] Re: All metar fetches fail due to NOAA 302 redirect

[Launchpad Bug Tracker]

This bug was fixed in the package metar - 20061030.1-2ubuntu3

---
metar (20061030.1-2ubuntu3) xenial; urgency=medium

  * SRU of 20061030.1-2.2 from Yakkety Yak and later,
fixes new upstream URL (LP: #1610210)

 -- Daniel Lange   Fri, 02 Dec 2016 09:58:27 +0100

** Changed in: metar (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/1610210

Title:
  All metar fetches fail due to NOAA 302 redirect

Status in metar package in Ubuntu:
  Fix Released
Status in metar source package in Xenial:
  Fix Released
Status in metar package in Debian:
  Fix Released

Bug description:
  [Impact]

   * NOAA changed the URL for the service metar relies on to retrieve weather 
information
   * This has been fixed in 20061030.1-2.2 that is in YY and ZZ (LP: #1610210)
 but not yet in XX (16.04 LTS) and previous releases
   * justification: the metar program will not display any weather information
 anymore without the fix (complete functionality loss for users)
   * remedy: update URL in the source (it is hardcoded)
 (a work-around is to set the environment variable to the new URL
  METARURL=http://tgftp.nws.noaa.gov/data/observations/metar/stations)

  [Test Case]

   * install metar # 20061030.1-2ubuntu2
   * metar FACT # metar information for Cape Town Airport (CPT)
 -> METAR pattern not found in NOAA data
 (correct would be something like: FACT 251000Z 18020KT CAVOK 22/13 Q1017 
NOSIG)

  [Regression Potential]

   * just a hardcoded URL fix, no program change otherwise
   * works in Debian sid & testing, Ubuntu YY and ZZ

  [Other Info]

   * Stable upload in progress as well for next Debian Jessie point-
  release

  -

  All metar fetches are failing:

  $ metar LSZH
  METAR pattern not found in NOAA data.

  Requests for
  http://weather.noaa.gov/pub/data/observations/metar/stations/.TXT
  are now receiving a 302 redirect to
  http://tgftp.nws.noaa.gov/data/observations/metar/stations/.TXT

  metar needs an updated METARURL, or to set CURLOPT_FOLLOWLOCATION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metar/+bug/1610210/+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 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.3-0ubuntu8.2

---
apport (2.20.3-0ubuntu8.2) yakkety-security; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: code execution via malicious crash files
- Use ast.literal_eval in apport/ui.py, added test to test/test_ui.py.
- No CVE number
- LP: #1648806
  * SECURITY UPDATE: path traversal vulnerability with hooks execution
- Clean path in apport/report.py, added test to test/test_ui.py.
- No CVE number
- LP: #1648806

  [ Steve Beattie ]
  * SECURITY UPDATE: code execution via malicious crash files
- Only offer restarting the application when processing a
  crash file in /var/crash in apport/ui.py, gtk/apport-gtk,
  and kde/apport-kde. Add testcases to test/test_ui.py,
  test/test_ui_gtk.py, and test_ui_kde.py.
- No CVE number
- LP: #1648806

 -- Marc Deslauriers   Tue, 13 Dec 2016
10:55:09 -0800

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1648806/+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 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.23

---
apport (2.14.1-0ubuntu3.23) trusty-security; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: code execution via malicious crash files
- Use ast.literal_eval in apport/ui.py, added test to test/test_ui.py.
- No CVE number
- LP: #1648806
  * SECURITY UPDATE: path traversal vulnerability with hooks execution
- Clean path in apport/report.py, added test to test/test_ui.py.
- No CVE number
- LP: #1648806

  [ Steve Beattie ]
  * SECURITY UPDATE: code execution via malicious crash files
- Only offer restarting the application when processing a
  crash file in /var/crash in apport/ui.py, gtk/apport-gtk,
  and kde/apport-kde. Add testcases to test/test_ui.py,
  test/test_ui_gtk.py, and test_ui_kde.py.
- No CVE number
- LP: #1648806

 -- Marc Deslauriers   Mon, 12 Dec 2016
07:27:21 -0500

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1648806/+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 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

[Martin Pitt]

New upstream release with the fixes:
https://launchpad.net/apport/trunk/2.20.4

Note that Brian committed some changes to trunk in the last 1.5 hours,
so we had some mid-air collection. I force-pushed trunk and will put
back his commits on top.

** Changed in: apport
   Status: In Progress => Fix Released

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1648806/+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 1649718] Re: Linux rtc self test fails in a VM under xenial

[Seth Forshee]

Those kernel patches fix the problem. Changing the package to linux,
I'll get those patches into xenial's kernel.

Ryan, thanks for the help.

** Package changed: qemu (Ubuntu) => linux (Ubuntu)

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

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

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

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

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

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

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

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

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

Title:
  Linux rtc self test fails in a VM under xenial

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

Bug description:
  ADT testing for the linux package hangs at the kernel's rtc selftest,
  for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/linux/20161212_132117_a258d@/log.gz

  Running this test manually, I've observed that this will hang in me
  with various kernel versions going back to 4.4 in a VM on my machine
  which is running xenial. The test runs to completion in a VM on a
  different machine running zesty.

  This is the section of the test which produces the hang:

  /* Turn on update interrupts (one per second) */
  retval = ioctl(fd, RTC_UIE_ON, 0);
  if (retval == -1) {
  if (errno == EINVAL) {
  fprintf(stderr,
  "\n...Update IRQs not supported.\n");
  goto test_READ;
  }
  perror("RTC_UIE_ON ioctl");
  exit(errno);
  }

  fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
  rtc);
  fflush(stderr);
  for (i=1; i<6; i++) {
  /* This read will block */
  retval = read(fd, , sizeof(unsigned long));
  if (retval == -1) {
  perror("read");
  exit(errno);
  }
  fprintf(stderr, " %d",i);
  fflush(stderr);
  irqcount++;
  }

  The read blocks indefinitely most of the time. After boot it might
  return once or twice before it hangs, but running the test
  subsequently always hangs on the first read. I'll attach the full
  source for the test (rtctest.c).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649718/+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 1621972] Re: python-murano-dashboard does not contain all required files

[Michael Terry]

** Also affects: murano-dashboard (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: murano-dashboard (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: murano-dashboard (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: murano-dashboard (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  python-murano-dashboard does not contain all required files

Status in murano-dashboard package in Ubuntu:
  Fix Released
Status in murano-dashboard source package in Xenial:
  Confirmed

Bug description:
  Currently murano-dashboard package (1:2.0.0-1) in Xenial [1] does not contain 
templates.
  Specifically folder: 
"/usr/lib/python2.7/dist-packages/muranodashboard/templates"

  Here is the link to the file list:
  http://packages.ubuntu.com/xenial/all/python-murano-dashboard/filelist
  http://paste.ubuntu.com/23155732/

  Debian already includes required files:
  https://packages.debian.org/sid/all/python-murano-dashboard/filelist
  http://paste.ubuntu.com/23155734/

  Fix was proposed by Thomas Goirand (zigo):
  
https://anonscm.debian.org/cgit/openstack/murano-dashboard.git/tree/debian/patches/install-missing-files.patch

  Also it is highly recommended sync code with the latest version in 
stable/mitaka branch:
  
https://review.openstack.org/gitweb?p=openstack/murano-dashboard.git;a=shortlog;h=refs/heads/stable/mitaka

  As it contains fix of CVE-2016-4972:
  https://review.openstack.org/#/c/333439/

  
  The detailed instruction how to reproduce the issue was written by my manager 
(Igor Yozhikov):
  
https://docs.google.com/document/d/1zf4WROMtd2Miq57WHDRRC7Qt-GZ6AIpQIlL2S3FT6Qo/view

  
  [1] http://packages.ubuntu.com/xenial/all/python-murano-dashboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/murano-dashboard/+bug/1621972/+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 1648875] Re: linux-snapdragon: 4.4.0-1042.46 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 14. December 2016 19:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 14. December 2016 19:03 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-snapdragon: 4.4.0-1042.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648875/+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 1645698] Re: [SRU] network-manager 1.2.4

[Michael Terry]

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Invalid

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Aron Xu (happyaron)

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  [SRU] network-manager 1.2.4

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Xenial:
  Triaged

Bug description:
  [Impact]

  This SRU would try to have the latest upstream point release of 1.2.x
  land in Xenial, which is the successor of the current 1.2.2 version,
  fixing quite some bugs that's suitable to land in the sable branch.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leak in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+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 1648872] Re: linux-raspi2: 4.4.0-1038.45 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 14. December 2016 17:16 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 14. December 2016 17:16 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-raspi2: 4.4.0-1038.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648872/+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 1572613] Re: GCC stack access scheduled after stack deallocation

[Dimitri John Ledkov]

gcc-avr | 1:4.9.2+Atmel3.5.3-1 | zesty/universe rebuild in zesty

** Changed in: gcc-avr (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/1572613

Title:
  GCC stack access scheduled after stack deallocation

Status in gcc:
  Unknown
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in ceph package in Ubuntu:
  Fix Released
Status in fpgatools package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-arm-none-eabi package in Ubuntu:
  Fix Released
Status in gcc-avr package in Ubuntu:
  Fix Released
Status in gcc-mingw-w64 package in Ubuntu:
  Fix Released
Status in higan package in Ubuntu:
  Fix Released
Status in insighttoolkit4 package in Ubuntu:
  Fix Released
Status in ivtools package in Ubuntu:
  Fix Released
Status in juju-mongodb3.2 package in Ubuntu:
  Fix Released
Status in libtsm package in Ubuntu:
  Fix Released
Status in mariadb-10.0 package in Ubuntu:
  Fix Released
Status in mysql-5.7 package in Ubuntu:
  Fix Released
Status in nodejs package in Ubuntu:
  Fix Released
Status in percona-server-5.6 package in Ubuntu:
  Fix Released
Status in percona-xtrabackup package in Ubuntu:
  Fix Released
Status in percona-xtradb-cluster-5.6 package in Ubuntu:
  Fix Released
Status in valgrind package in Ubuntu:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in ceph source package in Xenial:
  Fix Released
Status in fpgatools source package in Xenial:
  Fix Released
Status in gambas3 source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in higan source package in Xenial:
  Invalid
Status in insighttoolkit4 source package in Xenial:
  Fix Released
Status in ivtools source package in Xenial:
  Invalid
Status in juju-mongodb3.2 source package in Xenial:
  Fix Released
Status in libtsm source package in Xenial:
  Fix Released
Status in mariadb-10.0 source package in Xenial:
  Fix Released
Status in mysql-5.7 source package in Xenial:
  Fix Released
Status in nodejs source package in Xenial:
  Fix Released
Status in percona-server-5.6 source package in Xenial:
  Fix Released
Status in percona-xtrabackup source package in Xenial:
  Fix Released
Status in percona-xtradb-cluster-5.6 source package in Xenial:
  Fix Released
Status in valgrind source package in Xenial:
  Fix Released
Status in webkitgtk source package in Xenial:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Released
Status in fpgatools source package in Yakkety:
  Fix Released
Status in gambas3 source package in Yakkety:
  Fix Released
Status in gcc-5 source package in Yakkety:
  Fix Released
Status in higan source package in Yakkety:
  Fix Released
Status in insighttoolkit4 source package in Yakkety:
  Fix Released
Status in ivtools source package in Yakkety:
  Fix Released
Status in juju-mongodb3.2 source package in Yakkety:
  Fix Released
Status in libtsm source package in Yakkety:
  Fix Released
Status in mariadb-10.0 source package in Yakkety:
  Fix Released
Status in mysql-5.7 source package in Yakkety:
  Fix Released
Status in nodejs source package in Yakkety:
  Fix Released
Status in percona-server-5.6 source package in Yakkety:
  Fix Released
Status in percona-xtrabackup source package in Yakkety:
  Fix Released
Status in percona-xtradb-cluster-5.6 source package in Yakkety:
  Fix Released
Status in valgrind source package in Yakkety:
  Fix Released
Status in webkitgtk source package in Yakkety:
  Fix Released

Bug description:
  = Validation =
  For gcc-5, check that code generation is correct as per small C test case 
below.

  == fpgatools ==

  * compile autotest.c and strip chrpath
  * change path in autotest_diff.sh from ./ to /usr/bin
  * execute autotest and check error codes

  == gambas3 ==

  * execute gambas.test

  == inisghttoolkit4 ==
  $ apt install insighttoolkit4-python insighttoolkit4-examples

  Run attached insightoolkit4.py script against an image file, e.g.
  Circle.png from -examples package.

  == libtsm ==

  Nothing in the archive uses this... No idea why we have this package,
  either release the update, or remove it from proposed.

  == mariadb-10.0 ==

  Run mariadb.sh

  == percona-server-5.6 ==

  Run percona.sh

  == percona-xtrabackup ==

  Execute $ xtrabackup --backup; xtracbackup --prepare; xtrabackup
  --backup in a new directory

  == percona-xtradb-cluster-5.6 ==

  Deploy three node percona-cluster charm, upgrade to proposed, check
  that updating tables on one node is reflected on the others.

  == webkitgtk ==

  Open start.ubuntu.com in midori

  == Comment: #0 - Andreas Krebbel - 2016-04-19 

[Group.of.nepali.translators] [Bug 1572613] Re: GCC stack access scheduled after stack deallocation

[Dimitri John Ledkov]

gcc-arm-none-eabi | 15:5.4.1+svn241155-1 | zesty/universe rebuild in
zesty

** Changed in: gcc-arm-none-eabi (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/1572613

Title:
  GCC stack access scheduled after stack deallocation

Status in gcc:
  Unknown
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in ceph package in Ubuntu:
  Fix Released
Status in fpgatools package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-arm-none-eabi package in Ubuntu:
  Fix Released
Status in gcc-avr package in Ubuntu:
  Fix Released
Status in gcc-mingw-w64 package in Ubuntu:
  Fix Released
Status in higan package in Ubuntu:
  Fix Released
Status in insighttoolkit4 package in Ubuntu:
  Fix Released
Status in ivtools package in Ubuntu:
  Fix Released
Status in juju-mongodb3.2 package in Ubuntu:
  Fix Released
Status in libtsm package in Ubuntu:
  Fix Released
Status in mariadb-10.0 package in Ubuntu:
  Fix Released
Status in mysql-5.7 package in Ubuntu:
  Fix Released
Status in nodejs package in Ubuntu:
  Fix Released
Status in percona-server-5.6 package in Ubuntu:
  Fix Released
Status in percona-xtrabackup package in Ubuntu:
  Fix Released
Status in percona-xtradb-cluster-5.6 package in Ubuntu:
  Fix Released
Status in valgrind package in Ubuntu:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in ceph source package in Xenial:
  Fix Released
Status in fpgatools source package in Xenial:
  Fix Released
Status in gambas3 source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in higan source package in Xenial:
  Invalid
Status in insighttoolkit4 source package in Xenial:
  Fix Released
Status in ivtools source package in Xenial:
  Invalid
Status in juju-mongodb3.2 source package in Xenial:
  Fix Released
Status in libtsm source package in Xenial:
  Fix Released
Status in mariadb-10.0 source package in Xenial:
  Fix Released
Status in mysql-5.7 source package in Xenial:
  Fix Released
Status in nodejs source package in Xenial:
  Fix Released
Status in percona-server-5.6 source package in Xenial:
  Fix Released
Status in percona-xtrabackup source package in Xenial:
  Fix Released
Status in percona-xtradb-cluster-5.6 source package in Xenial:
  Fix Released
Status in valgrind source package in Xenial:
  Fix Released
Status in webkitgtk source package in Xenial:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Released
Status in fpgatools source package in Yakkety:
  Fix Released
Status in gambas3 source package in Yakkety:
  Fix Released
Status in gcc-5 source package in Yakkety:
  Fix Released
Status in higan source package in Yakkety:
  Fix Released
Status in insighttoolkit4 source package in Yakkety:
  Fix Released
Status in ivtools source package in Yakkety:
  Fix Released
Status in juju-mongodb3.2 source package in Yakkety:
  Fix Released
Status in libtsm source package in Yakkety:
  Fix Released
Status in mariadb-10.0 source package in Yakkety:
  Fix Released
Status in mysql-5.7 source package in Yakkety:
  Fix Released
Status in nodejs source package in Yakkety:
  Fix Released
Status in percona-server-5.6 source package in Yakkety:
  Fix Released
Status in percona-xtrabackup source package in Yakkety:
  Fix Released
Status in percona-xtradb-cluster-5.6 source package in Yakkety:
  Fix Released
Status in valgrind source package in Yakkety:
  Fix Released
Status in webkitgtk source package in Yakkety:
  Fix Released

Bug description:
  = Validation =
  For gcc-5, check that code generation is correct as per small C test case 
below.

  == fpgatools ==

  * compile autotest.c and strip chrpath
  * change path in autotest_diff.sh from ./ to /usr/bin
  * execute autotest and check error codes

  == gambas3 ==

  * execute gambas.test

  == inisghttoolkit4 ==
  $ apt install insighttoolkit4-python insighttoolkit4-examples

  Run attached insightoolkit4.py script against an image file, e.g.
  Circle.png from -examples package.

  == libtsm ==

  Nothing in the archive uses this... No idea why we have this package,
  either release the update, or remove it from proposed.

  == mariadb-10.0 ==

  Run mariadb.sh

  == percona-server-5.6 ==

  Run percona.sh

  == percona-xtrabackup ==

  Execute $ xtrabackup --backup; xtracbackup --prepare; xtrabackup
  --backup in a new directory

  == percona-xtradb-cluster-5.6 ==

  Deploy three node percona-cluster charm, upgrade to proposed, check
  that updating tables on one node is reflected on the others.

  == webkitgtk ==

  Open start.ubuntu.com in midori

  == Comment: #0 - Andreas Krebbel 

[Group.of.nepali.translators] [Bug 1649821] Re: Boot crash in xen_send_IPI_one

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081443.html

** 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) => Ross Lagerwall (rosslagerwall)

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

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

Title:
  Boot crash in xen_send_IPI_one

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

Bug description:
  Every hundred boots or so when booting Ubuntu 16.04 under Xen, it
  crashes early on boot with the following stack trace:

kernel BUG at 
/build/linux-Ay7j_C/linux-4.4.0/drivers/xen/events/events_base.c:1210!
invalid opcode:  [#1] SMP
...
RIP: 0010:[]  [] 
xen_send_IPI_one+0x59/0x60
...
Call Trace:
 [] xen_qlock_kick+0xe/0x10
 [] __pv_queued_spin_unlock+0xb2/0xf0
 [] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20
 [] ? check_tsc_warp+0x76/0x150
 [] check_tsc_sync_source+0x96/0x160
 [] native_cpu_up+0x3d8/0x9f0
 [] xen_hvm_cpu_up+0x35/0x80
 [] _cpu_up+0x13c/0x180
 [] cpu_up+0x7a/0xa0
 [] smp_init+0x7f/0x81
 [] kernel_init_freeable+0xef/0x212
 [] ? rest_init+0x80/0x80
 [] kernel_init+0xe/0xe0
 [] ret_from_fork+0x3f/0x70
 [] ? rest_init+0x80/0x80

  This is fixed by the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/x86/xen?id=707e59ba494372a90d245f18b0c78982caa88e48

  Unfortunately this wasn't backported to Linux 4.4. Can you please
  include this in the next Ubuntu 16.04 kernel release?

  Thanks
  Ross
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 14 11:48 seq
   crw-rw 1 root audio 116, 33 Dec 14 11:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=637c02d7-6135-4ecc-8273-b014d21cf217
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=6748a82f-b075-401e-ac74-0ebe865003f2 ro console=hvc0 console=tty0
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.7.1-xs131890-d
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.7.1-xs131890-d:bd12/07/2016:svnXen:pnHVMdomU:pvr4.7.1-xs131890-d:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.7.1-xs131890-d
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649821/+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 1620559] Re: /etc/resolv.conf is empty on snappy

[Oliver Grawert]

** Changed in: snappy
   Status: New => Incomplete

** Changed in: snappy
   Status: Incomplete => Fix Released

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=0a96feb1561

  
  Test case:

  I cannot reproduce this in a VM or normal laptop, this is somehow
  specific to the reporter's hardware/DHCP server config.

   * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
   * Reboot.
   * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
   * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.

  Regression potential: Low; in 16.04 LTS we do not configure networkd
  by any Ubuntu tool, so networkd is not widely used there yet. For
  systems which do use it it could happen that interface-specific DNS
  servers now appear in resolv.conf that should not be global -- but we
  do not have anything that would configure or obey this setup in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1620559/+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 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.157.6

---
linux-firmware (1.157.6) xenial; urgency=medium

  * linux-firmware 1.157.5 causes sound issues after initramfs update
(LP: #1645911)
- Revert "linux-firmware: First DMC image for Kabylake."

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

 -- Seth Forshee   Wed, 30 Nov 2016 15:05:05
-0600

** Changed in: linux-firmware (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/1645911

Title:
  linux-firmware 1.157.5 causes sound issues after initramfs update

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  On laptops with Kaby Lake processors and Sunrise point chipsets
  (System76 Lemu7), updating to the current (1.157.5) version of the
  linux-firmware package and then updating initramfs causes sound
  issues.  This can manifest in two ways:

  1: Volume hotkeys and controls appear to work, but actual playback volume 
remains the same.
 Three HDMI devices appear in the sound-settings gui, despite no HDMI 
device connected (and only 1 HDMI port)
  2: 'Dummy Output' is the only device in the sound-settings gui, and there is 
no sound output at all.

  In both cases dmesg shows error output relating to snd_hda_codec_hdmi.

  This bug only affects Xenial, not Yakkety.  Xenial still exhibits the
  above symptoms after installing the current Yakkety linux-firmware
  package.

  I believe the issue is related to the Kaby Lake firmware.  In testing,
  I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run
  'sudo update-initramfs -u', and reboot to get sound working correctly
  again.

  Perhaps this firmware is needed for the upcoming Union Point chipsets,
  but causes problems with the for Kaby Lake processor laptops running
  the 4.4.0 kernel and Sunrise Point chipsets.  There is either a bug in
  the new Kaby Lake firmware or it is being erroneously applied to
  inappropriate hardware.

  I have received a number of reports of users running into this bug,
  presumably anyone who updated to the latest kernel and linux-firmware
  packages at the same time.  Based on testing, next kernel update could
  trigger the bug for many more users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Launchpad Bug Tracker]

This bug was fixed in the package deja-dup - 34.2-0ubuntu1.1

---
deja-dup (34.2-0ubuntu1.1) xenial; urgency=medium

  * debian/patches/clear-cache-before-full-backup.patch:
- Fixes a bug that allowed an incorrect password when making a
  new full backup (LP: #918489)

 -- Michael Terry   Fri, 02 Dec 2016 16:07:55 -0500

** Changed in: deja-dup (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: deja-dup (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/918489

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  Fix Released
Status in deja-dup source package in Xenial:
  Fix Released
Status in deja-dup source package in Yakkety:
  Fix Released

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Launchpad Bug Tracker]

This bug was fixed in the package deja-dup - 30.0-0ubuntu4.1

---
deja-dup (30.0-0ubuntu4.1) trusty; urgency=medium

  * debian/patches/clear-cache-before-full-backup.patch:
 - Fixes a bug that allowed an incorrect password when making a
  new full backup (LP: #918489)

 -- Michael Terry   Thu, 08 Dec 2016 10:01:04 -0500

** Changed in: deja-dup (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/918489

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  Fix Released
Status in deja-dup source package in Xenial:
  Fix Released
Status in deja-dup source package in Yakkety:
  Fix Released

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1646197] Re: Update initrds after installing linux-firmware

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.157.6

---
linux-firmware (1.157.6) xenial; urgency=medium

  * linux-firmware 1.157.5 causes sound issues after initramfs update
(LP: #1645911)
- Revert "linux-firmware: First DMC image for Kabylake."

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

 -- Seth Forshee   Wed, 30 Nov 2016 15:05:05
-0600

** Changed in: linux-firmware (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/1646197

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1646197/+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 1649213] Re: Support rootfs on xhci-plat-hcd attached storage

[Ike Panhc]

initramfs-tools v0.125 or above picks up every hcd.ko for usb. Set to
invalid.

** Changed in: initramfs-tools (Ubuntu Zesty)
   Status: New => Invalid

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

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

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

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

Title:
  Support rootfs on xhci-plat-hcd attached storage

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Trusty:
  New
Status in linux source package in Trusty:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in initramfs-tools source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Invalid

Bug description:
  [Impact]
  If you install Ubuntu onto USB storage behind a Platform USB host controller, 
it will not be able to boot because the generated initramfs will not include 
the host controller driver.

  [Test Case]
  Install to a USB stick attached to platform USB controller and reboot. 
Booting will fail because it will be unable to find the root file system.

  [Regression Risk]
  Driver is only loaded when system requires xhci-plat-hcd, minimizing the 
impact to all other systems.

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