[Group.of.nepali.translators] [Bug 1799614] Re: Use new media API
** No longer affects: snapd-glib (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Committed Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API
** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu) Status: New => Fix Released ** Changed in: snapd-glib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: snapd-glib (Ubuntu) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Cosmic) Status: New => In Progress ** Changed in: snapd-glib (Ubuntu Bionic) Status: New => Triaged ** Changed in: snapd-glib (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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Committed Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in snapd-glib source package in Xenial: Triaged Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: In Progress Bug description: snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) -- 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/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -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: Invalid 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: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Thursday, 17. January 2019 19:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+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 1767760] Re: plymouth timeout prevents x-server from correct initialization
** No longer affects: plymouth (Ubuntu Artful) ** Tags added: rls-bb-notfixing -- 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/1767760 Title: plymouth timeout prevents x-server from correct initialization Status in plymouth package in Ubuntu: New Status in plymouth source package in Xenial: New Status in plymouth source package in Bionic: New Bug description: After upgrading from plymouth_0.9.2-3ubuntu13.3 to plymouth_0.9.2-3ubuntu13.4 about 50% of all x-server initializations failed and Xorg crashed after entering fail-save-mode. A typical reason for this behaviour was that it could not acquire DRM interface /dev/dri/card0 not have been release before by plymouth after a time- out condition. Downgrading to plymouth_0.9.2-3ubuntu13.3 fixed the issue same as elongating the time-out-interval from 2.0 to at least 6.0 seconds in src/client/plymouth.c. Ubuntu 16.04.4 is running on a about 9-year-old notebook with an Intel Core 2 Duo U9400 @ 1.4 GHz CPU and a non-solid-state-disk. Its rather complex xkb configuration takes more than a second to compile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1767760/+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 1800945] Re: Add Ubuntu disco as as supported release
** Changed in: debootstrap (Ubuntu Bionic) 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/1800945 Title: Add Ubuntu disco as as supported release Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Trusty: Fix Committed Status in debootstrap source package in Xenial: Fix Committed Status in debootstrap source package in Bionic: Fix Released Status in debootstrap source package in Cosmic: Fix Released Bug description: Add Ubuntu disco 19.04 debootstrap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1800945/+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 1811855] Re: linux-snapdragon: 4.4.0-1107.112 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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: 1811846 - phase: Promote to Proposed -- release to Proposed in progress - phase-changed: Thursday, 17. January 2019 13:51 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Thursday, 17. January 2019 17:59 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + verification-testing: Ongoing -- testing in progress ** 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: 1811846 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Thursday, 17. January 2019 17:59 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Thursday, 17. January 2019 18:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing 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/1811855 Title: linux-snapdragon: 4.4.0-1107.112 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Promote to Proposed -- snap release to beta ready phase-changed: Thursday, 17. January 2019 18:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress
[Group.of.nepali.translators] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** No longer affects: apt (Ubuntu) ** No longer affects: apt (Ubuntu Xenial) ** No longer affects: apt (Ubuntu Artful) ** No longer affects: apt (Ubuntu Bionic) -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in menu package in Ubuntu: Fix Released Status in menu source package in Xenial: Fix Released Status in menu source package in Artful: Fix Released Status in menu source package in Bionic: Fix Released Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menu/+bug/1768905/+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 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** 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: 1811846 - phase: Packaging -- ready to package - phase-changed: Wednesday, 16. January 2019 22:33 UTC + phase: Packaging -- uploaded + phase-changed: Thursday, 17. January 2019 17:45 UTC reason: - prepare-package: Pending -- version not specified + promote-to-proposed: Ongoing -- builds not complete -- 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/1811851 Title: linux-aws: 4.4.0-1075.85 -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: 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: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New 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 -- kernel-stable-master-bug: 1811846 phase: Packaging -- uploaded phase-changed: Thursday, 17. January 2019 17:45 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+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 1573594] Re: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling
** Also affects: libmemcached (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libmemcached (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libmemcached (Ubuntu Disco) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: In Progress ** Also affects: libmemcached (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: libmemcached (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/1573594 Title: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling Status in libmemcached: New Status in libmemcached package in Ubuntu: In Progress Status in libmemcached source package in Trusty: In Progress Status in libmemcached source package in Xenial: In Progress Status in libmemcached source package in Bionic: In Progress Status in libmemcached source package in Cosmic: In Progress Status in libmemcached source package in Disco: In Progress Bug description: When connecting to a server using SASL, memcached_sasl_authenticate_connection() reads the list of supported mechanisms [1] from the server via the command PROTOCOL_BINARY_CMD_SASL_LIST_MECHS. The server's response is a string containing supported authentication mechanisms, which gets stored into the (uninitialized) destination buffer without null termination [2]. The buffer then gets passed to sasl_client_start [3] which treats it as a null-terminated string [4], reading uninitialized bytes in the buffer. As the buffer lives on the stack, an attacker that can put strings on the stack before the connection gets made, might be able to tamper with the authentication. [1] libmemcached/sasl.cc:174 [2] libmemcached/response.cc:619 [1] libmemcached/sasl.cc:231 [3] http://linux.die.net/man/3/sasl_client_start To manage notifications about this bug go to: https://bugs.launchpad.net/libmemcached/+bug/1573594/+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 1812166] Re: [SRU] Please accept ec2-hibinit-agent to supported releases
Hello Balint, or anyone else affected, Accepted ec2-hibinit-agent into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ec2 -hibinit-agent/1.0.0-0ubuntu1~18.10.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: ec2-hibinit-agent (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu) Status: New => Fix Released ** Changed in: ec2-hibinit-agent (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1812166 Title: [SRU] Please accept ec2-hibinit-agent to supported releases Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in ec2-hibinit-agent source package in Trusty: New Status in ec2-hibinit-agent source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Committed Status in ec2-hibinit-agent source package in Cosmic: Fix Committed Bug description: [Impact] The package is new to the releases and sets up EC2 on demand instances to hibernate on an ACPI sleep event. [Test Case] Please perform piuparts-like tests with the package and make sure that ec2-hibinit-agent service is started. On EC2 on demand instances that were configured to allow hibernation the hibinit-agent service prepares the system for enabling hibernation. On non EC2 on demand instances and on EC2 on demand instances where hibernation is not configures when launching the instance the service starts without error but does not prepare the system for being able to hibernate. [Regression Potential] Since the package is new it may not cause regressions by being broken. The package sets up a swap file on / reserving the size of the memory from the root partition. There is check in the service to ensure that there is enough space but the space left may not be enough for the proper operation of the system later. Users a warned on EC2 console to allocate a big enough root partition for the instance when instance hibernation is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1812166/+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 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed -- release to Proposed in progress - phase-changed: Thursday, 17. January 2019 10:22 UTC + bugs-spammed: true + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Thursday, 17. January 2019 14:22 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages copies requested + automated-testing: Pending -- Ready + certification-testing: Ongoing -- testing in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + verification-testing: Ongoing -- testing 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/1811846 Title: linux: 4.4.0-142.168 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to edge ready phase-changed: Thursday, 17. January 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Pending -- Ready certification-testing: Ongoing -- testing in progress promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel
[Group.of.nepali.translators] [Bug 1797990] Re: kdump fail due to an IRQ storm
** Also affects: linux (Ubuntu Disco) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Changed in: linux (Ubuntu Disco) 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/1797990 Title: kdump fail due to an IRQ storm Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] * A kexec/crash kernel might get stuck and fail to boot (for crash kernel, kdump fails to collect a crashdump) if a PCI device is buggy/stuck/looping and triggers a continuous flood of MSI(X) interrupts (that the kernel does not yet know about). * This fix allowed to obtain crashdumps when debugging a heavy-load scenario, in which a (heavy-loaded) network adapter wouldn't stop triggering MSI-X interrupts ever after panic()->kdump kicked in. * This fix disables MSI(X) in all PCI devices on early boot (this is OK as it's (re-)enabled normally later) with a kernel cmdline parameter (disabled by default). [Test Case] * A synthetic test-case is not yet available, however, this particular system/workload triggered the problem consistently, and it was used for development/testing. * We'll update this bug once a synthetic test-case is available; we're working on patching QEMU for this. * $ cat /proc/cmdline <...> pci=clearmsi $ dmesg | grep 'Clearing MSI' [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk) * The comparison of 'dmesg -t | sort' has been reviewed between option disabled/enabled on boot & kexec modes, and only expected differences found (MHz, PIDs, MIPS). [Regression Potential] * The potential area for regressions is early boot, particularly effects of applying quirks during PCI bus scan, which is changed/broader w/ these patches. * However, all quirks are applied based on PCI ID matching, so would only apply if actually targeting a new device. * Moreover, the new quirk is only applied based on a kernel cmdline parameter that is disabled by default, which constraints even more when this is actually in effect. [Other Info] * The patch series is still under review/discussion upstream, but it's relatively important for Ubuntu users at this point, and after internal discussions we decided to submit it for SRU. * These are links to the linux-pci archive with the patches [1, 2, 3] [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/ [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/ [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/ [Original Description] We have reports of a kdump failure in Ubuntu (in x86 machine) that was narrowed down to a MSI irq storm coming from a PCI network device. The bug manifests as a lack of progress in the boot process of the kdump kernel, and a storm of kernel messages like: [...] [ 342.265294] do_IRQ: 0.155 No irq handler for vector [ 342.266916] do_IRQ: 0.155 No irq handler for vector [ 347.258422] do_IRQ: 14053260 callbacks suppressed [...] The root cause of the issue is that the kdump kernel kexec process does not ensure PCI devices are reset and/or MSI capabilities are disabled, so a PCI device could produce a huge amount of PCI irqs which would take all the processing time for the CPU (specially since we restrict the kdump kernel to use one single CPU only). This was tested using upstream kernel version 4.18, and the problem reproduces. In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit [8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under high load on the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+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 1805497] Re: Snaps not included in image manifests
This bug was fixed in the package livecd-rootfs - 2.408.42 --- livecd-rootfs (2.408.42) xenial; urgency=medium [ Cody Shepherd ] * Backport adding snaps to image manifests (LP: #1805497) -- Steve Langasek Mon, 10 Dec 2018 10:21:47 -0800 ** Changed in: livecd-rootfs (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/1805497 Title: Snaps not included in image manifests Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Cosmic: New Bug description: [Impact] * Snaps are not included in manifests for cloud images for those releases where snaps are pre-seeded (Xenial & Bionic) * Snaps should appear in the manifests for (mf)diff purposes. * Note that this issue has been fixed already in Cosmic and newer. [Test Case] * Build Xenial or Bionic image and note that snaps are not included in the manifest. [Regression Potential] * Manifest could continue to be incorrect * Image build could fail [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805497/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
This bug was fixed in the package cups - 2.2.7-1ubuntu2.3 --- cups (2.2.7-1ubuntu2.3) bionic; urgency=medium * fix-handling-of-MaxJobTime.patch: Fix handling of MaxJobTime 0 (LP: #1804576) -- Dariusz Gadomski Wed, 12 Dec 2018 08:31:14 +0100 ** Changed in: cups (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: cups (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/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
This bug was fixed in the package cups - 2.2.8-5ubuntu1.2 --- cups (2.2.8-5ubuntu1.2) cosmic; urgency=medium * fix-handling-of-MaxJobTime.patch: Fix handling of MaxJobTime 0 (LP: #1804576) -- Dariusz Gadomski Wed, 12 Dec 2018 08:27:17 +0100 ** Changed in: cups (Ubuntu Cosmic) 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/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1811853] Re: linux-kvm: 4.4.0-1040.46 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 phase: Packaging -- packaging in progress phase-changed: Wednesday, 16. January 2019 07:35 UTC reason: prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet 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/1811853 Title: linux-kvm: 4.4.0-1040.46 -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: Invalid 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 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- kernel-stable-master-bug: 1811846 phase: Packaging -- packaging in progress phase-changed: Wednesday, 16. January 2019 07:35 UTC reason: prepare-package: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+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 1811855] Re: linux-snapdragon: 4.4.0-1107.112 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 - phase: Packaging -- packaging in progress - phase-changed: Wednesday, 16. January 2019 07:33 UTC + phase: Packaging -- uploaded + phase-changed: Thursday, 17. January 2019 09:48 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1811855 Title: linux-snapdragon: 4.4.0-1107.112 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 phase: Packaging -- uploaded phase-changed: Thursday, 17. January 2019 09:48 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811855/+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
