[Group.of.nepali.translators] [Bug 1838322] Re: Support Japanese new era "令和 (Reiwa)"
** Changed in: icu (Ubuntu Disco) Status: New => 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/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: Won't Fix 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 1838323] Re: Support Japanese new era "令和 (Reiwa)"
disco is EOL; this SRU will not be completed for that release. ** Changed in: unicode-data (Ubuntu Disco) Status: Fix Committed => 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/1838323 Title: Support Japanese new era "令和 (Reiwa)" Status in unicode-data package in Ubuntu: Fix Released Status in unicode-data source package in Xenial: Fix Committed Status in unicode-data source package in Bionic: Fix Committed Status in unicode-data source package in Disco: Won't Fix 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 include REIWA like it includes HEISEI. Reverse-build- depends need a rebuild to include the new data, followed by the following tests to make sure the data is taken into account. 1) Rebuild reverse-depends of unicode-data; check that they build fine (ie. no regressions due to unicode-data changes): Reverse-Build-Depends = * console-data * courier-unicode * cyrus-imapd * fntsample * fonttools * gucharmap * ibus * julia * libxmlada * node-unicode-data * node-unicode-property-aliases * node-unicode-property-aliases-ecmascript * node-unicode-property-value-aliases * node-unicode-property-value-aliases-ecmascript * node-unicode-tr51 * re2 * safeclib * slang2 * utf8proc * wcwidth * wine * wine-development 2) Using gucharmap, verify that the SQUARE ERA NAME REIWA glyph point exists (there may not be a glyph associated as that is font-dependent. == 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. Use fonts-noto-cjk to display the 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/unicode-data/+bug/1838323/+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 1633485] Re: Backport login throttling plugin to 5.6 and 5.7
This was fixed some time ago it seems: $ dpkg -l| grep mysql-server-5.7 ii mysql-server-5.75.7.30-0ubuntu0.16.04.1 amd64MySQL database server binaries and system database setup $ dpkg -L mysql-server-5.7 | grep control /usr/lib/mysql/plugin/connection_control.so ** Changed in: mysql-5.7 (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: mysql-5.7 (Ubuntu Yakkety) Status: Triaged => Invalid ** Changed in: mysql-5.7 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1633485 Title: Backport login throttling plugin to 5.6 and 5.7 Status in mysql-5.6 package in Ubuntu: Invalid Status in mysql-5.7 package in Ubuntu: Fix Released Status in mysql-5.6 source package in Precise: Invalid Status in mysql-5.7 source package in Precise: Invalid Status in mysql-5.6 source package in Trusty: Triaged Status in mysql-5.7 source package in Trusty: Invalid Status in mysql-5.6 source package in Xenial: Invalid Status in mysql-5.7 source package in Xenial: Fix Released Status in mysql-5.6 source package in Yakkety: Invalid Status in mysql-5.7 source package in Yakkety: Invalid Bug description: In MySQL 8.0 we (Oracle) are adding a plugin to rate-limit/throttle login attempts in order to stop brute-force attacks. Since this is a security mechanism that has been requested by users, we would also like to backport this plugin to MySQL 5.6 and 5.7. After consulting with Robie Basak (racb), we understand this change to be allowed in Ubuntu under the SRU process (Sect. 2.2, https://wiki.ubuntu.com/StableReleaseUpdates), but if there are any comments or objections, we'd like to hear them now. Impact == This functionality is implemented in a plugin. The plugin is not loaded, and the functionality will not be activated unless the DBA explicitly activates it. Regression potential The potential for regression is considered low for the following reasons: - The new functionality is in a plugin that 1) is not loaded by default, and 2) can be unloaded if it causes problems. - The change does not introduce new SQL syntax, and no existing syntax is affected. - The plugin is new, so it's not used by any other packages in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1633485/+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)"
disco is EOL; wontfix. ** Changed in: glibc (Ubuntu Disco) Status: New => 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/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: Won't Fix 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 1717382] Re: [Bug] Glibc: performance improvement patches
This is fixed in newer releases of Ubuntu, including 2 LTSes that have been released since this bug was filed. We have not found capacity to land this in Ubuntu 16.04 in 2.5 years; I'm therefore marking this wontfix which is more realistic. Users will get improved performance by upgrading to Ubuntu 18.04 or Ubuntu 20.04. ** Changed in: glibc (Ubuntu Xenial) Status: Confirmed => 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/1717382 Title: [Bug] Glibc: performance improvement patches Status in GLibC: Fix Released Status in intel: Fix Released Status in glibc package in Ubuntu: Fix Released Status in glibc source package in Xenial: Won't Fix Status in glibc source package in Zesty: Won't Fix Status in glibc source package in Artful: Fix Released Bug description: Description: Intel’s new request – for performance related patches that need to be picked up as part of one the Ubuntu 16.04 LTS family releases and Ubuntu 17.10: Glibc 2.23 needs the first 2 patches on hjl/pr21258/2.23 branch: https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=shortlog;h=refs/heads/hjl/pr21258/2.23 Patches: Address transition penalty when SSE instructions are mixed with 256-bit AVX or 512-bit AVX512 load instructions. Target Release: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1717382/+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 1874787] Re: xenial/linux-hwe: 4.15.0-100.101~16.04.1 -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/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1875878 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Promote to Proposed - phase-changed: Monday, 04. May 2020 17:18 UTC + phase: Testing + phase-changed: Monday, 04. May 2020 18:47 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 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1874785 variant: debs versions: main: 4.15.0-100.101~16.04.1 meta: 4.15.0.100.107 signed: 4.15.0-100.101~16.04.1 -- 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/1874787 Title: xenial/linux-hwe: 4.15.0-100.101~16.04.1 -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 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-hwe source package in Xenial: New 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: 1875878 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Monday, 04. May 2020 18:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1874785 variant: debs versions: main: 4.15.0-100.101~16.04.1 meta: 4.15.0.100.107 signed: 4.15.0-100.101~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874787/+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 1875485] Re: [SRU] python-botocore out of date
I will sponsor the backports in a moment as these updates do make sense. That being said, the python-botocore binary packages do seem to have a few reverse-dependencies from what I see, so we'd have to make sure we didn't regress those as well: $ reverse-depends src:python-botocore Reverse-Recommends * python3-mapproxy (for python3-botocore) * snakemake (for python3-botocore) Reverse-Depends * awscli(for python3-botocore) * python3-boto3 (for python3-botocore) * python3-s3transfer(for python3-botocore) * python3-sahara(for python3-botocore) $ reverse-depends -b src:python-botocore Reverse-Build-Depends-Indep * awscli(for python3-botocore) * python-scrapy (for python3-botocore) * sahara(for python3-botocore) Reverse-Build-Depends * python-aws-xray-sdk (for python3-botocore) * snakemake (for python3-botocore) ** Also affects: python-botocore (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python-botocore (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python-botocore (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-botocore (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: python-botocore (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/1875485 Title: [SRU] python-botocore out of date Status in python-botocore package in Ubuntu: Fix Released Status in python-botocore source package in Xenial: New Status in python-botocore source package in Bionic: New Status in python-botocore source package in Eoan: New Status in python-botocore source package in Focal: New Bug description: [Impact] * the python-botocore package is out of date, and out of sync with python3-botocore in debian [1], for all pockets except groovy- proposed. * The various outdated versions in, e.g. xenial and bionic, leave out lots of useful botocore functionality. * SRUing the current version back through supported suites will normalize sdk functionality across supported ubuntu releases. [Test Case] * On a machine running xenial, bionic, eoan, or focal: `apt install python-botocore` `dpkg -s python-botocore` verify the package is installed, at its version matches the latest upstream release version, 1.15.46. [Regression Potential] * apt-cache rdepends python-botocore reveals no dependent packages, so that should not be an issue. * however, the awscli tool source does require this package; there are probable configurations in use (e.g. pip install of awscli which use the local version of this package) wherein updates to this package will break users' expectations, especially where the version of botocore is pinned. * Any users on releases who are pinned to, or otherwise dependent on old versions of python-botocore being in the archive will likely be broken at some point by the package being updated in the archive. * New bugs introduced by botocore version releases will exist in the updated package [Other Info] * The Hardware Enablement exception likely applies here, as updating this package version will enable using functionality of the AWS cloud which are impossible to use with the versions of the cli currently in the archive. [1] https://packages.debian.org/sid/python3-botocore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+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 1876600] Re: cookie overruns cause org.freedesktop.systemd1 dbus to hang
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) -- 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/1876600 Title: cookie overruns cause org.freedesktop.systemd1 dbus to hang Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] Long-running services overflow the sd_bus->cookie counter, causing further communication with org.freedesktop.systemd1 to stall. [Description] Systemd dbus messages usually include a "cookie" value to uniquely identify them in their bus context. For services that run for longer periods of time and keep communicating through dbus, it's possible to overflow the cookie value, causing further messages to the org.freedesktop.systemd1 dbus to hang. This has been fixed upstream by the commit below: - sd-bus: deal with cookie overruns (1f82f5bb4237) $ git describe --contains 1f82f5bb4237 v242-rc1~228 $ rmadison systemd systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.27 | xenial-security | source, ... systemd | 229-4ubuntu21.27 | xenial-updates | source, ... systemd | 229-4ubuntu21.28 | xenial-proposed | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.38 | bionic-security | source, ... systemd | 237-3ubuntu10.39 | bionic-updates | source, ... systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... < systemd | 242-7ubuntu3 | eoan| source, ... Releases starting with Eoan already have this fix. [Test Case] There doesn't seem to be an easy test case for this, as the cookie values start at zero and won't overflow until (1<<32). There have been reports from users hitting this on Kubernetes clusters continuously running for longer periods (~5 months). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876600/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Hi John and all, thanks for updating logs and enhancing the report! Due to a lot of other work, and the nature of this problem (being a FW issue that we'd try to alleviate using a hack in linux), I wasn't able to work the tentative hack approach yet. The issue was "resolved" through a FW update by ASMedia, but this was only worked with a specific motherboard vendor, not as a general release. This is the problem with FW fixes...they are quite scattered and vendor-depending. So, can you John or any of the reporters try to reproduce the problem with: (a) Ubuntu 20.04, just released? (b) Ubuntu 18.04 running the current HWE kernel (5.3)? That'd be good data points. Also, if you could try Ubuntu 20.04 with latest mainline kernel (from [0]), that would be a gigantic help! Thanks in advance, Guilherme [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** No longer affects: linux (Ubuntu Artful) ** Changed in: linux (Ubuntu Trusty) Status: In Progress => 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+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 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
** Changed in: util-linux (Debian) 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/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Fix Released Status in util-linux package in Debian: Fix Released Bug description: [Impact] fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) [Test Case] * Ubuntu lxd container * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer) * fstrim will run and report errors "Operation not permitted" "Permission denied", ... Container shouldn't run fstrim, it should only be run at host level. [Potential Regression] None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that. Xenial uses the cronjob approach /etc/cron.weekly/fstrim Bionic and late switched to a systemd timer. 2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect. [Other Informations] * The systemd timer change upstream PR: https://github.com/karelzak/util-linux/pull/841 https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1874793] Re: xenial/linux-aws: 4.4.0-1107.118 -proposed tracker
** Changed in: kernel-sru-workflow/automated-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/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1874804 packages: main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Monday, 04. May 2020 11:16 UTC + phase: Testing + phase-changed: Monday, 04. May 2020 12:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for - mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1874792 variant: debs versions: main: 4.4.0-1107.118 meta: 4.4.0.1107.111 -- 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/1874793 Title: xenial/linux-aws: 4.4.0-1107.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws source package in Xenial: New 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: 1874804 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 04. May 2020 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1874792 variant: debs versions: main: 4.4.0-1107.118 meta: 4.4.0.1107.111 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874793/+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 1874767] Re: xenial/linux-aws-hwe: 4.15.0-1067.71~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1874768 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe - phase: Promote to Proposed - phase-changed: Monday, 04. May 2020 11:10 UTC + phase: Testing + phase-changed: Monday, 04. May 2020 12:46 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 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.15.0-1067.71~16.04.1 meta: 4.15.0.1067.67 -- 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/1874767 Title: xenial/linux-aws-hwe: 4.15.0-1067.71~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws-hwe source package in Xenial: New 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: 1874768 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Monday, 04. May 2020 12:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.15.0-1067.71~16.04.1 meta: 4.15.0.1067.67 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874767/+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