[Group.of.nepali.translators] [Bug 1683825] Re: thermald: fix default preference to ENERGY_CONSERVE
This bug was fixed in the package thermald - 1.5.4-4ubuntu1
---
thermald (1.5.4-4ubuntu1) zesty; urgency=medium
* Add missing support for Kabylake and Broadwell-GT (LP: #1683829)
- upstream commit 405dcc0a6464d92, add some more CPU IDs
* Fix energy preference default (LP: #1683825)
- 37a25879239466f ("set default preference"); set the default
energy preference to ENERGY_CONSERVE rather than a garbage value
-- Colin King Tue, 18 Apr 2017 15:42:01
+0100
** Changed in: thermald (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1683825
Title:
thermald: fix default preference to ENERGY_CONSERVE
Status in thermald package in Ubuntu:
Fix Released
Status in thermald source package in Xenial:
Fix Released
Status in thermald source package in Yakkety:
Fix Released
Status in thermald source package in Zesty:
Fix Released
Bug description:
[SRU][XENIAL][YAKKETY][ZESTY]
Upstream thermald includes a minor fixes that ensure settings are
initialized correctly. The fix in question is:
commit 37a25879239466f2d096fd1a58b2ac7bbc3958f5
Author: Srinivas Pandruvada
Date: Mon Mar 27 17:39:30 2017 -0700
set default preference
In case there is missing element for preference, set ENERGY_CONSERVE
as default.
This fixes are not critical, but I think are proven stable enough for
a SRU and it plugs a *potential* issue that we've not yet seen to
occur.
[REGRESSION POTENTIAL]
Minimal, this ensures a default setting is correctly set to the default value
when config is provided without a default preference. Since this is not the
normal modus operandi of thermald since it uses zero config mode, this fix
plugs a corner case that not used by default. Users of the xml config will be
entering this default appropriately, so this catches the corner cases where it
is not defined in a user config.
[TEST]
This is not testable in the default zero config case. In cases where the
config does not have this default setting, it is hard to test as this is sets
internal state that is not easily checked during run time. As this bug has not
been observed in the field, it is hard to find a reproducer to test this corner
case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1683825/+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 1683825] Re: thermald: fix default preference to ENERGY_CONSERVE
This bug was fixed in the package thermald - 1.5.3-4ubuntu2
---
thermald (1.5.3-4ubuntu2) yakkety; urgency=medium
* Add missing support for Kabylake and Broadwell-GT (LP: #1683829)
- upstream commit 405dcc0a6464d92, add some more CPU IDs
* Fix energy preference default (LP: #1683825)
- 37a25879239466f ("set default preference"); set the default
energy preference to ENERGY_CONSERVE rather than a garbage value
-- Colin King Tue, 18 Apr 2017 15:42:01
+0100
** Changed in: thermald (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** Changed in: thermald (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/1683825
Title:
thermald: fix default preference to ENERGY_CONSERVE
Status in thermald package in Ubuntu:
Fix Released
Status in thermald source package in Xenial:
Fix Released
Status in thermald source package in Yakkety:
Fix Released
Status in thermald source package in Zesty:
Fix Released
Bug description:
[SRU][XENIAL][YAKKETY][ZESTY]
Upstream thermald includes a minor fixes that ensure settings are
initialized correctly. The fix in question is:
commit 37a25879239466f2d096fd1a58b2ac7bbc3958f5
Author: Srinivas Pandruvada
Date: Mon Mar 27 17:39:30 2017 -0700
set default preference
In case there is missing element for preference, set ENERGY_CONSERVE
as default.
This fixes are not critical, but I think are proven stable enough for
a SRU and it plugs a *potential* issue that we've not yet seen to
occur.
[REGRESSION POTENTIAL]
Minimal, this ensures a default setting is correctly set to the default value
when config is provided without a default preference. Since this is not the
normal modus operandi of thermald since it uses zero config mode, this fix
plugs a corner case that not used by default. Users of the xml config will be
entering this default appropriately, so this catches the corner cases where it
is not defined in a user config.
[TEST]
This is not testable in the default zero config case. In cases where the
config does not have this default setting, it is hard to test as this is sets
internal state that is not easily checked during run time. As this bug has not
been observed in the field, it is hard to find a reproducer to test this corner
case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1683825/+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 1683829] Re: thermald: Add support for Kabylake and Broadwell-GT processor models
This bug was fixed in the package thermald - 1.5.4-4ubuntu1
---
thermald (1.5.4-4ubuntu1) zesty; urgency=medium
* Add missing support for Kabylake and Broadwell-GT (LP: #1683829)
- upstream commit 405dcc0a6464d92, add some more CPU IDs
* Fix energy preference default (LP: #1683825)
- 37a25879239466f ("set default preference"); set the default
energy preference to ENERGY_CONSERVE rather than a garbage value
-- Colin King Tue, 18 Apr 2017 15:42:01
+0100
** Changed in: thermald (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1683829
Title:
thermald: Add support for Kabylake and Broadwell-GT processor models
Status in thermald package in Ubuntu:
Fix Released
Status in thermald source package in Xenial:
Fix Released
Status in thermald source package in Yakkety:
Fix Released
Status in thermald source package in Zesty:
Fix Released
Bug description:
[SRU][XENIAL][YAKKETY][ZESTY]
Newer x86 processor families are supported with thermald upstream
commit 405dcc0a6464d92e656789a5a76bb23f479975ea ("Add Kabylake and
Broadwell-GT processor models"). It makes sense to add these CPU IDs
to supported versions of thermald.
[REGRESSION POTENTIAL]
This fix adds new CPU IDs to the table of supported processors. This fix has
the potential of only changing behaviour of CPUs that have been added to the
list. The regression potential for existing CPUs is close to zero as this is a
table driven check.
[TESTCASE]
Modern CPUs with IDs will be supported with this fix:
6, 0x47 (Broadwell-GT3E)
6, 0x8e (Kabylake)
6, 0x9e (Kabylake)
..so thermald should be able to now detect this with the fix. Without
the rix, the thermald log will report "Need Linux PowerCap sysfs",
with the fix, this message will not be shown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1683829/+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 1683829] Re: thermald: Add support for Kabylake and Broadwell-GT processor models
This bug was fixed in the package thermald - 1.5.3-4ubuntu2
---
thermald (1.5.3-4ubuntu2) yakkety; urgency=medium
* Add missing support for Kabylake and Broadwell-GT (LP: #1683829)
- upstream commit 405dcc0a6464d92, add some more CPU IDs
* Fix energy preference default (LP: #1683825)
- 37a25879239466f ("set default preference"); set the default
energy preference to ENERGY_CONSERVE rather than a garbage value
-- Colin King Tue, 18 Apr 2017 15:42:01
+0100
** Changed in: thermald (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** Changed in: thermald (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/1683829
Title:
thermald: Add support for Kabylake and Broadwell-GT processor models
Status in thermald package in Ubuntu:
Fix Released
Status in thermald source package in Xenial:
Fix Released
Status in thermald source package in Yakkety:
Fix Released
Status in thermald source package in Zesty:
Fix Released
Bug description:
[SRU][XENIAL][YAKKETY][ZESTY]
Newer x86 processor families are supported with thermald upstream
commit 405dcc0a6464d92e656789a5a76bb23f479975ea ("Add Kabylake and
Broadwell-GT processor models"). It makes sense to add these CPU IDs
to supported versions of thermald.
[REGRESSION POTENTIAL]
This fix adds new CPU IDs to the table of supported processors. This fix has
the potential of only changing behaviour of CPUs that have been added to the
list. The regression potential for existing CPUs is close to zero as this is a
table driven check.
[TESTCASE]
Modern CPUs with IDs will be supported with this fix:
6, 0x47 (Broadwell-GT3E)
6, 0x8e (Kabylake)
6, 0x9e (Kabylake)
..so thermald should be able to now detect this with the fix. Without
the rix, the thermald log will report "Need Linux PowerCap sysfs",
with the fix, this message will not be shown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1683829/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
** No longer affects: mesa (Ubuntu Xenial) ** No longer affects: mesa (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/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Released Status in System76: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note: "Download updates while installing Ubuntu" doesn't currently seem to be working. If after installing 16.04 on effected Skylake hardware you find that Unity/Compiz is broken, switch to a VT with Control+Alt+F1, login, and then run: sudo apt-get update sudo apt-get dist-upgrade You should see the `libllvm3.8` package get updated. After a reboot, Unity/Compiz should be working. == In detail == The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1682160] Re: update-grub-legacy-ec2 fails if no /etc/fstab causing install or upgrade fail
This bug was fixed in the package cloud-init - 0.7.9-113-g513e99e0-0ubuntu1 --- cloud-init (0.7.9-113-g513e99e0-0ubuntu1) artful; urgency=medium * New upstream snapshot. - nova-lxd: read product_name from environment, not platform. (LP: #1685810) - Fix yum repo config where keys contain array values [Dylan Perry] (LP: #1592150) - template: Update debian backports template [Joshua Powers] (LP: #1627293) - rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899) - Doc: add additional RTD examples [Joshua Powers] (LP: #1459604) - Fix growpart for some cases when booted with root=PARTUUID. (LP: #1684869) - pylint: update output style to parseable [Joshua Powers] - pylint: fix all logging warnings [Joshua Powers] - CloudStack: Add NetworkManager to list of supported DHCP lease dirs. [Syed Mushtaq Ahmed] - net: kernel lies about vlans not stealing mac addresses, when they do [Dimitri John Ledkov] (LP: #1682871) - ds-identify: Check correct path for "latest" config drive [Daniel Watkins] (LP: #1673637) - doc: Fix example for resolve.conf configuration. [Jon Grimm] (LP: #1531582) - Fix examples that reference upstream chef repository. [Jon Grimm] (LP: #1678145) - doc: correct grammar and improve clarity in merging documentation. [David Tagatac] - doc: Add missing doc link to snap-config module. [Ryan Harper] - snap: allows for creating cloud-init snap [Joshua Powers] - DigitalOcean: assign IPv4ll address to lowest indexed interface. [Ben Howard] - DigitalOcean: configure all NICs presented in meta-data. [Ben Howard] - Remove (and/or fix) URL shortener references [Jon Grimm] (LP: #1669727) - HACKING.rst: more info on filling out contributors agreement. [Scott Moser] - util: teach write_file about copy_mode option [Lars Kellogg-Stedman] (LP: #1644064) - DigitalOcean: bind resolvers to loopback interface. [Ben Howard] - tests: fix AltCloud tests to not rely on blkid (LP: #1636531) -- Scott Moser Tue, 25 Apr 2017 16:34:08 -0400 ** Changed in: cloud-init (Ubuntu) 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/1682160 Title: update-grub-legacy-ec2 fails if no /etc/fstab causing install or upgrade fail Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Fix Committed Bug description: While not common, and probably not desirable, if /etc/fstab is not present, update-grub-legacy-ec2 will fail. Thus, if you don't have an /etc/fstab, an install of a kernel package will run /etc/kernel/postinst.d/x-grub-legacy-ec2 and thus fail install. recreate: % sudo mv /etc/fstab /etc/fstab.orig % sudo dpkg-reconfigure grub-legacy-ec2 Searching for GRUB installation directory ... found: /boot/grub Cannot determine root device. Assuming /dev/hda1 This error is probably caused by an invalid /etc/fstab awk: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: grub-legacy-ec2 0.7.9-90-g61eb03fe-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Apr 12 15:05:56 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1682160/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4
This bug was fixed in the package cloud-init - 0.7.9-113-g513e99e0-0ubuntu1 --- cloud-init (0.7.9-113-g513e99e0-0ubuntu1) artful; urgency=medium * New upstream snapshot. - nova-lxd: read product_name from environment, not platform. (LP: #1685810) - Fix yum repo config where keys contain array values [Dylan Perry] (LP: #1592150) - template: Update debian backports template [Joshua Powers] (LP: #1627293) - rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899) - Doc: add additional RTD examples [Joshua Powers] (LP: #1459604) - Fix growpart for some cases when booted with root=PARTUUID. (LP: #1684869) - pylint: update output style to parseable [Joshua Powers] - pylint: fix all logging warnings [Joshua Powers] - CloudStack: Add NetworkManager to list of supported DHCP lease dirs. [Syed Mushtaq Ahmed] - net: kernel lies about vlans not stealing mac addresses, when they do [Dimitri John Ledkov] (LP: #1682871) - ds-identify: Check correct path for "latest" config drive [Daniel Watkins] (LP: #1673637) - doc: Fix example for resolve.conf configuration. [Jon Grimm] (LP: #1531582) - Fix examples that reference upstream chef repository. [Jon Grimm] (LP: #1678145) - doc: correct grammar and improve clarity in merging documentation. [David Tagatac] - doc: Add missing doc link to snap-config module. [Ryan Harper] - snap: allows for creating cloud-init snap [Joshua Powers] - DigitalOcean: assign IPv4ll address to lowest indexed interface. [Ben Howard] - DigitalOcean: configure all NICs presented in meta-data. [Ben Howard] - Remove (and/or fix) URL shortener references [Jon Grimm] (LP: #1669727) - HACKING.rst: more info on filling out contributors agreement. [Scott Moser] - util: teach write_file about copy_mode option [Lars Kellogg-Stedman] (LP: #1644064) - DigitalOcean: bind resolvers to loopback interface. [Ben Howard] - tests: fix AltCloud tests to not rely on blkid (LP: #1636531) -- Scott Moser Tue, 25 Apr 2017 16:34:08 -0400 ** Changed in: cloud-init (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/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in linux source package in Xenial: Triaged Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions ___
[Group.of.nepali.translators] [Bug 1685810] Re: nova-lxd needs to read 'product_name' in environment, not 'platform'
This bug was fixed in the package cloud-init - 0.7.9-113-g513e99e0-0ubuntu1 --- cloud-init (0.7.9-113-g513e99e0-0ubuntu1) artful; urgency=medium * New upstream snapshot. - nova-lxd: read product_name from environment, not platform. (LP: #1685810) - Fix yum repo config where keys contain array values [Dylan Perry] (LP: #1592150) - template: Update debian backports template [Joshua Powers] (LP: #1627293) - rsyslog: replace ~ with stop [Joshua Powers] (LP: #1367899) - Doc: add additional RTD examples [Joshua Powers] (LP: #1459604) - Fix growpart for some cases when booted with root=PARTUUID. (LP: #1684869) - pylint: update output style to parseable [Joshua Powers] - pylint: fix all logging warnings [Joshua Powers] - CloudStack: Add NetworkManager to list of supported DHCP lease dirs. [Syed Mushtaq Ahmed] - net: kernel lies about vlans not stealing mac addresses, when they do [Dimitri John Ledkov] (LP: #1682871) - ds-identify: Check correct path for "latest" config drive [Daniel Watkins] (LP: #1673637) - doc: Fix example for resolve.conf configuration. [Jon Grimm] (LP: #1531582) - Fix examples that reference upstream chef repository. [Jon Grimm] (LP: #1678145) - doc: correct grammar and improve clarity in merging documentation. [David Tagatac] - doc: Add missing doc link to snap-config module. [Ryan Harper] - snap: allows for creating cloud-init snap [Joshua Powers] - DigitalOcean: assign IPv4ll address to lowest indexed interface. [Ben Howard] - DigitalOcean: configure all NICs presented in meta-data. [Ben Howard] - Remove (and/or fix) URL shortener references [Jon Grimm] (LP: #1669727) - HACKING.rst: more info on filling out contributors agreement. [Scott Moser] - util: teach write_file about copy_mode option [Lars Kellogg-Stedman] (LP: #1644064) - DigitalOcean: bind resolvers to loopback interface. [Ben Howard] - tests: fix AltCloud tests to not rely on blkid (LP: #1636531) -- Scott Moser Tue, 25 Apr 2017 16:34:08 -0400 ** Changed in: cloud-init (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/1685810 Title: nova-lxd needs to read 'product_name' in environment, not 'platform' Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Bug description: It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs: * bug 1661797: identify lxd-nova platform to enable Openstack datasource To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685810/+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 1615482] Re: apt-daily timer runs at random hours of the day
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apt (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => High ** Changed in: apt (Ubuntu Xenial) Status: New => In Progress ** Changed in: apt (Ubuntu Yakkety) Status: New => In Progress ** Changed in: apt (Ubuntu Zesty) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Yakkety: In Progress Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Low -- 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/1672710 Title: apt fails to verify keys when Dir has space, and set via cmdline Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Bug description: When Dir has a space, and it is set via APT_CONFIG file, keys are found and validated correctly. When Dir is set without a space via cmdline, keys are found and validated correctly. When Dir is set with a space via cmdline, keys are not found and repositories are not verified. [Test case] Please see attached reproducer, which works on xenial system (gpg1) but not on zesty system (gpg2) $ bash reproducer.sh ++ mktemp -d + tmpdir=/tmp/tmp.sFipy6h5yL + pushd /tmp/tmp.sFipy6h5yL /tmp/tmp.sFipy6h5yL ~ + mkdir 'Sub Dir' + pushd 'Sub Dir' /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~ + mkdir -p etc/apt/apt.conf.d + mkdir -p etc/apt/trusted.gpg.d + mkdir -p etc/apt/preferences.d + mkdir -p var/lib/apt/lists/partial + mkdir -p var/lib/dpkg + touch var/lib/dpkg/status + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg etc/apt/trusted.gpg.d/ + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main' + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";' + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + cat /tmp/tmp.sFipy6h5yL/apt.conf Dir "/tmp/tmp.sFipy6h5yL/Sub Dir"; + : + : == list available keys == + apt-key list /tmp/tmp.sFipy6h5yL/Sub Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg - pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) + : + : == update with environ APT_CONFIG setting the Dir variable == + apt update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB] Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B] Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB] Fetched 1,410 kB in 0s (1,959 kB/s) Reading package lists... Done Building dependency tree... Done All packages are up to date. + unset APT_CONFIG + : + : == update with cmdline Dir option setting Dir to relative pwd == + apt -o Dir=./ update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Reading package lists... Done Building dependency tree... Done All packages are up to date. + : + : == update with cmdline Dir option setting Dir to absolute pwd with space == + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Reading package lists... Done Building dependency tree... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download. They have been ignored, or old ones used instead. [Regression Potential] The fix changes the code to generate quotes in the Commmandline:AsString option, which dumps the command line for logging purposes. This was not parseable before, causing the file to be rejected, so what can happen is that something now works that did not before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1672710/+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 1685860] Re: linux: 4.4.0-76.97 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Kleber Sacilotto de Souza (kleber-souza) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1685860 Title: linux: 4.4.0-76.97 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-76.97 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 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1685860/+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 1611816] Re: pam_cifscreds.so not supplied in package
This bug was fixed in the package cifs-utils - 2:6.4-1ubuntu1.1 --- cifs-utils (2:6.4-1ubuntu1.1) xenial; urgency=low * Add pam_cifscreds (LP: #1611816). Patch by David McBride. -- Keith Ward Tue, 28 Feb 2017 14:01:32 -0800 ** Changed in: cifs-utils (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/1611816 Title: pam_cifscreds.so not supplied in package Status in cifs-utils package in Ubuntu: Fix Released Status in cifs-utils source package in Xenial: Fix Released Status in cifs-utils source package in Yakkety: Fix Released Status in cifs-utils source package in Zesty: Fix Released Status in cifs-utils package in Debian: Fix Released Bug description: The cifs-utils source package contains the pam_cifscreds.so PAM module; however, this is not built and supplied in a resulting binary package. This is necessary functionality for our local managed deployment. We have worked around this issue by building our own patched version of the package; however, this is liable to be clobbered by any future upstream updates. Hence, it would be valuable if our modifications, or some variant of them, could be adopted upstream. The changes required are minimal; simply add libpam0g-dev to Build- Depends, and add some appropriate flags to ./configure in debian/rules to ensure the requisite library is built and installed in the correct location. See attached patch. ## SRU Justification [Impact] As David has found, users are currently unable to use the cifscreds PAM module to unlock credentials at login because existing package doesn't compile the module along with the rest of the package. Davids patch adds libpam-0g-dev to the Build depends, and amends the debian rules file so that the PAM module is built along with the rest of the application and installed into the correct location. I'm requesting this to be backported to the existing releases, this change is a feature which is highly desired in managed deployments, the changes are minimal and as this patch only adds functionality and is largely unobtrusive I see no reason for the Ubuntu community to benefit from its inclusion considering the regression potential is minimal. This feature has been added to Zesty already as part of the merge done in LP: #1660372. [Test Case] Install the package and check for the existance of the PAM module at: /lib/x86_64-linux-gnu/security/pam_cifscreds.so At present this file is missing as it isn't compiled along with the rest of the package. [Regression Potential] I've been testing this myself on a number of systems and have discovered no issues as yet, with this patch the supplied module is built and placed into the correct location, as is the manpage, and both perform as intended. This change has an overall low chance of regression as it's only adding functionality should already be there. The only regression I could think of is that for some reason the patch could result in some of the other binaries being linked against PAM (and potentially have their behavior changed) as a result of the addition of PAM, but I find this extremely unlikely, and I have verified that PAM isn't linked to except for pam_cifscreds.so so I find the possibility of this happening negligible. Documentation for the feature is provided as a manpage and is distributed along with the updated package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+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 1611816] Re: pam_cifscreds.so not supplied in package
This bug was fixed in the package cifs-utils - 2:6.5-2ubuntu2 --- cifs-utils (2:6.5-2ubuntu2) yakkety; urgency=low * Add pam_cifscreds (LP: #1611816). Patch by David McBride. -- Keith Ward Tue, 28 Feb 2017 13:58:35 -0800 ** Changed in: cifs-utils (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/1611816 Title: pam_cifscreds.so not supplied in package Status in cifs-utils package in Ubuntu: Fix Released Status in cifs-utils source package in Xenial: Fix Released Status in cifs-utils source package in Yakkety: Fix Released Status in cifs-utils source package in Zesty: Fix Released Status in cifs-utils package in Debian: Fix Released Bug description: The cifs-utils source package contains the pam_cifscreds.so PAM module; however, this is not built and supplied in a resulting binary package. This is necessary functionality for our local managed deployment. We have worked around this issue by building our own patched version of the package; however, this is liable to be clobbered by any future upstream updates. Hence, it would be valuable if our modifications, or some variant of them, could be adopted upstream. The changes required are minimal; simply add libpam0g-dev to Build- Depends, and add some appropriate flags to ./configure in debian/rules to ensure the requisite library is built and installed in the correct location. See attached patch. ## SRU Justification [Impact] As David has found, users are currently unable to use the cifscreds PAM module to unlock credentials at login because existing package doesn't compile the module along with the rest of the package. Davids patch adds libpam-0g-dev to the Build depends, and amends the debian rules file so that the PAM module is built along with the rest of the application and installed into the correct location. I'm requesting this to be backported to the existing releases, this change is a feature which is highly desired in managed deployments, the changes are minimal and as this patch only adds functionality and is largely unobtrusive I see no reason for the Ubuntu community to benefit from its inclusion considering the regression potential is minimal. This feature has been added to Zesty already as part of the merge done in LP: #1660372. [Test Case] Install the package and check for the existance of the PAM module at: /lib/x86_64-linux-gnu/security/pam_cifscreds.so At present this file is missing as it isn't compiled along with the rest of the package. [Regression Potential] I've been testing this myself on a number of systems and have discovered no issues as yet, with this patch the supplied module is built and placed into the correct location, as is the manpage, and both perform as intended. This change has an overall low chance of regression as it's only adding functionality should already be there. The only regression I could think of is that for some reason the patch could result in some of the other binaries being linked against PAM (and potentially have their behavior changed) as a result of the addition of PAM, but I find this extremely unlikely, and I have verified that PAM isn't linked to except for pam_cifscreds.so so I find the possibility of this happening negligible. Documentation for the feature is provided as a manpage and is distributed along with the updated package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+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 1685860] Re: linux: 4.4.0-77.98 -proposed tracker
** Summary changed: - linux: 4.4.0-76.97 -proposed tracker + linux: 4.4.0-77.98 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1685860 Title: linux: 4.4.0-77.98 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-76.97 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 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1685860/+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 1645815] Re: apt install of local debs does not tab-complete
This bug was fixed in the package apt - 1.2.20
---
apt (1.2.20) xenial; urgency=medium
* Microrelease covering fixes of 1.4~rc2 (LP: #1668285)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
-- Julian Andres Klode Mon, 27 Feb 2017 15:29:18
+0100
** Changed in: apt (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/1645815
Title:
apt install of local debs does not tab-complete
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Yakkety:
Fix Released
Bug description:
[Impact]
Previously apt's bash completion was such that, given
$ mkdir xyzzz
$ touch xyzzy.deb xyzzx.two.deb
you'd get
$ apt install xyzz
xyzzx.two.deb xyzzz/
$ apt install /tmp/foo/xyzz
xyzzx.two.deb xyzzz/
this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but
worse than that it offered things that apt would not actually
recognise as candidates for install:
$ sudo apt install xyzzx.two.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xyzzx.two.deb
E: Couldn't find any package by glob 'xyzzx.two.deb'
E: Couldn't find any package by regex 'xyzzx.two.deb'
[Test case]
With this small (trival, really) change, apt's bash completion should
only offer things apt understands, and won't recquire an aditional
period in the filename to offer it:
$ apt install xyzz^C
$ # (no completions!)
$ apt install ./xyzz
xyzzx.two.deb xyzzy.deb xyzzz/
$ apt install /tmp/foo/xyzz
xyzzx.two.deb xyzzy.deb xyzzz/
[Regression potential]
Only the expansion of filenames in the completion is affected:
-_filedir "*.deb"
+if [[ "$cur" == ./* || "$cur" == /* ]]; then
+_filedir "deb"
+fi
so it's unlikely to introduce any regression.
[Original bug report]
this fails:
$ touch xyzzy.deb
$ apt install xyzzy
because the completion support for install is using _filedir wrong.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.15
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 29 17:51:57 2016
InstallationDate: Installed on 2016-07-05 (147 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1645815/+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 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
This bug was fixed in the package apt - 1.2.20
---
apt (1.2.20) xenial; urgency=medium
* Microrelease covering fixes of 1.4~rc2 (LP: #1668285)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
-- Julian Andres Klode Mon, 27 Feb 2017 15:29:18
+0100
** Changed in: apt (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/1657567
Title:
"Content-Range: */" on non-416 responses considered invalid
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Yakkety:
Fix Released
Bug description:
APT only allows Content-Range: */ to be specified on a 416
response. Sourceforge sometimes replies with that in a 302 redirect.
We should probably just accept and silently ignore that content-range
field for other values.
[Impact]
Issue breaks and other services that respond with a Content-Range header in a
302 redirect, or any non 416 one.
[Test Case]
Run
/usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
http://www.jak-software.de/lp1657567 ubuntu.iso
Before:
E: Failed to fetch http://www.jak-software.de/lp1657567 The HTTP
server sent an invalid Content-Range header Bad header data
After:
Redirect is followed successfully and a zesty live image is being
downloaded.
[Regression Potential]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+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 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated
This bug was fixed in the package apt - 1.2.20
---
apt (1.2.20) xenial; urgency=medium
* Microrelease covering fixes of 1.4~rc2 (LP: #1668285)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
-- Julian Andres Klode Mon, 27 Feb 2017 15:29:18
+0100
** Changed in: apt (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/1657440
Title:
apt won't redownload Release.gpg after inconsistent cache updates made
while UCA is being updated
Status in APT:
Fix Released
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Yakkety:
Fix Released
Bug description:
# apt --version
apt 1.2.18 (amd64)
xenial
I got myself into a situation where a repository has a Release and a
Release.gpg file, but apt is just ignoring the gpg one and won't
download it via apt update for some reason:
The repository in question is http://ubuntu-
cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
how locally I have just the Release file:
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
-rw-r--r-- 1 root root 100K Jan 15 18:03
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
-rw-r--r-- 1 root root 242K Apr 21 2016
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
-rw-r--r-- 1 root root 100K Jan 18 11:42
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
-rw-r--r-- 1 root root 100K Jan 18 11:42
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
-rw-r--r-- 1 root root 7.7K Jan 18 11:45
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a
"Get:":
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
InRelease
Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
Release
Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
Release.gpg [543 B]
Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 205 kB in 0s (395 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
And I can't install packages:
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
python3-setuptools
The following packages will be upgraded:
dh-python dnsmasq-base python-pkg-resources python-setuptools
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,193 kB of archives.
After this operation, 808 kB of additional disk space will be used.
Do you want to continue? [Y/n]
WARNING: The following packages cannot be authenticated!
dh-python dnsmasq-base python-setuptools python-pkg-resources
python3-pkg-resources python3-setuptools python3-cryptography python3-requests
python3-urllib3
Install these
[Group.of.nepali.translators] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20
This bug was fixed in the package apt - 1.2.20
---
apt (1.2.20) xenial; urgency=medium
* Microrelease covering fixes of 1.4~rc2 (LP: #1668285)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
-- Julian Andres Klode Mon, 27 Feb 2017 15:29:18
+0100
** Changed in: apt (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/1668285
Title:
[SRU] Update apt/xenial to 1.2.20
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Bug description:
[Impact]
Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a
far saner amount of changes than in 1.3.5, because we don't have the
installation ordering changes as the new installation ordering was introduced
in 1.3.
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes:
#850759)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
[Test case]
Mentioned launchpad bugs have their own test case sections. The rest is
checked in the CI, so we should just do some updates upgrades and check that
everything works.
[Regression Potential]
In #1668280, about 80% of the code changes are covered by test cases. This
leaves out most code changes that are not covered, so code coverage should be
higher, reducing the regression potential enormously.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1668285/+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 1645815] Re: apt install of local debs does not tab-complete
This bug was fixed in the package apt - 1.3.5
---
apt (1.3.5) yakkety; urgency=medium
* Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* react to trig-pend only if we have nothing else to do
* correct cross & disappear progress detection
* improve arch-unqualified dpkg-progress parsing
* don't perform implicit crossgrades involving M-A:same
* do not configure unconfigured to be removed packages
* skip unconfigure for unconfigured to-be removed pkgs
* get pdiff files from the same mirror as the index
* let {dsc,tar,diff}-only implicitly enable download-only
* ensure generation of valid EDSP error stanzas
* fix minimum pkgs option for dpkg --recursive usage
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* fix 'install --no-download' mode
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Edgar Fuß ]
* http: clear content before reporting the failure (Closes: #465572)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
* CMake: Install statvfs.h to include/sys, not just include/
-- Julian Andres Klode Mon, 27 Feb 2017 15:02:40
+0100
** Changed in: apt (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/1645815
Title:
apt install of local debs does not tab-complete
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Yakkety:
Fix Released
Bug description:
[Impact]
Previously apt's bash completion was such that, given
$ mkdir xyzzz
$ touch xyzzy.deb xyzzx.two.deb
you'd get
$ apt install xyzz
xyzzx.two.deb xyzzz/
$ apt install /tmp/foo/xyzz
xyzzx.two.deb xyzzz/
this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but
worse than that it offered things that apt would not actually
recognise as candidates for install:
$ sudo apt install xyzzx.two.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xyzzx.two.deb
E: Couldn't find any package by glob 'xyzzx.two.deb'
E: Couldn't find any package by regex 'xyzzx.two.deb'
[Test case]
With this small (trival, really) change, apt's bash completion should
only offer things apt understands, and won't recquire an aditional
period in the filename to offer it:
$ apt install xyzz^C
$ # (no completions!)
$ apt install ./xyzz
xyzzx.two.deb xyzzy.deb xyzzz/
$ apt install /tmp/foo/xyzz
xyzzx.two.deb xyzzy.deb xyzzz/
[Regression potential]
Only the expansion of filenames in the completion is affected:
-_filedir "*.deb"
+if [[ "$cur" == ./* || "$cur" == /* ]]; then
+_filedir "deb"
+fi
so it's unlikely to introduce any regression.
[Original bug report]
this fails:
$ touch xyzzy.deb
$ apt install xyzzy
because the completion support for install is using _filedir wrong.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.15
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 29 17:51:57 2016
InstallationDate: Installed on 2016-07-05 (147 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
[Group.of.nepali.translators] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated
This bug was fixed in the package apt - 1.3.5
---
apt (1.3.5) yakkety; urgency=medium
* Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* react to trig-pend only if we have nothing else to do
* correct cross & disappear progress detection
* improve arch-unqualified dpkg-progress parsing
* don't perform implicit crossgrades involving M-A:same
* do not configure unconfigured to be removed packages
* skip unconfigure for unconfigured to-be removed pkgs
* get pdiff files from the same mirror as the index
* let {dsc,tar,diff}-only implicitly enable download-only
* ensure generation of valid EDSP error stanzas
* fix minimum pkgs option for dpkg --recursive usage
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* fix 'install --no-download' mode
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Edgar Fuß ]
* http: clear content before reporting the failure (Closes: #465572)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
* CMake: Install statvfs.h to include/sys, not just include/
-- Julian Andres Klode Mon, 27 Feb 2017 15:02:40
+0100
** Changed in: apt (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/1657440
Title:
apt won't redownload Release.gpg after inconsistent cache updates made
while UCA is being updated
Status in APT:
Fix Released
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Yakkety:
Fix Released
Bug description:
# apt --version
apt 1.2.18 (amd64)
xenial
I got myself into a situation where a repository has a Release and a
Release.gpg file, but apt is just ignoring the gpg one and won't
download it via apt update for some reason:
The repository in question is http://ubuntu-
cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
how locally I have just the Release file:
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
-rw-r--r-- 1 root root 100K Jan 15 18:03
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
-rw-r--r-- 1 root root 242K Apr 21 2016
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
-rw-r--r-- 1 root root 100K Jan 18 11:42
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
-rw-r--r-- 1 root root 100K Jan 18 11:42
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
-rw-r--r-- 1 root root 7.7K Jan 18 11:45
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a
"Get:":
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
InRelease
Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
Release
Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton
Release.gpg [543 B]
Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 205 kB in 0s (395 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
And I can't install packages:
root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The follo
[Group.of.nepali.translators] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
This bug was fixed in the package apt - 1.3.5
---
apt (1.3.5) yakkety; urgency=medium
* Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)
[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* react to trig-pend only if we have nothing else to do
* correct cross & disappear progress detection
* improve arch-unqualified dpkg-progress parsing
* don't perform implicit crossgrades involving M-A:same
* do not configure unconfigured to be removed packages
* skip unconfigure for unconfigured to-be removed pkgs
* get pdiff files from the same mirror as the index
* let {dsc,tar,diff}-only implicitly enable download-only
* ensure generation of valid EDSP error stanzas
* fix minimum pkgs option for dpkg --recursive usage
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* fix 'install --no-download' mode
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: #850759)
[ Edgar Fuß ]
* http: clear content before reporting the failure (Closes: #465572)
[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
* CMake: Install statvfs.h to include/sys, not just include/
-- Julian Andres Klode Mon, 27 Feb 2017 15:02:40
+0100
** Changed in: apt (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/1657567
Title:
"Content-Range: */" on non-416 responses considered invalid
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Yakkety:
Fix Released
Bug description:
APT only allows Content-Range: */ to be specified on a 416
response. Sourceforge sometimes replies with that in a 302 redirect.
We should probably just accept and silently ignore that content-range
field for other values.
[Impact]
Issue breaks and other services that respond with a Content-Range header in a
302 redirect, or any non 416 one.
[Test Case]
Run
/usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
http://www.jak-software.de/lp1657567 ubuntu.iso
Before:
E: Failed to fetch http://www.jak-software.de/lp1657567 The HTTP
server sent an invalid Content-Range header Bad header data
After:
Redirect is followed successfully and a zesty live image is being
downloaded.
[Regression Potential]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+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 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
** Also affects: linux (Ubuntu Artful) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1684971 Title: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: The following patch fixes a problem with "[PATCH] pci-hyperv: Use device serial number as PCI domain" where some drivers were expecting a u16 instead of a u32 for PCI device serial numbers, as observed by Oops and hangs in Azure on NC and NV GPU instances. From: Haiyang Zhang This patch uses the lower 16 bits of the serial number as PCI domain, otherwise some drivers may not be able to handle it. Signed-off-by: Haiyang Zhang --- drivers/pci/host/pci-hyperv.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c index e73880c..b18dff3 100644 --- a/drivers/pci/host/pci-hyperv.c +++ b/drivers/pci/host/pci-hyperv.c @@ -1334,9 +1334,11 @@ static void put_pcichild(struct hv_pci_dev *hpdev, * can have shorter names than based on the bus instance UUID. * Only the first device serial number is used for domain, so the * domain number will not change after the first device is added. + * The lower 16 bits of the serial number is used, otherwise some + * drivers may not be able to handle it. */ if (list_empty(&hbus->children)) - hbus->sysdata.domain = desc->ser; + hbus->sysdata.domain = desc->ser & 0x; list_add_tail(&hpdev->list_entry, &hbus->children); spin_unlock_irqrestore(&hbus->device_list_lock, flags); return hpdev; -- 1.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684971/+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 1562002] Re: Nautilus: lag after choosing action in top right menu
This bug was fixed in the package gtk+3.0 - 3.18.9-1ubuntu3.3 --- gtk+3.0 (3.18.9-1ubuntu3.3) xenial; urgency=medium * Backport upstream patch to fix lagging and visual issues in Nautilus (toggled-not-clicked.patch, LP: #1562002). -- Dmitry Shachnev Thu, 23 Mar 2017 22:44:18 +0300 ** Changed in: gtk+3.0 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1562002 Title: Nautilus: lag after choosing action in top right menu Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: Fix Released Bug description: # Impact This is known to affect Nautilus, but can potentially affect other applications too (the upstream bug has an example test app attached). See also the duplicate bug 1644393, which is another appearance of the same bug but with other symptoms. # Proposed Fix The proposed fix is an upstream commit taken from gtk-3-20 branch: https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1 # Test Case https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case. # Regression Potential The bug is fixed in GTK+ 3.20.9, so the fix was already present in the version that shipped with Yakkety. I am not aware of any regressions. - choosing action like New Tab, New Folder, Select Items Matching, will make nautilus lag (unresponsive) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 25 20:52:21 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+685+36'" InstallationDate: Installed on 2016-03-24 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1562002/+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 1664312] Re: Update ENA driver to 1.1.2 from net-next
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Zesty) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu Zesty) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1664312 Title: Update ENA driver to 1.1.2 from net-next Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: New Bug description: "net/ena 1.1.2 changeset" recently merged into linux/net-next: http://marc.info/?l=linux-netdev&m=148664692122357&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664312/+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 1610878] Re: pmp-check-unix-memory stopped working because of new output from free
This bug was fixed in the package nagios-plugins-contrib - 16.20151226ubuntu0.16.04.1 --- nagios-plugins-contrib (16.20151226ubuntu0.16.04.1) xenial; urgency=medium * pmp-check-unix-memory: Consider MemAvailable if available in /proc/meminfo. (LP: #1610878) -- Christian Biamont Tue, 28 Feb 2017 10:18:11 -0800 ** Changed in: nagios-plugins-contrib (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/1610878 Title: pmp-check-unix-memory stopped working because of new output from free Status in nagios-plugins-contrib package in Ubuntu: Fix Released Status in nagios-plugins-contrib source package in Xenial: Fix Released Status in nagios-plugins-contrib source package in Yakkety: Fix Committed Status in nagios-plugins-contrib source package in Zesty: Fix Released Bug description: Hello, Current pmp-check-unix-memory in package nagios-plugins-contrib does not work anymore, from Ubuntu Xenial. It can't fetch free memory and therefor presents it incorrectly. E.g: $ ./pmp-check-unix-memory OK Memory % used | memory_used=0;90;95;0;100 As of version 3.3.10 of package procps, the command "free" uses a different output. See: http://upstream.rosalinux.ru/changelogs/procps- ng/3.3.10/changelog.html How free memory is calculated was changed in kernel here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=34e431b0ae398fc54ea69ff85ec700722c9da773 This problem has been fixed in the percona-monitoring-plugins repo on GitHub: https://github.com/percona/percona-monitoring- plugins/commit/b4636c49f0188d2af1235293d01396abeddacf7f I have ported and tested the fix and it is working, both on a computer with older procps and on a computer running Ubuntu Xenial. Will submit a debdiff with proposed patch shortly. Best regards, Christian Biamont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-contrib/+bug/1610878/+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 1605243] Re: iscsi initiator related configs and logs are not recorded
** Also affects: sosreport (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu Zesty) Status: New => In Progress ** Changed in: sosreport (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Zesty) Assignee: (unassigned) => Louis Bouchard (louis) -- 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/1605243 Title: iscsi initiator related configs and logs are not recorded Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: In Progress Status in sosreport source package in Xenial: In Progress Status in sosreport source package in Yakkety: In Progress Status in sosreport source package in Zesty: In Progress Bug description: [SRU justification] iscsi initiator data is needed for proper analysis [Impact] Difficult to investigate iscsi problems w/o the data [Fix] Enable the iscsi plugin for Ubuntu and Debian [Test Case] Without the fix, invoking the iscsi plugin will show : # sosreport --batch -oiscsi sosreport (version 3.1) a non-existing plugin (iscsi) was specified in the command line With the fix, the command will run successfully and collect the appropriate data. [Regression] None, the plugin was disabled previously. [Original description of the problem] iscsi useful initiator information such as: 1). etc/iscsi/* 2). iscsiadm -m session -P3 These 2 are useful for debugging the iscsi initiator side bug. However, it's not included by default in the sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+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 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial
This bug was fixed in the package python-os-brick - 1.2.0-2ubuntu0.3
---
python-os-brick (1.2.0-2ubuntu0.3) xenial; urgency=medium
* d/p/Stop-calling-multipath-r-when-attaching-detaching-iS.patch: Backport
Backport fix for stopping calling 'multipath -r' (LP: #1623700)
-- Zhang Hua Fri, 17 Mar 2017 19:23:13
+0800
** Changed in: python-os-brick (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/1623700
Title:
[SRU] multipath iscsi does not logout of sessions on xenial
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive mitaka series:
Fix Committed
Status in Ubuntu Cloud Archive newton series:
Fix Committed
Status in os-brick:
Fix Released
Status in python-os-brick package in Ubuntu:
Fix Released
Status in python-os-brick source package in Xenial:
Fix Released
Status in python-os-brick source package in Yakkety:
Fix Released
Bug description:
[Impact]
* multipath-tools has a bug that 'multipath -r' can cause
/dev/mapper/ to be deleted and re-created momentarily (bug
#1621340 is used to track this problem), thus os.stat(mdev) right
after _rescan_multipath ('multipath -r') in os-brick can fail if it is
executed before multipath dev being re-created. This will also lead to
multipath iscsi does not logout of sessions on xenial.
[Test Case]
* Enable cinder multipath by adding iscsi_ip_address and
iscsi_secondary_ip_addresses in cinder.conf
* Enable nova multipath by adding iscsi_use_multipath=True in [libvirt]
secion of nova.conf
* Detach a iSCSI volume
* Check that devices/symlinks do not get messed up mentioned below, or check
that multipath device /dev/mapper/ doesn't be deleted and re-created
momentarily
[Regression Potential]
* multipath-tools loads devices on its own, we shouldn't need to be
forcing multipathd to do reload, so there is no regression potential.
stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m
session
tcp: [5] 10.0.1.10:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [6] 10.0.5.10:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [7] 10.0.1.11:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [8] 10.0.5.11:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m node
10.0.1.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.5.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.5.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.1.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
stack@xenial-devstack-master-master-20160914-092014:~$ sudo tail -f
/var/log/syslog
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get udev uid:
Invalid argument
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sysfs uid:
Invalid argument
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sgio uid:
No such file or directory
Sep 14 22:33:14 xenial-qemu-tester systemd[1347]:
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1347]:
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1]:
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1]:
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester kernel: [22362.163521] audit: type=1400
audit(1473892394.556:21): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="libvirt-6e1017a7-6dea-418f-ad9b-879da085bd13"
pid=32665 comm="apparmor_parser"
Sep 14 22:33:14 xenial-
[Group.of.nepali.translators] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
This bug was fixed in the package ido - 13.10.0+14.04.20170403-0ubuntu1 --- ido (13.10.0+14.04.20170403-0ubuntu1) trusty; urgency=medium * IdoCalendarMenuItem: disconnect from parent signals on item destruction (LP: #1506427) -- Marco Trevisan (Treviño) Mon, 03 Apr 2017 16:09:37 + ** Changed in: ido (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/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Released Status in ido source package in Xenial: Fix Released Status in ido source package in Yakkety: Fix Released Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1614052] Re: SOSREPORT need to collect OPAL msglog
** Also affects: sosreport (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Zesty) Status: New => In Progress ** Changed in: sosreport (Ubuntu Trusty) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: sosreport (Ubuntu Yakkety) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: sosreport (Ubuntu Zesty) Assignee: (unassigned) => Louis Bouchard (louis) -- 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/1614052 Title: SOSREPORT need to collect OPAL msglog Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: In Progress Status in sosreport source package in Xenial: In Progress Status in sosreport source package in Yakkety: In Progress Status in sosreport source package in Zesty: In Progress Bug description: [SRU justification] Required to collect OPAL message log [Impact] Logs are unavailable without this fix [Fix] Add collection of /sys/firmware/opal/msglog if it exists [Test Case] Run sosreport on ppc64el with : $ sudo sosreport --batch -opowerpc The content of /sys/firmware/opal/msglog will be collected [~apw: we also need to test a selection of the other data is collected still to ensure we did not regress any non-opal data.] [Regression] None, this was not collected previously. [Original description of the problem] == Comment: #0 - Mukesh K. Ojha - 2016-08-17 02:13:40 == ---Problem Description--- Currently, SOSREPORT version used by 16.04.01 LTS release does not collect OPAL log which is present in /sys/firmware/opal/msglog. A patch has been submitted upstream(https://github.com/sosreport/sos.git) to do the above thing. commit 1bbf9e9690e7f2a5afc234b905537daacaecb6d4 Author: Joel Stanley Date: Tue Apr 15 14:05:17 2014 +0100 Add OPAL log to collected file list The OPAL console log used to live under /sys/kernel/debug/powerpc so it was collected as part of that glob. This patch adds the new location at /sys/firmware/opal/msglog to the list of collected files. Signed-off-by: Joel Stanley Reviewed-by: Vasant Hegde Contact Information = Contact Information = hegdevas...@linux.vnet.ibm.com, mukeo...@in.ibm.com ---uname output--- Ubuntu 16.04.01 LTS Machine Type = All power machine ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@ltctul57a-p1:/home/mukesh# sosreport sosreport (version 3.2.0a1) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.sj1x27eq. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter your first initial and last name [ltctul57a-p1]: Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Running 73/73: xfs... Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-ltctul57a-p1-20160810185800.tar.xz The checksum is: 33dbfc480ebf985e4372430537339c1c Please send this file to your support representative. root@ltctul57a-p1:/home/mukesh# root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls boot dev etc hostnameip_addr lib lsmod lspci netstat ps route sos_commands sos_reports uname usr version.txt date df free installed-debs last lsb-release lsof mount proc pstree runsos_logs sys uptime var vgdisplay root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# ls sys/ bus class devices fs kernel module root@ltctul57a-p1:/home/mukesh/sosreport-ltctul57a-p1-20160810185800# No Firmware directory available that confirms the unavailability of OPAL msglog. Userspace tool common name: sosreport The userspace tool has the following bit modes: both Userspace rpm: root@ltctul57a-p1:/home/mukesh# dpkg -l | grep sosreport ii sosreport 3.2+git276-g7da50d6-3ubuntu1ppc64el Set of tools to gather troubleshooting data from a system Userspace tool obtained from project website: na *Additional Instructions for Contact Information = hegdevas...@linux.vnet.ibm.com, mukeo...@in.ibm.com : -Attach ltrace and strace of userspace applicatio
[Group.of.nepali.translators] [Bug 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial
This bug was fixed in the package python-os-brick - 1.6.1-0ubuntu1.2
---
python-os-brick (1.6.1-0ubuntu1.2) yakkety; urgency=medium
* d/p/stop-calling-multipath-r-when-attaching-detaching-iS.patch
Backport fix for stopping calling 'multipath -r' (LP: #1623700)
-- Hua Zhang Wed, 22 Mar 2017 18:04:15
+0800
** Changed in: python-os-brick (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/1623700
Title:
[SRU] multipath iscsi does not logout of sessions on xenial
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive mitaka series:
Fix Committed
Status in Ubuntu Cloud Archive newton series:
Fix Committed
Status in os-brick:
Fix Released
Status in python-os-brick package in Ubuntu:
Fix Released
Status in python-os-brick source package in Xenial:
Fix Released
Status in python-os-brick source package in Yakkety:
Fix Released
Bug description:
[Impact]
* multipath-tools has a bug that 'multipath -r' can cause
/dev/mapper/ to be deleted and re-created momentarily (bug
#1621340 is used to track this problem), thus os.stat(mdev) right
after _rescan_multipath ('multipath -r') in os-brick can fail if it is
executed before multipath dev being re-created. This will also lead to
multipath iscsi does not logout of sessions on xenial.
[Test Case]
* Enable cinder multipath by adding iscsi_ip_address and
iscsi_secondary_ip_addresses in cinder.conf
* Enable nova multipath by adding iscsi_use_multipath=True in [libvirt]
secion of nova.conf
* Detach a iSCSI volume
* Check that devices/symlinks do not get messed up mentioned below, or check
that multipath device /dev/mapper/ doesn't be deleted and re-created
momentarily
[Regression Potential]
* multipath-tools loads devices on its own, we shouldn't need to be
forcing multipathd to do reload, so there is no regression potential.
stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m
session
tcp: [5] 10.0.1.10:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [6] 10.0.5.10:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [7] 10.0.1.11:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
tcp: [8] 10.0.5.11:3260,1
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m node
10.0.1.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.5.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.5.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
10.0.1.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
stack@xenial-devstack-master-master-20160914-092014:~$ sudo tail -f
/var/log/syslog
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get udev uid:
Invalid argument
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sysfs uid:
Invalid argument
Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sgio uid:
No such file or directory
Sep 14 22:33:14 xenial-qemu-tester systemd[1347]:
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1347]:
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1]:
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester systemd[1]:
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared
twice with different sysfs paths
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and
/sys/devices/virtual/block/dm-0
Sep 14 22:33:14 xenial-qemu-tester kernel: [22362.163521] audit: type=1400
audit(1473892394.556:21): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="libvirt-6e1017a7-6dea-418f-ad9b-879da085bd13"
pid=32665 comm="apparmor_parser"
Sep 14 22:33:14 xenial-qemu-test
[Group.of.nepali.translators] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
** Also affects: linux-firmware (Ubuntu Artful) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Status in linux-firmware source package in Artful: Confirmed Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install
This bug was fixed in the package appstream - 0.9.4-1ubuntu3 --- appstream (0.9.4-1ubuntu3) xenial; urgency=medium [ Carlo Vanini ] * modern-metadata-in-qt.patch: Fix type label for desktop applications in the Qt library. (LP: #1663695) [ Matthias Klumpp ] * Fix autopkgtest tests. -- Matthias Klumpp Fri, 31 Mar 2017 13:21:01 +0100 ** Changed in: appstream (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/1663695 Title: Kubuntu 16.04.1 discover empty after fresh install Status in appstream package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in plasma-discover package in Ubuntu: Invalid Status in appstream source package in Xenial: Fix Released Status in packagekit source package in Xenial: Invalid Status in plasma-discover source package in Xenial: Invalid Bug description: [Impact] * A previous update made AppStream use modern-style component-ids, thereby breaking the Qt library if it is reading data from the cache and if that data happens to be a desktop-application. * This leads to KDE's Discover not displaying applications. * The issue was introduced by a patch to the Xenial version of AppStream, and is not present in any other version of the package in Ubuntu, affecting Xenial only. [Test Case 1] * Update the libappstream-qt package, run Discover: All apps should be loaded correctly. [Regression Potential] * Low, this change affects only the Qt bindings and nothing else. The change is also a simple string value change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1663695/+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 1666239] Re: Add ZFS sosreport plugin
** Also affects: sosreport (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu) Status: Confirmed => Fix Released ** Changed in: sosreport (Ubuntu Trusty) Status: New => In Progress ** Changed in: sosreport (Ubuntu Xenial) Status: New => In Progress ** Changed in: sosreport (Ubuntu Yakkety) Status: New => In Progress ** Changed in: sosreport (Ubuntu Zesty) Status: New => In Progress ** Changed in: sosreport (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Trusty) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: sosreport (Ubuntu Yakkety) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: sosreport (Ubuntu Zesty) Assignee: (unassigned) => Louis Bouchard (louis) -- 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/1666239 Title: Add ZFS sosreport plugin Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: In Progress Status in sosreport source package in Xenial: In Progress Status in sosreport source package in Yakkety: In Progress Status in sosreport source package in Zesty: In Progress Bug description: [Impact] * Current sosreport doesn't include any ZFS verifications, which could be useful for general initial ZFS troubleshooting on Xenial and upward. (Xenial being the release where ZFS has been first introduced in Ubuntu.) [Test Case] #1) Have ZFS installed and configured - https://wiki.ubuntu.com/Kernel/Reference/ZFS #2) Have sosreport installed and configured $ sudo apt-get update $ sudo apt-get install sosreport -y #3) Run sosreport $ /usr/bin/sosreport -a #4) Lookin for a sosreport*.tar.xz file in /tmp - In PATH_TO_SOSREPORT/sos_commands/, there will be no trace of zfs output, cause as of today, there is no ZFS plugin in Ubuntu/Debian nor upstream. [Regression Potential] * No regression * The PR passed all the upstream checks. [Other Info] * Pull Request: https://github.com/sosreport/sos/pull/934 (Closed #934 via 922ea54) * Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 [Original Description] I did a PR to upstream sosreport in order to include the ZFS plugin for Ubuntu/Debian. PR: https://github.com/sosreport/sos/pull/934 Commit : https://github.com/sosreport/sos/commit/922ea54bf4f9cb488f72a75a180e5351169dd710 The ZFS plugin is collecting ZFS informations using the following commands : "zfs get all" "zfs list -t all -o space" "zpool list" "zpool status -x" It would be great to have this ZFS plugin available for Xenial (where ZFS has been first introduce in Ubuntu) and upward (Zesty, ...) - Eric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+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 1681294] Re: ugly "pthread_create failed: Resource temporarily unavailable" running snaps
This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04.2
---
golang-1.6 (1.6.2-0ubuntu5~16.04.2) xenial; urgency=medium
* Fix build on ppc64el.
golang-1.6 (1.6.2-0ubuntu5~16.04.1) xenial; urgency=medium
* Backport fix for ugly "pthread_create failed: Resource temporarily
unavailable" message when calling syscall.Exec. (LP: #1681294)
* Backport CL 29995 for tzdata 2016g changes.
* Backport CL 37964 for tzdata 2017a changes.
-- Michael Hudson-Doyle Wed, 12 Apr 2017
14:42:48 +1200
** Changed in: golang-1.6 (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/1681294
Title:
ugly "pthread_create failed: Resource temporarily unavailable" running
snaps
Status in golang-1.6 package in Ubuntu:
Invalid
Status in golang-1.7 package in Ubuntu:
New
Status in golang-1.6 source package in Xenial:
Fix Released
Status in golang-1.6 source package in Yakkety:
Won't Fix
Bug description:
[Impact]
As reported here:
https://lists.ubuntu.com/archives/snapcraft/2017-March/003497.html (and on
internal lists), it is possible for a golang executable that calls syscall.Exec
to print an ugly "pthread_create failed: Resource temporarily unavailable"
message before it starts the new process. There is no functional effect, but
snapd runs into this frequently so it interferes with a nice snappy experience.
Luckily for us, the bug was fixed upstream in the 1.8 release
(https://github.com/golang/go/issues/18146) so I can just backport the
fix to Xenial and Yakkety.
It also turns out to be necessary to include two more upstream patches
that fix test suite failures with new tzdata packages.
[Test case]
Run this code:
package main
//
import "C"
import (
"syscall"
)
func main() {
syscall.Exec("/bin/true", []string{"/bin/true"}, nil)
}
a few thousand times and check for messages (it prints a message ~2%
of the time or so without the fix).
[Regression potential]
The patch is simple, if a bit verbose (it has some per-architecture changes).
It has not been the cause of any bug reports in 1.8 as far as I am aware. So I
would characterise the regression potential as very low.
The tzdata patches are similarly well exercised as they are backports,
and are necessary or the build will fail!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1681294/+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 1684965] Re: [SRU] New stable micro release 2.29
This bug was fixed in the package snapcraft - 2.29+16.10 --- snapcraft (2.29+16.10) yakkety; urgency=medium [ Sergio Schvezov ] * store: better retry strategy for GETs. (#1212) * docs: remove docs and link to snappy-docs. (#1227) * nodejs plugin: switch to the newer LTS. (#1228) * pluginhandler: exclude `/snap/` from libraries. (#1231) * nodejs plugin: switch to the newer LTS. (#1228) (#1232) * core: find the correct libraries as a snap. (#1234) * snap: use the gpg tarball instead of git://. (#1236) * docs: update contribution guide. (#1233) * repo: enable elementary. (#1237) * cli: improve push output. (#1240) * ci: split plugin integration tests out. (#1252) * nodejs plugin: add support for yarn. (#1245) * ci: fix travis ordering for locales generation. (#1254) * core: support running from other operating systems. (#1257) * meta: version from git support. (#1260) * shell_utils: code cleanup (#1265) * meta: override the version with version-script. (#1267) * tests: fix package version pinning tests. (#1269) * New upstream release 2.29 (LP: #1684965) [ Joe Talbott ] * tests: Fix staging store test for Tracks. (#1225) * pluginhandler: factor out state bits into the state package. (#1221) * repo: track per-part build-packages. (#1193) * sources: add VCS asset tracking (#1229) [ Facundo Batista ] * store: better check of the error code in StatusTracker. (#1226) [ Leo Arias ] * tests: add arm64 to the nightly tests (#1210) * tests: update name registration window limit test. (#1224) * ci: update the location of the upstream retry autopkgtests script. (#1243) * tests: use launchpad as the source of the compressed test snap (#1259) [ Jumpei Ogawa ] * repo: enable KDE Neon. (#1244) [ Kyle Fazzari ] * catkin plugin: create completely valid environment (#1239) [ edvega ] * help: replace dashes with underscores when printing plugins help (#1241) * cli: remove empty lines in the unclean parts message (#1251) [ Celso Providelo ] * store: new registration errors and test update. (#1247) [ Christian Dywan ] * lxd: refactor Cleanbuilder into Containerbuild and add Project. (#1230) [ Parameswaran Sivatharman ] * store: plumbing for collaboration support. (#1246) [ Colin Watson ] * ant plugin: honour proxy configuration (#1256) [ Chris MacNaughton ] * rust plugin: update plugin to set RUSTFLAGS (#1255) [ Andy Li ] * docs: fixed links to doc. (#1250) * tests: report coverage only in unit tests. (#1266) -- Sergio Schvezov Thu, 20 Apr 2017 13:57:08 -0300 ** Changed in: snapcraft (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: snapcraft (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/1684965 Title: [SRU] New stable micro release 2.29 Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: Fix Released Status in snapcraft source package in Yakkety: Fix Released Status in snapcraft source package in Zesty: Fix Released Bug description: This is an SRU bug to release 2.29 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates The list of bugs and features in this release are defined at https://launchpad.net/snapcraft/+milestone/2.29 and https://github.com/snapcore/snapcraft/milestone/2?closed=1 More detailed information and procedures for this release can be found on https://forum.snapcraft.io/t/release-in-progress- snapcraft-2-29/346?u=sergiusens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1684965/+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 1684965] Re: [SRU] New stable micro release 2.29
** Changed in: snapcraft (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1684965 Title: [SRU] New stable micro release 2.29 Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: Fix Released Status in snapcraft source package in Yakkety: Fix Released Status in snapcraft source package in Zesty: Fix Released Bug description: This is an SRU bug to release 2.29 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates The list of bugs and features in this release are defined at https://launchpad.net/snapcraft/+milestone/2.29 and https://github.com/snapcore/snapcraft/milestone/2?closed=1 More detailed information and procedures for this release can be found on https://forum.snapcraft.io/t/release-in-progress- snapcraft-2-29/346?u=sergiusens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1684965/+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 1685860] Re: linux: 4.4.0-76.97 -proposed tracker
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1685860 Title: linux: 4.4.0-76.97 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-76.97 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 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1685860/+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 1686040] Re: linux: 4.4.0-77.98 -proposed tracker
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686040 Title: linux: 4.4.0-77.98 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-77.98 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 kernel-stable-phase:Packaging kernel-stable-phase-changed:Tuesday, 25. April 2017 08:16 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686040/+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 1686064] [NEW] sbuild ADT test can only pass in devel series
Public bug reported: [Impact] * sbuild adt tests assume that the test is running on the host, which is the current devel series, which is not the case when adt tests are running as part of SRU regression testing. [Test Case] * ADT test should pass [Regression Potential] * sbuild itself is not modified, only the autopkgtest themself are fixed to not make unrealistic assumptions [Other Info] * Original bug report / problem description src:sbuild has test build-procenv which can only pass in devel series, as it assumes that the release test is running is the devel series. This was true, until we started to run adt tests for stable releases and SRUs. Here is the detailed log of running build-procenv on xenial, whilst devel series is called artful: # ADTTMP=$(mktemp -d) sh -x debian/tests/build-procenv + set -e + pkg=procenv + components= + lsb_release -is + tr [A-Z] [a-z] + distro=ubuntu + [ -z ubuntu ] + lsb_release -cs + host_release=xenial + [ -z xenial ] + [ ubuntu = ubuntu ] + distro-info --devel + release=artful + components=main,universe + dpkg --print-architecture + url=http://archive.ubuntu.com/ubuntu + dpkg --print-architecture + arch=amd64 + [ -z amd64 ] + [ -z /tmp/tmp.QYJvzqYkbV ] + dir=/tmp/tmp.QYJvzqYkbV/schroot-artful + chroot=artful-amd64-sbuild + schroot -l + schroots= + [ -n ] + [ -z ] + apt-config shell http_proxy Acquire::http::Proxy + RES= + eval + export http_proxy + echo INFO: using proxy: (none) INFO: using proxy: (none) + echo INFO: Downloading source for package 'procenv' from release 'artful' INFO: Downloading source for package 'procenv' from release 'artful' + apt-get source --download-only -o APT::Sandbox::User=root procenv/artful Reading package lists... Done E: Unable to find a source package for procenv There are a couple of options here depending what we want to test. We can either build procenv from $current on $current release -> this will test that e.g. SRUs in xenial, do not break building packages for xenial on xenial. Or we can try to always build procenv from $devel in $devel chroot -> this will test that all currently supported releases, can build packages for $devel series. ** Affects: sbuild (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: sbuild (Ubuntu Xenial) Importance: Medium Assignee: Dimitri John Ledkov (xnox) Status: In Progress ** Affects: sbuild (Ubuntu Yakkety) Importance: Medium Assignee: Dimitri John Ledkov (xnox) Status: In Progress ** Also affects: sbuild (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sbuild (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: sbuild (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: sbuild (Ubuntu Yakkety) Importance: Undecided Status: New ** No longer affects: sbuild (Ubuntu Zesty) ** No longer affects: sbuild (Ubuntu Artful) ** Changed in: sbuild (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686064 Title: sbuild ADT test can only pass in devel series Status in sbuild package in Ubuntu: Fix Released Status in sbuild source package in Xenial: In Progress Status in sbuild source package in Yakkety: In Progress Bug description: [Impact] * sbuild adt tests assume that the test is running on the host, which is the current devel series, which is not the case when adt tests are running as part of SRU regression testing. [Test Case] * ADT test should pass [Regression Potential] * sbuild itself is not modified, only the autopkgtest themself are fixed to not make unrealistic assumptions [Other Info] * Original bug report / problem description src:sbuild has test build-procenv which can only pass in devel series, as it assumes that the release test is running is the devel series. This was true, until we started to run adt tests for stable releases and SRUs. Here is the detailed log of running build-procenv on xenial, whilst devel series is called artful: # ADTTMP=$(mktemp -d) sh -x debian/tests/build-procenv + set -e + pkg=procenv + components= + lsb_release -is + tr [A-Z] [a-z] + distro=ubuntu + [ -z ubuntu ] + lsb_release -cs + host_release=xenial + [ -z xenial ] + [ ubuntu = ubuntu ] + distro-info --devel + release=artful + components=main,universe + dpkg --print-architecture + url=http://archive.ubuntu.com/ubuntu + dpkg --print-architecture + arch=amd64 + [ -z amd64 ] + [ -z /tmp/tmp.QYJvzqYkbV ] + dir=/tmp/tmp.QYJvzqYkbV/schroot-artful + chroot=artful-amd64-sbuild + schroot -l + schroots= + [ -n ] + [ -z ] + apt-config shell http_proxy Acquire::http::Proxy + RES= + eval + export http_proxy + echo INFO: using prox
[Group.of.nepali.translators] [Bug 1686077] Re: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too
This bug was fixed in the package gnome-settings-daemon - 3.24.1-0ubuntu3 --- gnome-settings-daemon (3.24.1-0ubuntu3) artful; urgency=medium * Really add git_fix-gdm-plugins.patch * Add media-keys-Fix-mmkeys-D-Bus-API-to-match-API-docs.patch: Own the D-Bus name that the API documentation tells users of the multimedia keys API they should use (org.gnome.SettingsDaemon.MediaKeys), in addition to the D-Bus name that they actually use in practice (org.gnome.SettingsDaemon). (LP: #1686077) -- Jeremy Bicha Tue, 25 Apr 2017 07:55:13 -0400 ** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu ** Changed in: gnome-settings-daemon (Ubuntu) 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/1686077 Title: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too Status in gnome-settings-daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon source package in Xenial: Triaged Status in unity-settings-daemon source package in Xenial: Triaged Status in gnome-settings-daemon source package in Yakkety: Triaged Status in unity-settings-daemon source package in Yakkety: Triaged Status in gnome-settings-daemon source package in Zesty: Triaged Status in unity-settings-daemon source package in Zesty: Triaged Status in gnome-settings-daemon package in Debian: Unknown Bug description: Impact == This bugfix enabled gnome-settings-daemon's multimedia key support to work according to what the API has said for years (in addition to the way it's been commonly used). https://git.gnome.org/browse/gnome-settings- daemon/commit/?h=gnome-3-24&id=42f75ed4cdc86498d6e02e511a1314b8916bd4aa https://mail.gnome.org/archives/desktop-devel- list/2017-April/msg00069.html The SRU justification is that newer versions of apps will be switching to the D-Bus name in the API documentation. If someone installs the newer version from a PPA or a Flatpak or Snap, the multimedia key support should continue working. Test Case = ? Regression Potential This should just make gnome(unity)-settings-daemon own both the commonly used D-Bus name and the one actually defined in the API docs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686077/+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 1686082] Re: autopkgtest autopkgtest fails on xenial when run under autopkgtest
This fixes it, going to upload.
commit cbac10742cc44d66c82ee9776157273a5cce7a59
Author: Martin Pitt
Date: Tue May 31 23:42:47 2016 +0200
Fix ChrootRunner.test_setup_commands_string when ran recursively
Commit a94e5ac42 exported $ADT_NORMAL_USER to tests. So remove it from the
environment for the this test as it otherwise breaks it when we run our own
tests through autopkgtest.
diff --git a/tests/adt-run b/tests/adt-run
index fc7e7c0..1f870a0 100755
--- a/tests/adt-run
+++ b/tests/adt-run
@@ -1638,13 +1638,19 @@ Restrictions: needs-root
p = self.build_src('Tests: pass\nDepends:\nRestrictions: needs-root\n',
{'pass': '#!/bin/sh -e\n[ -x /bin/cp_cp ]; cat
/setup.log\n'})
-# not expecting a normal user for chroot
+# not expecting a normal user for chroot; but filter out any
+# $ADT_NORMAL_USER from *our* environment
+env = os.environ.copy()
+try:
+del env['ADT_NORMAL_USER']
+except KeyError:
+pass
(code, out, err) = self.runtest(['-B', '--unbuilt-tree=' + p,
'--setup-commands', '[ -z
$ADT_NORMAL_USER ];'
'sleep 3; cp /bin/cp /bin/cp_cp; '
'echo setup_success > /setup.log',
'--setup-commands', 'cp /bin/cp
/bin/cp_cp',
- '--timeout-short=1',
'--timeout-copy=1'])
+ '--timeout-short=1',
'--timeout-copy=1'], env=env)
# test should succeed
self.assertEqual(code, 0, err)
self.assertRegex(out, 'pass\s+PASS', out)
** Also affects: autopkgtest (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: autopkgtest (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: autopkgtest (Ubuntu Xenial)
Status: New => In Progress
** Changed in: autopkgtest (Ubuntu Xenial)
Assignee: (unassigned) => Iain Lane (laney)
** Description changed:
+ [ Description ]
+
+ autopkgtest's own autopkgtests are failing in xenial. The environment
+ now exports $ADT_NORMAL_USER into the tests, and one of the tests checks
+ that this is not set. Commit cbac10742cc44d66c82ee9776157273a5cce7a59
+ cleans it out of the test in question's environment.
+
+ [ Fix ]
+
+ Cherry pick that commit.
+
+ [ QA ]
+
+ This is a testsuite fix. Check that the package builds and that the
+ autopkgtests pass.
+
+ [ Regression potential ]
+
+ It's a test fix only. If it's bad then the test won't be fixed. If the
+ test fix itself is wrong then we could be allowing a regression to pass
+ through. But this fix is in subsequent releases.
+
+ [ Development fix ]
+
+ The commit is in ≥ yakkety.
+
+ [ Original description ]
+
==
FAIL: test_setup_commands_string (__main__.ChrootRunner)
--setup-commands with command string
--
Traceback (most recent call last):
- File "/tmp/autopkgtest.4F1JtS/build.knp/autopkgtest-3.20.4/tests/adt-run",
line 1628, in test_setup_commands_string
- self.assertEqual(code, 0, err)
+ File "/tmp/autopkgtest.4F1JtS/build.knp/autopkgtest-3.20.4/tests/adt-run",
line 1628, in test_setup_commands_string
+ self.assertEqual(code, 0, err)
AssertionError: 16 != 0 : adt-run [12:25:30]: version @version@
adt-run [12:25:30]: host autopkgtest-lxd-muplzd; command line:
/tmp/autopkgtest.4F1JtS/build.knp/autopkgtest-3.20.4/runner/adt-run -B
--unbuilt-tree=/tmp/test.adt-run.4aqx12ew/testpkg --setup-commands '[ -z
$ADT_NORMAL_USER ];sleep 3; cp /bin/cp /bin/cp_cp; echo setup_success >
/setup.log' --setup-commands 'cp /bin/cp /bin/cp_cp' --timeout-short=1
--timeout-copy=1 --- chroot /tmp/test.adt-run.4aqx12ew/chroot
adt-run [12:25:31]: test bed setup
adt-run [12:25:31]: ERROR: testbed failure: testbed setup commands failed
with status 1
-
--
Ran 211 tests in 189.417s
FAILED (failures=1, skipped=141)
autopkgtest [13:28:08]: test adt-run: ---]
autopkgtest [13:28:08]: test adt-run: - - - - - - - - - - results - - - - -
- - - - -
adt-run FAIL non-zero exit status 1
autopkgtest [13:28:09]: - - - - - - - - - - running shell - - - - - - - - - -
root@autopkgtest-lxd-muplzd:/tmp/autopkgtest.4F1JtS/build.knp/autopkgtest-3.20.4#
./tests/adt-run ChrootRunner.test_setup_commands_string
test_setup_commands_string (__main__.ChrootRunner)
--setup-commands with command string ... ok
--
Ran 1 test in 4.185s
OK
root@autopkgtest-lxd-muplzd:/tmp/autopkgtest.4F1JtS/build.knp/autopkgtest-3.20.4#
-
This is happe
[Group.of.nepali.translators] [Bug 1685131] Re: root cannot login to system without password
Hi Thomas thank you for your report and your help to make Ubuntu better. I found the associated change at: https://pagure.io/SSSD/sssd/c/fcbcfa69f9291936f01f24b5fcb5a7672dca46f3 That fix is in version 1.14 which means that Ubuntu Zesty and later are already fixed. Adding a bug task fro X/Y - not sure if it applies back to trusty. By the code alone I'd think it does, but one has to confirm with a Test. ** Also affects: sssd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: sssd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1685131 Title: root cannot login to system without password Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: New Status in sssd source package in Yakkety: New Bug description: similar issue: https://pagure.io/SSSD/sssd/issue/3003 (Workaround suggested above don't work on Xenial) dev3 detail: /var/log/auth.log - dev3 sshd[77]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 root@dev3:~# cat .k5login us...@hk.domain.com root@dev3:~# cat /root/.k5login us...@hk.domain.com root@dev3:~# sss_ssh_authorizedkeys user1 root@dev3:~# sss_ssh_authorizedkeys root Error looking up public keys root@dev3:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial root@dev3:~# sssd --version 1.13.4 root@dev3:~# cat /etc/nsswitch.conf passwd: compat sss group: compat sss shadow: compat sss gshadow:files hosts: files dns networks: files protocols: db files services: db files sss ethers: db files rpc:db files netgroup: nis sss sudoers: files sss login from Mocha to dev3: user1@mocha:~$ ssh r...@dev3.hk.domain.com r...@dev3.hk.domain.com's password: (Ctrl+c) user1@mocha:~$ ssh us...@dev3.hk.domain.com Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-72-generic x86_64) user1@dev3:/home/user1$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1685131/+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 1641203] Re: SSSD can't process GPO from Active Directory when it contains lines with no equal sign
sssd in 17.04 works
** Changed in: sssd (Ubuntu)
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/1641203
Title:
SSSD can't process GPO from Active Directory when it contains lines
with no equal sign
Status in ding-libs package in Ubuntu:
Fix Released
Status in sssd package in Ubuntu:
Fix Released
Status in ding-libs source package in Xenial:
Triaged
Status in sssd source package in Xenial:
Triaged
Bug description:
[Impact]
This bug hits users who is joined to a domain server (probably MS Active
Directory) where there is a GPO line that doesn't contain an equal sign (=).
See more info in the upstreams bug report linked below. This could be rather
common in corporate environments and normally nothing you "fix" on the domain
controller side to be able to use SSSD clients. This means all clients that
upgrades to 16.04 using SSSD with a GPO containing a line without equal sign
will be affected.
[Test Case]
Steps to reproduce (you'll need a domain server with GPO containing a line
withouth equal sign!):
- Install:
apt install krb5-user samba sssd ntp
- Make sure the default realm is setup properly (FQDN in uppercase):
dpkg-reconfigure krb5-config
- Set up /etc/samba/smb.conf like this: https://paste.ubuntu.com/24407627/
- Set up /etc/sssd/sssd.conf like this: https://paste.ubuntu.com/24407643/
- File permissions:
sudo chown root:root /etc/sssd/sssd.conf
sudo chmod 600 /etc/sssd/sssd.conf
- Restart services:
sudo service ntp restart
sudo service smbd restart
sudo service nmbd restart
- Join domain with:
sudo net ads join -U "administra...@domain.com"
"createcomputer=Servers/Virtual" osName=Ubuntu osVer=16.04
- Start SSSD:
sudo service sssd start
- Verify:
getent passwd administra...@qrtech.se
- Add creation of home directories on login (check the unchecked box):
sudo pam-auth-update
- Now try to login to the server with a domain user:
arune@d152:~$ ssh ar...@domain.com@server.domain.com
- This should fail and you'll find in the logs:
grep "ad_gpo_store_policy_settings" /var/log/sssd/*
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020):
[/var/lib/sss/gpo_cache/DOMAIN.COM/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/Machine/Microsoft/Windows
NT/SecEdit/GptTmpl.inf]: ini_config_parse failed [5][Input/output error]
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020): Error (5) on
line 20: Equal sign is missing.
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_store_policy_settings] (0x0020): Error
encountered: 5.
/var/log/sssd/sssd_DOMAIN.COM.log:(Tue Apr 18 15:13:28 2017)
[sssd[be[DOMAIN.COM]]] [ad_gpo_cse_done] (0x0040): ad_gpo_store_policy_settings
failed: [5](Input/output error)
[Regression Potential]
The current state of SSSD in Xenial is broken for _some_ users (where the GPO
has a line without equal sign) it's _not known_ how many users are affected. A
potential regression could mean even more users are affected by a new unknown
bug.
Upstreams bugreport and patch:
https://fedorahosted.org/sssd/ticket/2751
Please backport to xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ding-libs/+bug/1641203/+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 1685610] Re: assertion failed: String.cc
At least from the source containing the assert, this could go back to Trusty. ** Also affects: squid3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: squid3 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: squid3 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: squid3 (Ubuntu) Status: New => Fix Released ** Changed in: squid3 (Ubuntu Trusty) Status: New => Incomplete ** Changed in: squid3 (Ubuntu Xenial) Status: New => Incomplete ** Changed in: squid3 (Ubuntu Yakkety) Status: New => Incomplete -- 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/1685610 Title: assertion failed: String.cc Status in squid3 package in Ubuntu: Fix Released Status in squid3 source package in Trusty: Incomplete Status in squid3 source package in Xenial: Incomplete Status in squid3 source package in Yakkety: Incomplete Bug description: assertion failed: String.cc:174: "len_ + len < 65536" current squid crash with this bug http://bugs.squid-cache.org/show_bug.cgi?id=4448 squid 3.5.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1685610/+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
