[Group.of.nepali.translators] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu8 --- unattended-upgrades (0.93.1ubuntu8) artful; urgency=medium [ Steve Langasek ] * Cherry-pick 2e5deed, f26edb4 from upstream to add support for a --download-only option, enabling us to download updates at a random time of day by default but apply them predictably in the 6am-7am window. LP: #1686470. -- Dimitri John Ledkov Mon, 31 Jul 2017 23:28:38 +0100 ** Changed in: unattended-upgrades (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Committed Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.
[Group.of.nepali.translators] [Bug 1707082] Re: regression on openjdk-8 caused by the S8169392 security update
This bug was fixed in the package openjdk-8 - 8u131-b11-2ubuntu1.17.04.3 --- openjdk-8 (8u131-b11-2ubuntu1.17.04.3) zesty-security; urgency=medium * Fix regression introduced by security fix S8169392. LP: #1707082. - debian/rules: apply jdk-S8184993-fix-S8169392-regression.patch. - debian/patches/jdk-S8184993-fix-S8169392-regression.patch: upstream fix for the regression. -- Tiago Stürmer Daitx Thu, 27 Jul 2017 21:26:44 + ** Changed in: openjdk-8 (Ubuntu Zesty) Status: Confirmed => Fix Released ** Changed in: openjdk-8 (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1707082 Title: regression on openjdk-8 caused by the S8169392 security update Status in openjdk-8 package in Ubuntu: Confirmed Status in openjdk-8 source package in Xenial: Fix Released Status in openjdk-8 source package in Zesty: Fix Released Bug description: The security update S8169392 introduced a regression on OpenJDK 8 and the regression was fixed by S8184993 (released as 8u144). This was reported on http://mail.openjdk.java.net/pipermail/jdk8u- dev/2017-July/006793.html This affects OpenJDK-8 versions: - Xenial: 8u131-b11-2ubuntu1.16.04.2 - Zesty: 8u131-b11-2ubuntu1.17.04.2 - Artful: 8u141-b15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1707082/+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 1704817] Re: [Xenial] nvme-cli does not recognize version 1.0 NVME drives
@Manoj: While the code in the patch looks fine, I do see a couple issues with the DEP-3 headers: >Description: Remove version from list > We can't reliably map controller registers due to kernel memory > protections added in kernel commit 90a545e98, so we are removing its > dependency for the 'list' command to run. > Author: Keith Busch I'd suggest starting with the git commit, including all the metadata, and adding the DEP-3 specific fields (Origin, Bug) to the end of the header. > Origin: upstream, https://github.com/linux-nvme/nvme-cli Origin should be the URL of the commit, not the repository. > Bug: https://launchpad.net/bugs/## This isn't a valid URL, and it should be a pointer to the upstream bug, if one exists. The "Bug-Ubuntu" field should be used to provide a pointer to the Ubuntu bug in LP. > Forwarded: not-needed Well, technically it *is* needed since it was applied upstream. I'd suggest just omitting this field though, it only really makes sense if it is a vendor-specific patch. ** Changed in: nvme-cli (Ubuntu Xenial) Assignee: (unassigned) => Manoj Iyer (manjo) ** No longer affects: nvme-cli (Ubuntu Zesty) ** Changed in: nvme-cli (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704817 Title: [Xenial] nvme-cli does not recognize version 1.0 NVME drives Status in nvme-cli package in Ubuntu: Fix Released Status in nvme-cli source package in Xenial: Confirmed Bug description: [Impact] We've noticed that the nvme-cli package does not work on QDF2400 and gives the false impression that the hardware is broken. This prevents customers from running NVMe diagnostics. [Test Case] Current version available - ubuntu@ubuntu:~$ sudo nvme version nvme version 0.5 Current failure mode - root@ubuntu:/home/ubuntu# nvme list nvme0 did not find a pci resource Known issue: https://github.com/linux-nvme/nvme-cli/issues/81 [Fix] Backport patch https://github.com/linux-nvme/nvme-cli/commit/6ab2e9ef204053d82c1eb40e514119286749cefe [Regression Potential] None. This was tested by QTI on Version 1.0 card and by Canonical on Version 1.2 card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1704817/+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 1704817] Re: [Xenial] nvme-cli does not recognize version 1.0 NVME drives
** Also affects: nvme-cli (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: nvme-cli (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvme-cli (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvme-cli (Ubuntu Zesty) Status: New => Fix Released ** Changed in: nvme-cli (Ubuntu) Assignee: dann frazier (dannf) => (unassigned) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1704817 Title: [Xenial] nvme-cli does not recognize version 1.0 NVME drives Status in nvme-cli package in Ubuntu: Fix Released Status in nvme-cli source package in Xenial: New Status in nvme-cli source package in Zesty: Fix Released Bug description: [Impact] We've noticed that the nvme-cli package does not work on QDF2400 and gives the false impression that the hardware is broken. This prevents customers from running NVMe diagnostics. [Test Case] Current version available - ubuntu@ubuntu:~$ sudo nvme version nvme version 0.5 Current failure mode - root@ubuntu:/home/ubuntu# nvme list nvme0 did not find a pci resource Known issue: https://github.com/linux-nvme/nvme-cli/issues/81 [Fix] Backport patch https://github.com/linux-nvme/nvme-cli/commit/6ab2e9ef204053d82c1eb40e514119286749cefe [Regression Potential] None. This was tested by QTI on Version 1.0 card and by Canonical on Version 1.2 card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1704817/+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 1691772] Re: provide a way to seed NoCloud from network without image modification.
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1691772 Title: provide a way to seed NoCloud from network without image modification. Status in cloud-init: Confirmed 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 Zesty: Confirmed Bug description: Vladimir suggested this in bug 1660385 comment 12 [1]. The idea would be to have a supported way that you could seed images with cloud-init using Nocloud without any tinkering in the image. That would mean a.) no second block device b.) no usage of kernel command line. -- [1] https://bugs.launchpad.net/cloud-init/+bug/1660385/comments/12 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1691772/+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 1701097] Re: eni rendering of ipv6 gateways fails
** Changed in: cloud-init (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** No longer affects: cloud-init (Ubuntu Yakkety) -- 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/1701097 Title: eni rendering of ipv6 gateways fails 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 Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: cloud-init trunk and xenial, yakkety, zesty and artful all fail A network config with a ipv6 gateway route like: subnets: - type: static address: 2001:4800:78ff:1b:be76:4eff:fe06:96b3 netmask: ':::::' routes: - gateway: 2001:4800:78ff:1b::1 netmask: '::' network: '::' For eni rendering, this should create a post-up/post-down route command that generates a default ipv6 route entry, like this: post-up route add -A inet6 default gw 2001:4800:78ff:1b::1 || true pre-down route del -A inet6 default gw 2001:4800:78ff:1b::1 || true However, what is currently generated is this: post-up route add -net :: netmask :: gw 2001:4800:78ff:1b::1 || true pre-down route del -net :: netmask :: gw 2001:4800:78ff:1b::1 || true That does not install the route correctly as a default gateway route. This is fallout from commit d00da2d5b0d45db5670622a66d833d2abb907388 net: normalize data in network_state object This commit removed ipv6 route 'netmask' values, and converted them to prefix length values, but failed to update the eni renderer's check for ipv6 default gateway. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701097/+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 1088611] Re: using random hostnames to detect dns proxies allows for false positives
** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Xenial) Importance: Medium => 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/1088611 Title: using random hostnames to detect dns proxies allows for false positives 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 Zesty: Confirmed Bug description: The fix that's been applied for bug #974509 checks for the presence of a redirector by looking of three hostnames, and treating as invalid any results pointing to a matching address: - does-not-exist.example.com. - example.invalid. - a random, unqualified 32-character alphanumeric hostname. The last of these carries a small but non-zero risk of colliding with a real hostname, and there's a small but non-zero risk that this host points to the same address as something we care about. If possible, it would be better to not include this random-host lookup in the algorithm, as somewhere, some day, chances are there will eventually be a collision, causing an incomprehensible and unreproducible failure for a user. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1088611/+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 1706900] Re: CVE-2016-9877 RabbitMQ authentication vulnerability
This bug was fixed in the package rabbitmq-server - 3.2.4-1ubuntu0.1 --- rabbitmq-server (3.2.4-1ubuntu0.1) trusty-security; urgency=medium * SECURITY UPDATE: authentication bypass (LP: #1706900) - debian/patches/CVE-2016-9877.patch: fix password check in plugins-src/rabbitmq-mqtt/src/rabbit_mqtt_processor.erl, add test to plugins-src/rabbitmq-mqtt/test/src/com/rabbitmq/mqtt/test/MqttTest.java, fix URL in plugins-src/rabbitmq-mqtt/test/Makefile. - CVE-2016-9877 -- Marc Deslauriers Thu, 27 Jul 2017 14:48:35 -0400 ** Changed in: rabbitmq-server (Ubuntu Trusty) 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/1706900 Title: CVE-2016-9877 RabbitMQ authentication vulnerability Status in RabbitMQ: Fix Released Status in rabbitmq-server package in Ubuntu: Fix Released Status in rabbitmq-server source package in Trusty: Fix Released Status in rabbitmq-server source package in Xenial: Fix Released Bug description: https://pivotal.io/security/cve-2016-9877 "MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected." Affects RabbitMQ "3.x versions prior to 3.5.8" Ubuntu's Xenial repos are currently offering 3.5.7-1ubuntu0.16.04.1, and according to its changelog, Pivotal's fix for CVE-2016-9877 has not been included. To manage notifications about this bug go to: https://bugs.launchpad.net/rabbitmq/+bug/1706900/+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 1706900] Re: CVE-2016-9877 RabbitMQ authentication vulnerability
This bug was fixed in the package rabbitmq-server - 3.5.7-1ubuntu0.16.04.2 --- rabbitmq-server (3.5.7-1ubuntu0.16.04.2) xenial-security; urgency=medium * SECURITY UPDATE: authentication bypass (LP: #1706900) - debian/patches/CVE-2016-9877.patch: fix password check in plugins-src/rabbitmq-mqtt/src/rabbit_mqtt_processor.erl, add test to plugins-src/rabbitmq-mqtt/test/src/com/rabbitmq/mqtt/test/MqttTest.java, fix URL in plugins-src/rabbitmq-mqtt/test/Makefile. - CVE-2016-9877 -- Marc Deslauriers Thu, 27 Jul 2017 14:36:17 -0400 ** Changed in: rabbitmq-server (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1706900 Title: CVE-2016-9877 RabbitMQ authentication vulnerability Status in RabbitMQ: Fix Released Status in rabbitmq-server package in Ubuntu: Fix Released Status in rabbitmq-server source package in Trusty: Fix Released Status in rabbitmq-server source package in Xenial: Fix Released Bug description: https://pivotal.io/security/cve-2016-9877 "MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected." Affects RabbitMQ "3.x versions prior to 3.5.8" Ubuntu's Xenial repos are currently offering 3.5.7-1ubuntu0.16.04.1, and according to its changelog, Pivotal's fix for CVE-2016-9877 has not been included. To manage notifications about this bug go to: https://bugs.launchpad.net/rabbitmq/+bug/1706900/+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 1707015] Re: image composite functions not working in php
This bug was fixed in the package imagemagick - 8:6.7.7.10-6ubuntu3.9 --- imagemagick (8:6.7.7.10-6ubuntu3.9) trusty-security; urgency=medium * SECURITY REGRESSION: image composite function regression (LP: #1707015) - disabled the following patches which cause issue: 0224-Ensure-token-does-not-overflow.patch, 0225-Fix-off-by-one-error-when-checking-token-length.patch, 0226-Use-proper-cast.patch. -- Marc Deslauriers Mon, 31 Jul 2017 07:24:18 -0400 ** Changed in: imagemagick (Ubuntu Trusty) Status: In Progress => Fix Released ** Changed in: imagemagick (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1707015 Title: image composite functions not working in php Status in imagemagick package in Ubuntu: Invalid Status in imagemagick source package in Trusty: Fix Released Status in imagemagick source package in Xenial: Fix Released Status in imagemagick package in Debian: Unknown Bug description: We use php-imagick to make image compositions on our servers. On July 25 we got an upgrade of imagemagick, from 6.8.9.9-7ubuntu5.7 to 8:6.8.9.9-7ubuntu5.8. After that upgrade our webservers, using the php imagick bindings, stopped making composites. The composite images just have the background layer showing, with no overlay layer composited on top. In PHP there are no errors or exceptions, and other imagick functions work fine. Reading images, scaling, making new images, rendering to bytes, all work fine. It is only the composite functions, in php bindings, that are not working. I downgraded our webservers to imagemagick 6.8.9.9-7ubuntu5, which is still available in the ubuntu archives, and the php composite functions started working again. 6.8.9.9-7ubuntu5.7 is no longer available in the archives (http://security.ubuntu.com/ubuntu/pool/main/i/imagemagick/). A test script to reproduce the bug is attached to this ticket. On version 6.8.9.9-7ubuntu5 this will show the ubuntu logo over a gray background. On the latest version, 6.8.9.9-7ubuntu5.8, this will show garbled fragments of the ubuntu logo over gray background, or perhaps just an empty gray background. This bug was identified on Ubuntu 16.04.2 LTS as a result of an automatic upgrade from ubuntu security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1707015/+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 1707060] Re: [SRU] New stable micro release 2.32 and 2.33
This bug was fixed in the package snapcraft - 2.33+17.10 --- snapcraft (2.33+17.10) artful; urgency=medium [ Sergio Schvezov ] * tests: reduce the amount of test code in test_meta (#1391) * meta: bash completion support (#1390) * tests: fix issues with python 3.6 (#1398) (LP: #1699009) * cleanbuild: ensure we enter a shell on failures on --debug (#1404) * tests: do not break a systems `bzr whoami` (#1357) * snap: remove completer entry (#1409) * core: minimal cross OS support. (#1413) * core: a clean command should clean. (#1416) * nodejs plugin: copy the content of out of tree symlinks (#1418) * tests: adapt opencv's test expectations (#1426) * New upstream release (LP: #1707060) [ Zygmunt Krynicki ] * pluginhandler: don't clobber path on local import failure (#1361) [ Paolo Pisati ] * core: use the correct kernel arch for s390 (#1376) [ Tim Süberkrüb ] * core: support yaml merge tags (#1384) [ roxd ] * schema: blank version should not be allowed in snapcraft.yaml (#1379) [ Paolo Pisati ] * kernel plugin: add a default target per powerpc, ppc64el and s390x (#1377) [ Rex Tsai ] * tests: mock download for rustup in the x-compile test. (#1396) [ Evan Dandrea ] * file_utils: handle I/O errors in os.link (#1369) * python plugin: correct capitalisation for PyPI. (#1401) * python plugin: better explain dependency link processing (#1402) [ Leo Arias ] * python plugin: output json in pip list (#1393) * tests: allow to filter tests in docker (#1375) * tests: document the test suites in the snapcraft repo (#1394) * recording: rename the file to manifest.yaml (#1406) * pluginhandler: check for collisions only in existing files (#1405) * tests: run the tests in travis using LXD containers (#1415) * tests: build the snapcraft snap in travis tests (#1411) * ci: remove the old script to run with lxc (#1422) [ Christian Dywan ] * cli: proper parsing of hidden options (#1378) * core: clean the container on a full clean (#1372) * lxd: do not assume user ID of 1000 for raw.idmap (#1385) * autotools plugin: Enable cross-compilation support (#1383) * lxd: distingish FileNotFoundError for when not installed (#1400) * waf plugin: enable cross-compilation support (#1397) * ci: wait for apt/dpkg lock when setting lxd up (#1421) * lxd: stop setting `$HOME` in containers (#1408) * lxd: only remove container if one exists (#1403) [ Simon Davy ] * meta: add support for `reload-command` (#1373) -- Sergio Schvezov Thu, 27 Jul 2017 20:19:01 + ** Changed in: snapcraft (Ubuntu Artful) 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/1707060 Title: [SRU] New stable micro release 2.32 and 2.33 Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: New Status in snapcraft source package in Zesty: New Status in snapcraft source package in Artful: Fix Released Bug description: This is an SRU bug to release 2.32 and 2.33 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.32 and https://launchpad.net/snapcraft/+milestone/2.33; and https://github.com/snapcore/snapcraft/milestone/7?closed=1 and https://github.com/snapcore/snapcraft/milestone/8?closed=1 Information about 2.32 can be found on https://forum.snapcraft.io/t /welcome-snapcraft-2-32/1163?u=sergiusens and 2.33 (TBD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1707060/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the sy
[Group.of.nepali.translators] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** 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/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: Fix Released Status in apt source package in Yakkety: Won't Fix 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
[Group.of.nepali.translators] [Bug 1694697] Re: build-depends keeps OR flag if end of or group is ignored
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** 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/1694697 Title: build-depends keeps OR flag if end of or group is ignored Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Bug description: [Impact] If the last alternative(s) of an Or group is ignored, because it does not match an architecture list, we would end up keeping the or flag, effectively making the next AND an OR. For example, when parsing (on amd64): debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386] => debhelper (>= 9), libnacl-dev | Which can cause python-apt and apt-get build-dep to crash. Even worse: debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar => debhelper (>= 9), libnacl-dev [amd64] | foobar [Test case] On amd64: cat > segv.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy] Standards-Version: 3.9.8 EOF cat > failure.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy], a-non-existing-package Standards-Version: 3.9.8 EOF (1) apt-get build-dep -s ./segv.dsc should succeed instead of crash (2) apt-get build-dep -s ./failure.dsc should complain about "Depends: a-non-existing-package but it is not installable" instead of succeeding. This is the same test as run by CI and autopkgtests, so if they pass the tests passed. You can also run apt-get build-dep -s dq for a real life example that should not segfault. [Regression Potential] apt-get build-dep and friends can now fail where they succeeded previously for packages that employ architecture-limited alternatives in their build depends, as in the second example given above, because now additional packages need to be installed (which is correct, though). [Other info] By setting the previous alternatives Or flag to the current Or flag if the current alternative is ignored, we solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694697/+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 1649616] Re: Keystone Token Flush job does not complete in HA deployed environment
** Changed in: tripleo Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649616 Title: Keystone Token Flush job does not complete in HA deployed environment Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in Ubuntu Cloud Archive newton series: Fix Released Status in Ubuntu Cloud Archive ocata series: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Identity (keystone) newton series: In Progress Status in OpenStack Identity (keystone) ocata series: In Progress Status in puppet-keystone: Triaged Status in tripleo: Fix Released Status in keystone package in Ubuntu: In Progress Status in keystone source package in Xenial: Fix Released Status in keystone source package in Yakkety: Fix Released Status in keystone source package in Zesty: Fix Released Bug description: [Impact] * The Keystone token flush job can get into a state where it will never complete because the transaction size exceeds the mysql galara transaction size - wsrep_max_ws_size (1073741824). [Test Case] 1. Authenticate many times 2. Observe that keystone token flush job runs (should be a very long time depending on disk) >20 hours in my environment 3. Observe errors in mysql.log indicating a transaction that is too large Actual results: Expired tokens are not actually flushed from the database without any errors in keystone.log. Only errors appear in mysql.log. Expected results: Expired tokens to be removed from the database [Additional info:] It is likely that you can demonstrate this with less than 1 million tokens as the >1 million token table is larger than 13GiB and the max transaction size is 1GiB, my token bench-marking Browbeat job creates more than needed. Once the token flush job can not complete the token table will never decrease in size and eventually the cloud will run out of disk space. Furthermore the flush job will consume disk utilization resources. This was demonstrated on slow disks (Single 7.2K SATA disk). On faster disks you will have more capacity to generate tokens, you can then generate the number of tokens to exceed the transaction size even faster. Log evidence: [root@overcloud-controller-0 log]# grep " Total expired" /var/log/keystone/keystone.log 2016-12-08 01:33:40.530 21614 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1082434 2016-12-09 09:31:25.301 14120 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1084241 2016-12-11 01:35:39.082 4223 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1086504 2016-12-12 01:08:16.170 32575 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1087823 2016-12-13 01:22:18.121 28669 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1089202 [root@overcloud-controller-0 log]# tail mysqld.log 161208 1:33:41 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161208 1:33:41 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161209 9:31:26 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161209 9:31:26 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161211 1:35:39 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161211 1:35:40 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161212 1:08:16 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161212 1:08:17 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161213 1:22:18 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161213 1:22:19 [ERROR] WSREP: rbr write fail, data_len: 0, 2 Disk utilization issue graph is attached. The entire job in that graph takes from the first spike is disk util(~5:18UTC) and culminates in about ~90 minutes of pegging the disk (between 1:09utc to 2:43utc). [Regression Potential] * Not identified To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1649616/+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 1706195] Re: whoopsie can start before network-manager during boot
This bug was fixed in the package whoopsie - 0.2.55.2 --- whoopsie (0.2.55.2) zesty-proposed; urgency=medium * Modify the whoopsie service file to wants=networking-online.target too. (LP: #1706195) -- Brian Murray Tue, 25 Jul 2017 13:01:28 -0700 ** Changed in: whoopsie (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/1706195 Title: whoopsie can start before network-manager during boot Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Zesty: Fix Released Bug description: [Impact] whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker. [Test Case] 1) Boot a system with the old version of whoopsie 2) Run 'systemctl status whoopsie' 3) Observe: Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/whoopsie/lock Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state: Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline With the version of whoopsie in -proposed you'll see the following: Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/whoopsie/lock Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 [Regression Potential] If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports. Original Description whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. A fix was attempted by changing the service file to include "After=network-online.target" but this was insufficient. The following messages demonstrate the failure, if whoopsie were to start after network-manager we would not see them: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+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 1706195] Re: whoopsie can start before network-manager during boot
This bug was fixed in the package whoopsie - 0.2.52.5 --- whoopsie (0.2.52.5) xenial-proposed; urgency=medium * Modify the whoopsie service file to wants=networking-online.target too. (LP: #1706195) -- Brian Murray Tue, 25 Jul 2017 13:08:46 -0700 ** Changed in: whoopsie (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/1706195 Title: whoopsie can start before network-manager during boot Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Zesty: Fix Released Bug description: [Impact] whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker. [Test Case] 1) Boot a system with the old version of whoopsie 2) Run 'systemctl status whoopsie' 3) Observe: Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/whoopsie/lock Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state: Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline With the version of whoopsie in -proposed you'll see the following: Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/whoopsie/lock Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 [Regression Potential] If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports. Original Description whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. A fix was attempted by changing the service file to include "After=network-online.target" but this was insufficient. The following messages demonstrate the failure, if whoopsie were to start after network-manager we would not see them: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+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 1691489] Re: fstab entries written by cloud-config may not be mounted
This bug was fixed in the package cloud-init - 0.7.9-231-g80bf98b9-0ubuntu1 --- cloud-init (0.7.9-231-g80bf98b9-0ubuntu1) artful; urgency=medium * New upstream snapshot. - tests: remove 'yakkety' from releases as it is EOL. - systemd: make systemd-fsck run after cloud-init.service (LP: #1691489) - tests: Add initial tests for EC2 and improve a docstring. - locale: Do not re-run locale-gen if provided locale is system default. - archlinux: fix set hostname usage of write_file. [Joshua Powers] (LP: #1705306) - sysconfig: support subnet type of 'manual'. - Drop rand_str() usage in DNS redirection detection [Bob Aman] (LP: #1088611) -- Scott Moser Mon, 31 Jul 2017 09:47:34 -0400 ** Changed in: cloud-init (Ubuntu Artful) 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/1691489 Title: fstab entries written by cloud-config may not be mounted Status in cloud-init: Confirmed 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 Status in cloud-init source package in Artful: Fix Released Bug description: As reported in bug 1686514, sometimes /mnt will not get mounted when re-delpoying or stopping-then-starting a Azure vm of L32S. This is probably a more generic issue, I suspect shown due to the speed of disks on these systems. Related bugs: * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1691489/+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 1707285] Re: linux-azure: Update Hyper-V support
** Also affects: linux-azure (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/1707285 Title: linux-azure: Update Hyper-V support Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Bug description: Hyper-V support is moving very fast in upstream and the following changes were requested by MS: https://github.com/dcui/linux/compare/dcbb774667213607b83cf0cc193f2f27b9dd0a94...dcui:decui /upstream-ubuntu/master-next To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1707285/+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 1598316] Re: gtk2-engines-murrine desktop text shadow problem
** Changed in: gtk2-engines-murrine (Debian) 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/1598316 Title: gtk2-engines-murrine desktop text shadow problem Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in gtk2-engines-murrine source package in Xenial: Fix Released Status in gtk2-engines-murrine package in Debian: Fix Released Bug description: Impact == https://launchpad.net/ubuntu/+source/gtk2-engines-murrine/0.98.2-0ubuntu2.1 The above SRU caused a major regression: On Xfce, desktop icon labels are now badly misaligned. This affects numix-gtk-theme which is included (but not as the default theme) with Xubuntu 16.04 LTS. Third- party affected themes include Arc and Vertex. Test Case = 1. In Xubuntu 16.04 LTS, open the Xfce menu in the top left corner of the screen. 2. Select Settings>Appearance 3. Select Numix. Do the desktop icon labels look ok or do they look like the screenshot posted in comment #17? Regression Potential This obviously re-opens bug 1294699 but that seems to be a fairly obscure bug. Who sets their default system theme to a bitmap font in 2016? That regression is outweighed by breaking several popular themes. Original Bug Report and Followup Upgraded my xubuntu 16.04 system on 01 Jul 2016. The apt update included an upgrade to gtk2-engines-murrine. However, after the upgrade and boot, the any desktop text, folder, launcher, etc. had a problem with the text and shadow being quite far apart. This bug affects themes that use the textstyle feature of the murrine engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has caja draw the desktop icons instead of xfdesktop, does not appear to be affected (or at least not nearly as noticeably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1598316/+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 1707015] Re: image composite functions not working in php
** Bug watch added: Debian Bug tracker #870273 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870273 ** Also affects: imagemagick (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870273 Importance: Unknown Status: Unknown -- 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/1707015 Title: image composite functions not working in php Status in imagemagick package in Ubuntu: Invalid Status in imagemagick source package in Trusty: In Progress Status in imagemagick source package in Xenial: In Progress Status in imagemagick package in Debian: Unknown Bug description: We use php-imagick to make image compositions on our servers. On July 25 we got an upgrade of imagemagick, from 6.8.9.9-7ubuntu5.7 to 8:6.8.9.9-7ubuntu5.8. After that upgrade our webservers, using the php imagick bindings, stopped making composites. The composite images just have the background layer showing, with no overlay layer composited on top. In PHP there are no errors or exceptions, and other imagick functions work fine. Reading images, scaling, making new images, rendering to bytes, all work fine. It is only the composite functions, in php bindings, that are not working. I downgraded our webservers to imagemagick 6.8.9.9-7ubuntu5, which is still available in the ubuntu archives, and the php composite functions started working again. 6.8.9.9-7ubuntu5.7 is no longer available in the archives (http://security.ubuntu.com/ubuntu/pool/main/i/imagemagick/). A test script to reproduce the bug is attached to this ticket. On version 6.8.9.9-7ubuntu5 this will show the ubuntu logo over a gray background. On the latest version, 6.8.9.9-7ubuntu5.8, this will show garbled fragments of the ubuntu logo over gray background, or perhaps just an empty gray background. This bug was identified on Ubuntu 16.04.2 LTS as a result of an automatic upgrade from ubuntu security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1707015/+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 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. I've confirmed that the issue is as you describe in Xenial. Trusty pre- dates the change to locking in ntp.if-up, so is consistent. Zesty is also consistent in using flock in both places, as is Artful. So this bug affects only Xenial. In order to understand the importance of this bug, please could you explain why you're using both ntp and ntpdate? ntpdate isn't installed by default on Xenial, and shouldn't be required in the normal case because ntp defaults to "-g". So you could work around this bug by just removing the ntpdate package. Is there a particular reason that this won't work in your case? ** Also affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ntp (Ubuntu) Status: New => Fix Released ** Changed in: ntp (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Unknown Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+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 1706991] Re: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected
** 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/1706991 Title: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Bug description: SRU Justification = [Impact] wifi throughput numbers are good when device is running in WLAN only mode. In STA+BT+BLE mode, we get expected wifi throughput numbers when BT device is not connected. However downlink throughput drops to 5-6 Mbps from 35+Mbps as soon as bluetooth keyboard is connected. [Fix] Enable UAPSD mode with some optimized parameters, so that wifi station can get Rx packets buffered by AP efficiently even if radio is shared with bluetooth [Test Case] Conducted throughput tests and confirmed throughput gets dropped by 60% to 65% as expected(not more than that) when bluetooth keyboard connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706991/+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 1704964] Re: linux-hwe-edge: 4.11.0-12.17~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Andy Whitcroft (apw) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1704961 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Monday, 31. July 2017 09:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1704961 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Monday, 31. July 2017 09:00 UTC + phase: Uploaded -- 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/1704964 Title: linux-hwe-edge: 4.11.0-12.17~16.04.1 -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: Confirmed 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: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1704961 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704964/+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 1705276] Re: linux-gke: 4.4.0-1023.23 -proposed tracker
4.4.0-1023.23 - gke Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in x86_64 (gke): libhugetlbfs - 1 failed (brk_near_huge bug 1653597), Killed by signal 15, bad configuration 3 ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1705276 Title: linux-gke: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1705270 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705276/+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 1705742] Re: linux-gcp: 4.10.0-1003.3 -proposed tracker
No bug was tagged with verification-needed this cycle. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1705742 Title: linux-gcp: 4.10.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.10.0-1003.3 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705742/+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 1705275] Re: linux-aws: 4.4.0-1027.36 -proposed tracker
Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in x86_64 (aws): ebizzy - failed on one instance but passed on the other two libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 15, bad configuration 3 ubuntu_lxc - Failed creating ubuntu-cloud container due to too many open files on 1 of 3 testing instances ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1705275 Title: linux-aws: 4.4.0-1027.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1705270 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705275/+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
