[Group.of.nepali.translators] [Bug 1837620] Re: xenial/linux-azure-edge: 4.15.0-1053.58 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge - phase: Ready for Packaging - phase-changed: Thursday, 01. August 2019 08:36 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 02. August 2019 05:20 UTC reason: - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa meta:queued variant: debs -- 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/1837620 Title: xenial/linux-azure-edge: 4.15.0-1053.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid 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 verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge phase: Holding before Promote to Proposed phase-changed: Friday, 02. August 2019 05:20 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837620/+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 1837620] Re: xenial/linux-azure-edge: 4.15.0-1053.58 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge phase: Ready for Packaging phase-changed: Thursday, 01. August 2019 08:36 UTC reason: - prepare-package-meta: Pending -- version not specified + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- 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/1837620 Title: xenial/linux-azure-edge: 4.15.0-1053.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Confirmed 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 verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge phase: Ready for Packaging phase-changed: Thursday, 01. August 2019 08:36 UTC reason: prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837620/+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 1836208] Re: wslusc screws fonts
This bug was fixed in the package wslu - 2.3.0-1ubuntu1 --- wslu (2.3.0-1ubuntu1) eoan; urgency=medium * debian/control: Set Vcs-* fields * New upstream release - Stop changing terminal font when running wsl* commands (LP: #1836208) * Refresh patches * debian/rules: Run tests in WSL only -- Balint Reczey Thu, 01 Aug 2019 12:54:30 +0200 ** Changed in: wslu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836208 Title: wslusc screws fonts Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Disco: New Bug description: Using W10 r18932 Typing 'wslusc' on a WSL2/Ubuntu 18.04 uptodate instance leads to have the Ubuntu instance font changing/being screwed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1836208/+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 1838346] Re: Support Japanese new era "令和 (Reiwa)"
Fixed in unstable/eoan AFAICT. ** Changed in: anthy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1838346 Title: Support Japanese new era "令和 (Reiwa)" Status in anthy package in Ubuntu: Fix Released Status in anthy source package in Xenial: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） [Impact] Users who run Ubuntu in Japanese. [Test cases] == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. 3) Type in 'reiwa' 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) 5) Type in the following strings, and verify that the options are provided in the input method: * "れいわ"(reiwa) => "令和" * "れいわ"(reiwa) => "㋿" * "２０１８ねん"(2018nenn) => "平成三十年" * "２０１９ねん"(2019nenn) => "平成三十一年" * "２０１９ねん"(2019nenn) => "令和元年" * "２０２０ねん"(2020nenn) => "令和二年" [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anthy/+bug/1838346/+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 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -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/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Packaging - phase-changed: Tuesday, 30. July 2019 17:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 01. August 2019 16:11 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:building variant: debs -- 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/1837600 Title: xenial/linux-fips: 4.4.0-1016.21 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837600/+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 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+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 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Release - phase-changed: Thursday, 01. August 2019 14:45 UTC + phase: Complete + phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published variant: debs -- 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+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 1838322] Re: Support Japanese new era "令和 (Reiwa)"
** Also affects: icu (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/1838322 Title: Support Japanese new era "令和 (Reiwa)" Status in icu package in Ubuntu: Fix Released Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] Unicode data embedded into icu should include REIWA like it includes HEISEI. == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1838322/+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 1838327] Re: Support Japanese new era "令和 (Reiwa)"
** Also affects: glibc (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/1838327 Title: Support Japanese new era "令和 (Reiwa)" Status in glibc package in Ubuntu: Fix Released Status in glibc source package in Xenial: New Status in glibc source package in Bionic: New Status in glibc source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1838327/+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 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Release phase-changed: Thursday, 01. August 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+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 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
** Changed in: chrony (Ubuntu Disco) 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/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Fix Released Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- Checking last eoan merge I realized that some tests were failing for chrony: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 But eoan ran autopkgtests okay when the trigger was chrony/3.5-2ubuntu2 (this last merge): http://autopkgtest.ubuntu.com/packages/chrony/eoan/amd64 Despite having failed for the previous 12 times (eoan). Now, for the first time, we have the same failure for disco: http://autopkgtest.ubuntu.com/packages/chrony/disco/amd64 http://bit.ly/2LpMx4G """ make: Leaving directory '/tmp/autopkgtest.pBHSAl/build.WCD/src/test/simulation/clknetsim' ... 110-chronyc PASS 111-knownclient FAIL 112-port FAIL 121-orphan PASS ... SUMMARY: TOTAL 50 PASSED 48 FAILED 2(111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 265) """ And I'm able to reproduce locally: """ (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: non-default settings: starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking mean/min incoming/outgoing packet interval: node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK checking clock sync time, max/rms time/freq error: node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK checking port numbers in packet log: node 1: BAD node 2: BAD network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node
[Group.of.nepali.translators] [Bug 1838627] [NEW] AppArmor onexec transition causes WARN kernel stack trace
Public bug reported: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!()->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: John Johansen (jjohansen) Status: Confirmed ** Tags: xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: linux (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/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the
[Group.of.nepali.translators] [Bug 1633120] Re: [SRU] Nova scheduler tries to assign an already-in-use SRIOV QAT VF to a new instance
Mitaka not backportable so abandoning: $ git-deps -e mitaka-eol 5c5a6b93a07b0b58f513396254049c17e2883894^! c2c3b97259258eec3c98feabde3b411b519eae6e $ git-deps -e mitaka-eol c2c3b97259258eec3c98feabde3b411b519eae6e^! a023c32c70b5ddbae122636c26ed32e5dcba66b2 74fbff88639891269f6a0752e70b78340cf87e9a e83842b80b73c451f78a4bb9e7bd5dfcebdefcab 1f259e2a9423a4777f79ca561d5e6a74747a5019 b01187eede3881f72addd997c8fd763ddbc137fc 49d9433c62d74f6ebdcf0832e3a03e544b1d6c83 ** Changed in: cloud-archive/mitaka Status: Triaged => Won't Fix ** Changed in: nova (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1633120 Title: [SRU] Nova scheduler tries to assign an already-in-use SRIOV QAT VF to a new instance Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Won't Fix Status in Ubuntu Cloud Archive ocata series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Released Status in Ubuntu Cloud Archive rocky series: Fix Released Status in Ubuntu Cloud Archive stein series: Fix Released Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ocata series: Fix Committed Status in OpenStack Compute (nova) pike series: Fix Committed Status in OpenStack Compute (nova) queens series: Fix Committed Status in OpenStack Compute (nova) rocky series: Fix Committed Status in nova package in Ubuntu: Fix Released Status in nova source package in Xenial: Won't Fix Status in nova source package in Bionic: Fix Released Status in nova source package in Cosmic: Fix Released Status in nova source package in Disco: Fix Released Status in nova source package in Eoan: Fix Released Bug description: [Impact] This patch is required to prevent nova from accidentally marking pci_device allocations as deleted when it incorrectly reads the passthrough whitelist [Test Case] * deploy openstack (any version that supports sriov) * single compute configured for sriov with at least once device in pci_passthrough_whitelist * create a vm and attach sriov port * remove device from pci_passthrough_whitelist and restart nova-compute * check that pci_devices allocations have not been marked as deleted [Regression Potential] None anticipated Upon trying to create VM instance (Say A) with one QAT VF, it fails with the following error i.e., “Requested operation is not valid: PCI device :88:04.7 is in use by driver QEMU, domain instance-0081”. Please note that, PCI device :88:04.7 is already being assigned to another VM (Say B) . We have installed openstack-mitaka release on CentO7 system. It has two Intel QAT devices. There are 32 VF devices available per QAT Device/DH895xCC device Out of 64 VFs, only 8 VFs are allocated (to VM instances) and rest should be available. But the nova scheduler tries to assign an already-in-use SRIOV VF to a new instance and instance fails. It appears that the nova database is not tracking which VF's have already been taken. But if I shut down VM B instance, then other instance VM A boots up and vice-versa. Note that, both the VM instances cannot run simultaneously because of the aforesaid issue. We should always be able to create as many instances with the requested PCI devices as there are available VFs. Please feel free to let me know if additional information is needed. Can anyone please suggest why it tries to assign same PCI device which has been assigned already? Is there any way to resolve this issue? Thank you in advance for your support and help. [root@localhost ~(keystone_admin)]# lspci -d:435 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT 88:00.0 Co-processor: Intel Corporation DH895XCC Series QAT [root@localhost ~(keystone_admin)]# [root@localhost ~(keystone_admin)]# lspci -d:443 | grep "QAT Virtual Function" | wc -l 64 [root@localhost ~(keystone_admin)]# [root@localhost ~(keystone_admin)]# mysql -u root nova -e "SELECT hypervisor_hostname, address, instance_uuid, status FROM pci_devices JOIN compute_nodes oncompute_nodes.id=compute_node_id" | grep :88:04.7 localhost :88:04.7e10a76f3-e58e-4071-a4dd-7a545e8000deallocated localhost :88:04.7c3dbac90-198d-4150-ba0f-a80b912d8021allocated localhost :88:04.7c7f6adad-83f0-4881-b68f-6d154d565ce3allocated localhost.nfv.benunets.com :88:04.7 0c3c11a5-f9a4-4f0d-b120-40e4dde843d4allocated [root@localhost ~(keystone_admin)]# [root@localhost ~(keystone_admin)]# grep -r e10a76f3-e58e-4071-a4dd-7a545e8000de /etc/libvirt/qemu /etc/libvirt/qemu/instance-0081.xml: e10a76f3-e58e-4071-a4dd-7a545e8000de
[Group.of.nepali.translators] [Bug 1629715] Re: [SRU] usb-creator-kde shows the install popup after a few seconds of launching without any input
This bug was fixed in the package usb-creator - 0.3.5ubuntu18.04.2 --- usb-creator (0.3.5ubuntu18.04.2) bionic; urgency=medium * Move progress dialog setup to the install method on the KDE frontend. Thanks to Paul Worrall for the patch! (LP: #1629715) -- Walter Lapchynski Tue, 16 Jul 2019 10:40:51 -0700 ** Changed in: usb-creator (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: usb-creator (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/1629715 Title: [SRU] usb-creator-kde shows the install popup after a few seconds of launching without any input Status in usb-creator package in Ubuntu: Fix Released Status in usb-creator source package in Xenial: Fix Released Status in usb-creator source package in Bionic: Fix Released Status in usb-creator source package in Cosmic: Won't Fix Status in usb-creator source package in Disco: Fix Released Status in usb-creator source package in Eoan: Fix Released Bug description: [SRU] [Impact] Unlike usb-creator-gtk, which has a different codebase, usb-creator- kde has long been non-functional, getting stuck immediately upon launching. This means that for Kubuntu, post-18.04 Lubuntu, and any user who chooses to use usb-creator-kde, it is useless. There is code to setup a progress dialog for when a USB is being written to, but it is in the class initialization, so it displays immediately. This moves that to the actual install method so it doesn't appear until the user clicks the button the perform the USB install. [Test Case] To reproduce the bug, simply launch usb-creator-kde (Startup Disk Creator in the menu). If the bug is present, the installation popup immediately displays, rendering the program unusable. If the bug is NOT present, the program should wait for the ISO and target to be specified and the button to perform the install to be clicked before the installation popup shows. It is highly recommended that a USB install is performed as part of the testing if the bug is not present. See below. [Regression Potential] The patch is small, applies cleanly, and does nothing to change logic. It merely moves logic around. There should be no reason why this should cause any sort of regression. The most likely cause of a regression would be the fact that the program has been unusable for so long, it hasn't seen a lot of use and, as such, its quality is a bit unknown. I would hope anyone testing would ensure that the basic function is there. == [Original Description] STEPS TO REPRODUCE 1. Launch usb-creator-kde (Startup Disk Creator) EXPECTED RESULTS Application launches normally, waiting for the ISO and target before installing. ACTUAL RESULTS Without any input, the installation popup immediately shows up, making the program unusable. AFFECTED VERSIONS 0.3.2 0.3.5 (possibly earlier versions, but couldn't install in trusty) NOTES & WORKAROUND usb-creator-gtk is unaffected by this bug Tracked by Lubuntu here: https://phab.lubuntu.me/T51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1629715/+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 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
This bug was fixed in the package ubuntu-meta - 1.417.3 --- ubuntu-meta (1.417.3) bionic; urgency=medium * Added dbus-x11 to wsl-recommends (LP: #1837466) -- Balint Reczey Wed, 24 Jul 2019 01:21:39 +0200 ** Changed in: ubuntu-meta (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/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Released Status in ubuntu-meta source package in Disco: Fix Released Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+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 1837620] Re: xenial/linux-azure-edge: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:24 UTC + phase: Ready for Packaging + phase-changed: Thursday, 01. August 2019 08:36 UTC reason: - prepare-package: Holding -- waiting for master bug - prepare-package-meta: Holding -- waiting for master bug + prepare-package-meta: Pending -- version not specified variant: debs -- 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/1837620 Title: xenial/linux-azure-edge: -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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Confirmed 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 verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1837622 packages: meta: linux-meta-azure-edge phase: Ready for Packaging phase-changed: Thursday, 01. August 2019 08:36 UTC reason: prepare-package-meta: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837620/+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 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -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/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Wednesday, 31. July 2019 13:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 01. August 2019 08:35 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs -- 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/1837622 Title: xenial/linux-azure: 4.15.0-1053.58 -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 prepare-package-signed 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837622/+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 1629715] Re: [SRU] usb-creator-kde shows the install popup after a few seconds of launching without any input
This bug was fixed in the package usb-creator - 0.3.5ubuntu19.04.2 --- usb-creator (0.3.5ubuntu19.04.2) disco; urgency=medium * Move progress dialog setup to the install method on the KDE frontend. Thanks to Paul Worrall for the patch! (LP: #1629715) -- Walter Lapchynski Tue, 16 Jul 2019 10:44:30 -0700 ** Changed in: usb-creator (Ubuntu Disco) 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/1629715 Title: [SRU] usb-creator-kde shows the install popup after a few seconds of launching without any input Status in usb-creator package in Ubuntu: Fix Released Status in usb-creator source package in Xenial: Fix Committed Status in usb-creator source package in Bionic: Fix Committed Status in usb-creator source package in Cosmic: Won't Fix Status in usb-creator source package in Disco: Fix Released Status in usb-creator source package in Eoan: Fix Released Bug description: [SRU] [Impact] Unlike usb-creator-gtk, which has a different codebase, usb-creator- kde has long been non-functional, getting stuck immediately upon launching. This means that for Kubuntu, post-18.04 Lubuntu, and any user who chooses to use usb-creator-kde, it is useless. There is code to setup a progress dialog for when a USB is being written to, but it is in the class initialization, so it displays immediately. This moves that to the actual install method so it doesn't appear until the user clicks the button the perform the USB install. [Test Case] To reproduce the bug, simply launch usb-creator-kde (Startup Disk Creator in the menu). If the bug is present, the installation popup immediately displays, rendering the program unusable. If the bug is NOT present, the program should wait for the ISO and target to be specified and the button to perform the install to be clicked before the installation popup shows. It is highly recommended that a USB install is performed as part of the testing if the bug is not present. See below. [Regression Potential] The patch is small, applies cleanly, and does nothing to change logic. It merely moves logic around. There should be no reason why this should cause any sort of regression. The most likely cause of a regression would be the fact that the program has been unusable for so long, it hasn't seen a lot of use and, as such, its quality is a bit unknown. I would hope anyone testing would ensure that the basic function is there. == [Original Description] STEPS TO REPRODUCE 1. Launch usb-creator-kde (Startup Disk Creator) EXPECTED RESULTS Application launches normally, waiting for the ISO and target before installing. ACTUAL RESULTS Without any input, the installation popup immediately shows up, making the program unusable. AFFECTED VERSIONS 0.3.2 0.3.5 (possibly earlier versions, but couldn't install in trusty) NOTES & WORKAROUND usb-creator-gtk is unaffected by this bug Tracked by Lubuntu here: https://phab.lubuntu.me/T51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1629715/+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 1698367] Re: Rebase linux-azure to 4.11
** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-azure (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/1698367 Title: Rebase linux-azure to 4.11 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: The support for Hyper-V and Azure is under heavy development and due to this reason it's necessary to keep the Azure kernel as closest to upstream as possible in order to get access to the latest features and bug fixes. Fix: Rebase the Azure kernel to the latest 4.11 artful kernel in proposed. Testcase: It's necessary to run a smoke test and check if any performance regression was caused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1698367/+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 1699157] Re: Re-enable -extra package for linux-azure
** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-azure (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/1699157 Title: Re-enable -extra package for linux-azure Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: It's necessary to ship some drivers that will not be included by default. Fix: Re-enable the -extra package for linux-azure. Testcase: The -extra package should be built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1699157/+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 1706165] Re: linux-azure: disable unused modules in the -extra package
** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1706165 Title: linux-azure: disable unused modules in the -extra package Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: Currently the linux-image-extra-*-azure package contains many unused modules. Fix: Remove modules that are not use in Azure. Testcase: not applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1706165/+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 1812123] Re: Upstream Commits Needed for DPDK on Azure
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1812123
Title:
Upstream Commits Needed for DPDK on Azure
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Bug description:
The following two patches are related to multi-queue. They are needed
in the linux-azure kernels for DPDK to work properly on Azure.
b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")
Both commits have also been cc'd to upstream stable. Commit 5e3c420dcca5 is
in mainline as of v4.20. Commit b5679cebf780 is still in linux-next.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812123/+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
